CVE-2026-87720

Incorrect Authorization via Stale ProjectCache Eviction and Repeated .git Suffixes in Gerrit Code Review

HIGH
7.6
CVSS Score
Published: September 24, 2026 at 09:59 PM UTC
Updated: September 25, 2026 at 05:17 PM UTC
1 product affected across 1 vendorGerrit

Using Gerrit by Gerrit?

Get instant alerts when new vulnerabilities affect Gerrit - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.6
Exploit prediction
EPSS 0.3%
SSVC
PoC

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.16.0 ≤ v < 3.12.103.13.0 ≤ v < 3.13.93.14.0 ≤ v < 3.14.32.16.03.13.03.14.0
Affected range stops below 3.12.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.13.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.14.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCPoCNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.6HIGHGoogle
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-613CWE-706CWE-863

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card