dbcve.org
CWE-506Weakness · CWE-506

CVE-2026-28353

CRITICAL · 10.0 CVSS v4.0 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Trivy Vulnerability Scanner is a VS Code extension that helps find vulnerabilities. In Trivy VSCode Extension version 1.8.12, which was distributed via OpenVSX marketplace was compromised and contained malicious code designed to leverage local AI coding agent to collect and exfiltrate sensitive information. Users using the affected artifact are advised to immediately remove it and rotate environment secrets. The malicious artifact has been removed from the marketplace. No other affected artifacts have been identified.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Trivy VSCode Extension version 1.8.12 distributed via OpenVSX marketplace was compromised with malicious code designed to leverage local AI coding agents to collect and exfiltrate sensitive information from developer environments.

MitigationImmediately remove the compromised extension from VS Code and rotate all environment secrets, API keys, tokens, and credentials that may have been exposed during the time the malicious extension was installed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Trivy extension is installed
    Open VS Code, go to Extensions view (Ctrl+Shift+X), search for 'Trivy' and verify if the Trivy Vulnerability Scanner extension is listed in your installed extensions
    Affected if The Trivy Vulnerability Scanner extension appears in your installed extensions list
  2. Identify the installed version
    In the Extensions view, click on the Trivy extension to view its details. The version number is displayed on the extension's detail page under the extension name
    Affected if The installed version is 1.8.12
  3. Check the extension source
    In the extension detail page, look for the publisher information or extension source (OpenVSX vs VS Code Marketplace). The extension ID format typically shows the publisher name
    Affected if The extension was obtained from OpenVSX marketplace (verify by checking the extension ID or source in the detail view)
  4. Review extension permissions
    Open VS Code settings, go to Extensions > Trivy, and review what permissions/scopes the extension has been granted
    Affected if The extension has permissions to access files, environment variables, or network resources (which it would need to exfiltrate data)

You are affected if the Trivy Vulnerability Scanner extension version 1.8.12 from OpenVSX is installed in your VS Code instance, as this specific version contains the malicious code designed to target local AI coding agents.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove the compromised extension from VS Code and rotate all environment secrets, API keys, tokens, and credentials that may have been exposed during the time the malicious extension was installed.

Recommended fix High confidence
  1. Uninstall the Trivy VS Code Extension version 1.8.12 from your IDE
  2. Rotate all environment secrets, API keys, tokens, and credentials that may have been accessible during the time the extension was installed
  3. Review logs and systems for any signs of unauthorized access or data exfiltration
  4. Reinstall the extension from a trusted, verified source only after confirming it is legitimate (note: the malicious artifact has been removed from OpenVSX marketplace)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28353 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28353 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data