CVE-2026-53670

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: Elevated riskExposed: 0

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

PREVAIL is a Polynomial-Runtime EBPF Verifier using an Abstract Interpretation Layer. Prior to version 0.2.4, in the Prevail eBPF verifier, EbpfTransformer::add() silently skips offset-variable updates when the destination register carries a non-singleton typeset (two or more simultaneously possible pointer types). Subsequent bounds checks use the stale offset and accept out-of-bounds memory accesses, so a crafted BPF program passes verification even though it would corrupt memory at runtime. This issue has been patched in version 0.2.4.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
73(Attend)
EG Risk 73/100SSVC: Attend

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
Severity93% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github Patch Available🟡 PoC Available

Non-singleton typeset in add() skips offset update, allowing OOB access to pass eBPF verification · Advisory · vbpf/prevail · GitHub

https://github.com/vbpf/prevail/security/advisories/GHSA-2qc8-qh94-66rc
github_release Patch Available

v0.2.4

Patch available: vbpf/prevail v0.2.4

https://github.com/vbpf/prevail/releases/tag/v0.2.4
github_commit Patch Available

commit 2b209bc4e3d6 (vbpf/prevail)

Patch available: vbpf/prevail v0.2.4 (contains commit 2b209bc4e3d6)

https://github.com/vbpf/prevail/commit/2b209bc4e3d612ff9aca87125e67c0ff84477e61

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 28× 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 23:07 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:37 UTCEG score recompute
  4. 2026-09-16 14:33 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:44 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 03:12 UTCEG score recompute
  9. 2026-09-13 20:03 UTCEG score recompute
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-12 17:34 UTCEG score recompute
  12. 2026-09-11 10:45 UTCEG score recompute
  13. 2026-09-10 12:44 UTCEG score recompute
  14. 2026-09-10 09:35 UTCEPSS rescore
  15. 2026-09-08 23:11 UTCEG score recompute
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 19:15 UTCEG score recompute
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 16:15 UTCEG score recompute
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-05 18:14 UTCEG score recompute
  22. 2026-09-04 15:43 UTCEG score recompute
  23. 2026-09-04 06:56 UTCEG score recompute
  24. 2026-09-04 05:06 UTCEPSS rescore
  25. 2026-09-02 19:31 UTCEG score recompute
Show 3 more
  1. 2026-09-02 18:30 UTCEG score recompute
  2. 2026-09-02 18:03 UTCEG score recompute
  3. 2026-09-02 18:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53670?
CVE-2026-53670 is a critical vulnerability published on September 2, 2026. PREVAIL is a Polynomial-Runtime EBPF Verifier using an Abstract Interpretation Layer. Prior to version 0.2.4, in the Prevail eBPF verifier, EbpfTransformer::add() silently skips offset-variable updates when the destination register carries a non-singleton typeset (two or more simultaneously…
When was CVE-2026-53670 disclosed?
CVE-2026-53670 was first published in the National Vulnerability Database on September 2, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53670 actively exploited?
CVE-2026-53670 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.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53670?
CVE-2026-53670 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-53670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53670, 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-53670

Explore →

Is Your Infrastructure Affected by CVE-2026-53670?

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