How severe is CVE-2026-83530?

CVE-2026-83530 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2026-83530 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-83530?

CVE-2026-83530 affects Google Common Expression Language. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-83530?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-83530 published?

CVE-2026-83530 was published on 2026-09-09 and last updated on 2026-09-23.

CVE-2026-83530

CVE-2026-83530 is a medium-severity vulnerability in Google Common Expression Language with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-789.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
CVSS v4: 6.9
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-789
Affected product: Google Common Expression Language
Published: 2026-09-09
Last modified: 2026-09-23

Description

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.

Frequently asked questions

What is CVE-2026-83530?: 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.
How severe is CVE-2026-83530?: CVE-2026-83530 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-83530 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-83530?: CVE-2026-83530 affects Google Common Expression Language. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-83530?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-83530 published?: CVE-2026-83530 was published on 2026-09-09 and last updated on 2026-09-23.

References

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

Affected products (1)

cpe:2.3:a:google:common_expression_language:*:*:*:*:*:go:*:*

Other CWE-789 vulnerabilities

CVE-2026-82435 — Critical (CVSS 9.8): Description The worker's Netty message decoder is installed ahead of the SASL authentication handlers in the…
CVE-2026-77410 — High (CVSS 8.9): RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the…
CVE-2021-34869 — High (CVSS 8.8): This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop…
CVE-2021-34868 — High (CVSS 8.8): This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop…
CVE-2026-63574 — High (CVSS 8.7): Memory allocation with excessive size value in the OpenPGP signature and user attribute subpacket parsers…
CVE-2026-103603 — High (CVSS 8.7): Memory allocation with excessive size value in the HSS/LMS signature code (HssPublicKeyParameters, HssSignature) in…

Browse all CWE-789 vulnerabilities →