CVE-2026-84811

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-02. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

agentverus-scanner fails to analyze compiled Python bytecode files in companion code directories, allowing attackers to bypass security scanning by shipping malicious __pycache__ entries alongside benign source files. Attackers can execute arbitrary Python bytecode on import while the scanner reports a CERTIFIED verdict with high trust scores in both static and semantic analysis modes.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 3, 2026

Advisory Details (5)

Auto-updated Sep 2, 2026
No patch confirmed yet.
generic

agentverus-scanner Companion Code Analysis Bypass via Excluded Python Bytecode | Advisories | VulnCheck

https://www.vulncheck.com/advisories/agentverus-scanner-companion-code-analysis-bypass-via-excluded-python-bytecode
generic

GitHub - agentverus/agentverus-scanner: Trust, but verify. Security scanner for AI agent skills. Detects prompt injection, data exfiltration, and 10 ASST threat categories that antivirus misses. · GitHub

https://github.com/agentverus/agentverus-scanner
generic

agentverus-scanner/src/scanner/analyzers/semantic.ts at v0.8.1 · agentverus/agentverus-scanner · GitHub

https://github.com/agentverus/agentverus-scanner/blob/v0.8.1/src/scanner/analyzers/semantic.ts
generic

agentverus-scanner/src/scanner/companion-code.ts at v0.8.1 · agentverus/agentverus-scanner · GitHub

https://github.com/agentverus/agentverus-scanner/blob/v0.8.1/src/scanner/companion-code.ts
generic

[SECURITY BUG] .pyc bytecode excluded from companion code analysis (v0.8.1) · Issue #27 · agentverus/agentverus-scanner · GitHub

https://github.com/agentverus/agentverus-scanner/issues/27

Vendor Advisories for CVE-2026-84811(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 22:34 UTCEG score recompute
  2. 2026-09-18 22:34 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 20:37 UTCEG score recompute
  5. 2026-09-17 20:37 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-16 14:57 UTCEG score recompute
  8. 2026-09-16 14:57 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 13:00 UTCEG score recompute
  12. 2026-09-15 13:00 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 11:03 UTCEG score recompute
  16. 2026-09-14 11:03 UTCGHSA enrichment
  17. 2026-09-13 09:06 UTCEG score recompute
  18. 2026-09-13 09:06 UTCGHSA enrichment
  19. 2026-09-12 07:09 UTCEG score recompute
  20. 2026-09-12 07:09 UTCGHSA enrichment
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 05:12 UTCEG score recompute
  24. 2026-09-11 05:12 UTCGHSA enrichment
  25. 2026-09-10 03:15 UTCGHSA enrichment
Show 21 more
  1. 2026-09-09 01:18 UTCEG score recompute
  2. 2026-09-09 01:18 UTCGHSA enrichment
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 23:21 UTCEG score recompute
  5. 2026-09-07 23:21 UTCGHSA enrichment
  6. 2026-09-06 21:24 UTCEG score recompute
  7. 2026-09-06 21:24 UTCGHSA enrichment
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-05 19:25 UTCEG score recompute
  10. 2026-09-05 19:25 UTCGHSA enrichment
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 17:28 UTCEG score recompute
  13. 2026-09-04 17:28 UTCGHSA enrichment
  14. 2026-09-04 05:07 UTCEPSS rescore
  15. 2026-09-03 15:31 UTCEG score recompute
  16. 2026-09-03 15:31 UTCGHSA enrichment
  17. 2026-09-03 14:49 UTCEG score recompute
  18. 2026-09-03 14:49 UTCGHSA enrichment
  19. 2026-09-02 17:35 UTCEG score recompute
  20. 2026-09-02 17:03 UTCEG score recompute
  21. 2026-09-02 17:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84811?
CVE-2026-84811 is a medium vulnerability published on September 2, 2026. agentverus-scanner fails to analyze compiled Python bytecode files in companion code directories, allowing attackers to bypass security scanning by shipping malicious pycache entries alongside benign source files. Attackers can execute arbitrary Python bytecode on import while the scanner reports a…
When was CVE-2026-84811 disclosed?
CVE-2026-84811 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84811 actively exploited?
CVE-2026-84811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-84811?
CVE-2026-84811 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-84811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84811

Explore →

Is Your Infrastructure Affected by CVE-2026-84811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs