cve.bz

CVE-2026-77299 dlclark regexp2: Uncontrolled Resource Consumption

7.5 highEPSS 0.3%

High (7.5) in dlclark regexp2. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Regexp2 is a feature-rich RegExp engine for Go. Prior to version 2.3.0, when regexp2 compiles and matches a pattern containing a large fixed-count quantifier applied to a zero-width subexpression — e.g. (?:){50000000} — the match engine executes the empty loop body m-1 times, pushing two integers onto the backtracking stack on every iteration. Because the parser accepts any repetition count up to math.MaxInt32 and the backtracking stack grows without bound, a pattern of fewer than 20 bytes matched against an empty input can force multi-gigabyte allocation and OOM-kill the process. MatchTimeout does not fully mitigate this because the memory is allocated faster than the 100 ms timeout clock can fire. This issue has been patched in version 2.3.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-77299 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77299?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77299?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77299 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
dlclark regexp2< 2.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-dlclark-regexp2no fix listedDEBIAN-CVE-2026-77299
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 3 moregolang-github-dlclark-regexp2no fix listedUBUNTU-CVE-2026-77299
Red Hathummingbird:1hugo0:0.169.0-0.2.hum1RHSA-2026:99590
Red Hathummingbird:1loki3.6, loki3.6-canary, loki3.6-logcli0:3.6.20-0.2.hum1RHSA-2026:98019
Red Hathummingbird:1trivy0:0.76.1-0.3.hum1RHSA-2026:97885
Azure Linux3daselno fix listedAZL-113137
Azure Linux3ghno fix listedAZL-113161
Azure Linux3regexpno fix listedAZL-112697

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity because it enables remote attackers to crash consuming Go applications or services through rapid memory exhaustion without authentication. Applications utilizing regexp2 are susceptible when they compile or evaluate untrusted, user-controlled regular expressions. In typical Red Hat environments, Go services parsing arbitrary expressions directly from network clients face service termination via out-of-memory errors, whereas deployments that restrict pattern definitions to trusted administrative inputs remain unaffected.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

--- CME Mitigation Guidance (2026-11-06) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce computational budget and backtracking depth limits within regexp2 or disallow untrusted user-supplied patterns: upgrade to regexp2 2.3.0 (or the corresponding fixed Red Hat builds), which enforce a default limit of 100,000 slots on the backtracking stack via OptionMaxBacktrackingStackSize and optimize away repeated literal empty expressions, closing crafted regular expression with large repetition quantifier on empty subexpression. Until patched, this is only a concern on Go applications compiling or matching untrusted, user-supplied regular expressions using regexp2 — deployments restricting pattern definitions to trusted administrative inputs are unaffected — so validate incoming patterns to reject large quantifier values and zero-width repetitions, and restrict regular expression compilation exclusively to trusted administrative inputs. As a compensating measure, enforce per-process address space limits (RLIMIT_AS) via ulimit or prlimit to constrain memory consumed by the backtracking stack, reject regular expression inputs containing repetition quantifiers that exceed safe application-defined bounds before passing them to regexp2, and apply cgroups v2 resource limits to bound container memory usage and prevent host-wide memory starvation. These controls limit blast radius and contain exploitation, but they do not fix the underlying unbounded memory allocation defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1316 Algorithmic Complexity Safeguards (Pattern/Regex Execution Limits) (high)

ProductPackageStateAdvisory
Logging Subsystem for Red Hat OpenShiftopenshift-logging/logging-loki-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-analyzer-addon-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-cli-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-go-external-provider-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-java-external-provider-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-nodejs-external-provider-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-python-external-provider-rhel9Under investigation
Migration Toolkit for Applications 8mta/mta-solution-server-rhel9Under investigation
Multicluster Global Hubmulticluster-globalhub/multicluster-globalhub-grafana-rhel9Under investigation
Multicluster Global Hub 5multicluster-globalhub/multicluster-globalhub-grafana-rhel9Under investigation
OpenShift Service Mesh 3istio-proxyUnder investigation
OpenShift Service Mesh 3openshift-service-mesh/istio-cni-rhel9Under investigation
OpenShift Service Mesh 3openshift-service-mesh/istio-pilot-rhel9Under investigation
OpenShift Service Mesh 3openshift-service-mesh/istio-proxyv2-rhel9Under investigation
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/acm-grafana-rhel9Under investigation
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/kube-state-metrics-rhel9Under investigation
Red Hat Ceph Storage 8rhceph/rhceph-promtail-rhel9Fix deferred
Red Hat Enterprise Linux 10grafanaUnder investigation
Red Hat Enterprise Linux 10gvisor-tap-vsockUnder investigation
Red Hat Enterprise Linux 8grafanaUnder investigation
51 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77299.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON