Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-87722 – Denial of Service (ReDoS) – Gerrit Code Review 2.1.6–3.14.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-87722 is a Denial of Service vulnerability in Gerrit Code Review caused by uncontrolled resource consumption when processing user-supplied regular expressions in search query predicates and REST filter endpoints. An unauthenticated, remote attacker can submit a crafted regular expression that exhausts JVM heap memory or pins CPU/request threads, degrading or crashing the Gerrit instance. The issue carries a CVSS score of 8.7 (High).

Technical details

  • Root cause: regex-based search predicates (e.g., project, ref, and path regex filters) and certain REST filter endpoints compile attacker-supplied regular expressions into an automaton representation without bounding size or complexity, before access-control or index-visibility checks occur.
  • Trigger condition: submitting a specially crafted regular expression (e.g., with excessive repetition or patterns causing exponential state expansion during compilation) to a regex-capable search or filter parameter.
  • Attack vector: Network — the malicious query can be sent over HTTP(S) to the Gerrit web/REST interface; no authentication or user interaction is required.
  • Impact: CPU starvation and JVM heap exhaustion/OutOfMemoryError, resulting in denial of service for the Gerrit instance; no confidentiality or integrity impact is reported.

Affected software

  • Gerrit Code Review 2.1.6 through 3.12.9
  • Gerrit Code Review 3.13.0 through 3.13.8
  • Gerrit Code Review 3.14.0 through 3.14.2

Severity

  • CVSS Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Gerrit Code Review to version 3.12.10, 3.13.9, or 3.14.3, depending on your current release line.
  • If patching is not immediately possible: restrict network access to the Gerrit web/REST interface (e.g., via allow-listing, VPN, or reverse proxy access controls) to reduce exposure to untrusted, unauthenticated requests, and monitor for abnormal CPU/memory usage on Gerrit servers as an indicator of attempted exploitation.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge