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.
Published: 2026-09-09
Score: 6.9 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A vulnerability allows a user to submit a CEL expression whose string length exceeds the configured ParserExpressionSizeLimit(), causing the library to allocate memory in proportion to the expression size before the limit is enforced. The result is an uncontrolled memory allocation that can exhaust host resources and lead to a denial of service. The weakness is characterized as an uncontrolled allocation flaw (CWE-789).

Affected Systems

The affected product is Google’s cel-go library. No specific version information is supplied, so any version of cel-go that does not implement length checks before allocation may be vulnerable. Organizations using cel-go in any code path that accepts user‑supplied expressions are at risk.

Risk and Exploitability

The CVSS score of 6.9 reflects moderate risk, and the lack of an EPSS score indicates insufficient data on actual exploitation. The vulnerability is not listed in CISA’s KEV catalog, implying no publicly known exploits. The likely attack vector is through application code that processes user‑provided CEL expressions, where an attacker can intentionally craft a very long expression to trigger excessive memory allocation. Because the allocation occurs before validation, the exploit is straightforward whenever a large expression is accepted.

Generated by OpenCVE AI on September 9, 2026 at 16:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update cel-go to the latest version that enforces size limits before allocation
  • If an update is not feasible, configure ParserExpressionSizeLimit to a conservative value and enforce validation of expression length beforehand
  • Implement application‑level checks to reject or truncate expressions that exceed a safe threshold, reducing the risk of resource exhaustion

Generated by OpenCVE AI on September 9, 2026 at 16:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 09 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 09 Sep 2026 15:15:00 +0000

Type Values Removed Values Added
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.
Title Uncontrolled Memory Allocation in cel-go
Weaknesses CWE-789
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Google

Published:

Updated: 2026-09-09T15:15:12.321Z

Reserved: 2026-08-31T16:27:40.016Z

Link: CVE-2026-83530

cve-icon Vulnrichment

Updated: 2026-09-09T15:15:09.385Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-09T15:17:12.123

Modified: 2026-09-09T16:17:11.983

Link: CVE-2026-83530

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-09T16:45:13Z

Weaknesses
  • CWE-789

    Memory Allocation with Excessive Size Value