CVE-2026-83530

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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
Trending — 3 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

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

A user could provide an expression whose string length is longer than the ParserExpressionSizeLimit() configured on the CEL environment, and a memory allocation would occur proportional to the size of the input before the limit would be checked / enforced.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

fix: enforce expression size limit before source construction

Patch available: cel-expr/cel-go v0.29.0 (PR #1302 merged 2026-05-19)

https://github.com/cel-expr/cel-go/pull/1302

Vendor Advisories for CVE-2026-83530(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 19× in last 7d / 29× 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-19 00:41 UTCEG score recompute
  2. 2026-09-19 00:41 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 23:54 UTCEG score recompute
  5. 2026-09-17 23:54 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-16 22:24 UTCEG score recompute
  8. 2026-09-16 22:24 UTCGHSA enrichment
  9. 2026-09-16 14:09 UTCEPSS rescore
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 21:15 UTCEG score recompute
  12. 2026-09-15 21:15 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 20:29 UTCGHSA enrichment
  16. 2026-09-13 19:43 UTCEG score recompute
  17. 2026-09-13 19:43 UTCGHSA enrichment
  18. 2026-09-12 18:57 UTCEG score recompute
  19. 2026-09-12 18:57 UTCGHSA enrichment
  20. 2026-09-11 18:11 UTCEG score recompute
  21. 2026-09-11 18:11 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-10 17:24 UTCGHSA enrichment
  25. 2026-09-09 16:37 UTCGHSA enrichment
Show 4 more
  1. 2026-09-09 15:47 UTCGHSA enrichment
  2. 2026-09-09 15:27 UTCEG score recompute
  3. 2026-09-09 15:05 UTCEG score recompute
  4. 2026-09-09 15:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83530?
CVE-2026-83530 is a medium vulnerability published on September 9, 2026. A user could provide an expression whose string length is longer than the ParserExpressionSizeLimit() configured on the CEL environment, and a memory allocation would occur proportional to the size of the input before the limit would be checked / enforced.
When was CVE-2026-83530 disclosed?
CVE-2026-83530 was first published in the National Vulnerability Database 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-83530 actively exploited?
CVE-2026-83530 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 88.7% of all scored CVEs.
What is the CVSS score of CVE-2026-83530?
CVE-2026-83530 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-83530?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83530, 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-83530

Explore →

Is Your Infrastructure Affected by CVE-2026-83530?

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

Start Free Scan →Browse All CVEs