Skip to content

Commit 4050aeb

Browse files
authored
Merge pull request #11 from mlimardo1984/msr4-trivy
Add Advisory 0014 (MSR4 Trivy Vuln)
2 parents 29d8760 + 83167cf commit 4050aeb

2 files changed

Lines changed: 30 additions & 0 deletions

File tree

advisories/0014.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Mirantis Secure Registry 4 and CVE-2026-33634: Not Vulnerable
2+
3+
### Release Date
4+
2026-03-26
5+
6+
### Overview
7+
In March 2026, a supply chain compromise was identified within the Trivy ecosystem, where malicious actors gained unauthorized access to the release pipeline. This resulted in the publication of compromised Trivy binaries (v0.69.4, v0.69.5, and v0.69.6) and the poisoning of associated GitHub Action tags. These malicious versions contained code designed to exfiltrate credentials from CI/CD environments.
8+
9+
Mirantis has verified that **Mirantis Secure Registry (MSR) 4** does not utilize any of the compromised Trivy versions. MSR 4 releases are built using stable, verified versions of Trivy that predate the incident, ensuring the integrity of the registry's internal vulnerability scanning engine.
10+
11+
### Unaffected Products
12+
**No versions of MSR 4 (Mirantis Secure Registry) are affected by CVE-2026-33634.** Internal audits of the dependency tree for all MSR 4 branches confirm that the software remains on secure, non-compromised versions of the scanning binary. Security scanners or automated dependency trackers may flag the presence of Trivy as a general category; however, MSR 4 specifically utilizes versions released prior to the window of compromise.
13+
14+
* **MSR 4.13.0:** Utilizes Trivy **v0.69.3** (Unaffected).
15+
* **MSR 4.0.0:** Utilizes Trivy **v0.52.2** (Unaffected).
16+
17+
### Vulnerability Information
18+
19+
**CVE Identifier** [CVE-2026-33634](https://nvd.nist.gov/vuln/detail/CVE-2026-33634), [GHSA-69fq-xp46-6x23](https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23)
20+
21+
**CVSSv3.1** 9.8 (Critical) `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
22+
23+
**CWEs** CWE-506 (Embedded Malicious Code), CWE-912 (Managed Third-Party Compromise)
24+
25+
### Disclosure Timeline
26+
* **2026-03-17:** Trivy v0.69.4 is released with unauthorized malicious code injected into the binary.
27+
* **2026-03-19:** The vulnerability is publicly disclosed; malicious versions (v0.69.4 - v0.69.6) are pulled from distribution.
28+
* **2026-03-20:** Mirantis begins an impact analysis of MSR product utilizing the Trivy scanning engine.
29+
* **2026-03-22:** Analysis confirms that MSR 4.13 and MSR 4.0 utilize Trivy v0.69.3 and v0.52.2, respectively, and were never updated to the compromised versions.

advisories/advisories.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
## Security Advisories
22

3+
* [0014](/advisories/0014.md): Mirantis Secure Registry 4 and CVE-2026-33634: Not Vulnerable
34
* [0013](/advisories/0013.md): Mirantis Container Products and CVE-2024-41110: Not Vulnerable
45
* [0012](/advisories/0012.md): Mirantis Container Products and CVE-2024-3094: Not Vulnerable
56
* [0011](/advisories/0011.md): Mirantis Kubernetes Engine (MKE) and CVE-2024-21626: Understanding the Potential Impact and Mitigation

0 commit comments

Comments
 (0)