Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-87720Published 2026-09-24

CVE-2026-87720 — Gerrit

high (derived)Public exploit1 PoC repo

As of 2026-09-25, CVE-2026-87720 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in Gerrit, CVSS v4.0 7.6, EPSS 0.2% (14.7th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-87720 as of 2026-09-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
7.6/10High (derived)
EPSS
0.2%Higher than 14.7% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
6.4/10Threadlinqs triage score
Published
Updated 2026-09-25
CVSS v4.0 7.6 (High, derived from score) · EPSS 0.2% (higher than 14.7% of all scored CVEs) · Priority 6.4/10 · Published 2026-09-24

Last updated:

What is CVE-2026-87720?

Incorrect Authorization (CWE-863) in project name normalization (ProjectUtil.stripGitSuffix) and ProjectCache eviction logic (ProjectCacheImpl) in Gerrit Code Review versions 2.16.0 through 3.12.9, 3.13.0 through 3.13.8, and 3.14.0 through 3.14.2 allows an authenticated user (or an unauthenticated user if the repository was previously public) to cause unauthorized disclosure of private repository content and durable restoration of revoked project-owner administrative privileges via crafted requests using repeated .git suffixes (such as project.git.git) across REST APIs, Gitiles, or SSH Git commands. Because Gerrit strips only a single terminal .git suffix when constructing the logical ProjectCache key while JGit (FileKey.lenient) resolves the suffixed alias to the same canonical bare repository on disk, revoking read access or removing owner rules on the canonical project name fails to evict the cached alias ProjectState during the cache validity window, enabling reads of newly created private commits or writes to refs/meta/config. This issue is fixed in Gerrit Code Review versions 3.12.10, 3.13.9, and 3.14.3.

The record classifies CVE-2026-87720 under weakness classes CWE-863, CWE-613, CWE-706. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 11 days ago.

Severity and exploitation probability

CVSS v4.0 base score
7.6 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 14.7% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-24, last modified 2026-09-25

Is CVE-2026-87720 being exploited?

Weaponised exploit code for CVE-2026-87720 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Gerrit: Gerrit

How to fix CVE-2026-87720

No vendor patch reference has been recorded for CVE-2026-87720 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-87720

No threat campaign in the Threadlinqs corpus currently references CVE-2026-87720, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories, NVD. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Other references