Threats / Aquasecurity / CVE-2026-33634
CVE-2026-33634
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Aquasecurity Trivy vulnerability
Aquasecurity Trivy contains embedded malicious code allowing attackers to extract sensitive credentials and configuration from CI/CD environments, including tokens, SSH keys, and cloud credentials.
Verdict
Today item — known-exploited.
An attacker exploiting this embedded malicious code vulnerability gains unauthorized access to CI/CD pipeline secrets and credentials, enabling lateral movement, infrastructure compromise, and data exfiltration across connected systems.
CISA KEV Yes · 2026-03-265EPSS 0.59164 (verify live)6CVSS 9.43CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-26).
Probability (EPSS)
EPSS 0.59164 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.4 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H) · Affected: Aquasecurity, Trivy. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-506 CWE-506.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
WeaknessCWE-506 · CWE-506
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I execute the compromised Trivy binary in a CI/CD pipeline to trigger the embedded malicious code.
Business
Attacker gains direct access to all secrets stored in the CI/CD environment without detection.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract tokens, SSH keys, cloud credentials, and database passwords from the pipeline's memory and environment.
Business
Sensitive authentication material is compromised, enabling unauthorized access to production systems and data stores.
3
Lateral reach — past segmentation narrative 3
Attacker
I use the stolen credentials to move laterally across cloud infrastructure, repositories, and internal services.
Business
Organizational security perimeter is breached; attacker gains persistent access to critical infrastructure and intellectual property.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05