CVE-2026-28353: Malicious Trivy VS Code Extension 1.8.12 Supply-Chain Compromise
CVE-2026-28353 tracks a supply-chain compromise of the Trivy Vulnerability Scanner VS Code extension. According to the provided content, Trivy VSCode Extension version 1.8.12 distributed through the OpenVSX marketplace was compromised and shipped with malicious code. The implanted code was designed to leverage a locally installed AI coding agent to inspect the developer environment, collect sensitive information, and exfiltrate that data. Supporting reporting in the provided context states the broader incident involved abuse of local AI coding CLIs such as Claude, Codex, Gemini, GitHub Copilot CLI, and Kiro, and that the malicious extension targeted developer workstations rather than production systems directly. The malicious artifact has since been removed from the marketplace, and the provided content states that no other affected artifacts were identified in the CVE record.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation exposes sensitive information present in the affected developer environment. Based on the provided content, the malicious extension was intended to collect and exfiltrate secrets and other sensitive data from systems where it was installed, potentially including environment secrets and data accessible to local AI coding agents. Additional reporting in the supplied context indicates the broader campaign targeted developer trust zones and could abuse authenticated local tooling, including AI coding assistants and, in some variants, the victim's authenticated GitHub CLI session, creating risk of credential theft, repository access abuse, and downstream compromise of development and CI/CD assets. The CVE context indicates high confidentiality, integrity, and availability impact.
Mitigation
If you can’t patch tonight, do this now.
Until remediation is complete, isolate affected developer workstations from sensitive resources where feasible, revoke or disable exposed tokens, and monitor for unauthorized use of GitHub, cloud, registry, and CI/CD credentials. Restrict or review use of local AI coding agents and authenticated developer CLIs on systems that installed the malicious extension, because the malicious logic was designed to leverage such tools for collection and exfiltration. More broadly, reduce marketplace supply-chain risk by pinning trusted extension sources, validating publisher provenance, limiting secret exposure on developer endpoints, and monitoring outbound activity from developer tooling.
Remediation
Patch, then assume compromise.
Immediately uninstall/remove the compromised Trivy VSCode Extension version 1.8.12 obtained from OpenVSX. Treat the affected host as exposed and rotate environment secrets and any credentials that may have been accessible from the developer environment at the time of installation, including tokens used for source control, cloud services, registries, and CI/CD where applicable. Verify that the malicious artifact is no longer present in the extension directory, review developer workstation and repository activity for unauthorized access or exfiltration, and reinstall only a known-good version from a trusted source after validating publisher integrity. The provided content states the malicious artifact has already been removed from the marketplace.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-28353 exploited in the wild?
- Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-28353?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-28353.
- Is there a patch for CVE-2026-28353?
- Immediately uninstall/remove the compromised Trivy VSCode Extension version 1.8.12 obtained from OpenVSX. Treat the affected host as exposed and rotate environment secrets and any credentials that may have been accessible from the developer environment at the time of installation, including tokens used for source control, cloud services, registries, and CI/CD where applicable.
- How severe is CVE-2026-28353?
- CVE-2026-28353 has a CVSS v4 score of 10.0 (Critical) and an EPSS score of 0.51% (44th percentile) as of Sep 25, 2026.
Recent activity
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.