Threats / Aquasecurity / CVE-2026-33634

CVE-2026-33634 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

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-26⁵EPSS 0.59164 (verify live)⁶CVSS 9.4³CISA SSVC Exploitation: active · Automatable: no · Impact: total⁴

Is it exploitable?

— the evidence, ranked above the score

Reported exploitation

7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

nvd.nist.gov ↗kaspersky.com ↗cisa.gov ↗recordedfuture.com ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-26).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.59164 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

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.

CVE.org ↗Reported

Weakness (CWE)

Mapped to CWE-506 CWE-506.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.

CVE.org ↗Reported

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.

CISA-ADP ↗Reported

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.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-506 · CWE-506

Who’s exploiting it?

— attribution turns risk into urgency

Attribution 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.

Why it matters

— the attack path, told twice: adversary, then board

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.

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.

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.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

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.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

7 reported-exploitation source(s)

CVSS 9.4 — CNA-assigned (CVE.org)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping — CNA-assigned (CVE.org)

Catalogued by GitHub_M (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder is named in the public CVE record — attribution scoped to the sources checked.

Disclosure & credit²

Catalogued by GitHub_MCNA

Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2026-33634.html"], ["v", "sha256:c11983d288ff3ee6330cc269a9067efc11d004bc499934ca491a557f7477b620"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.