Heap Memory exhaustion in Gerrit

published 2021-02-17 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-9694

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits: 0; none known

Any git operation is passed through Jetty and a session is created. No expiry is set for the session and Jetty does not automatically dispose of the session. Over multiple git actions, this can lead to a heap memory exhaustion for Gerrit servers. We recommend upgrading Gerrit to any of the versions listed above.

Patch / fix

fixed in 1

Google LLC Gerrit 2.15.22, 2.16.26, 3.0.16, 3.1.12, 3.2.7, 3.3.2

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

Google LLC Gerrit

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption
CWE-772 Missing Release of Resource after Effective Lifetime

References

bugs.chromium.org /p/gerrit/issues/detail?id=13858
issue-tracking, third-party-advisory

Sources

CVE List CVE-2021-22553
NVD CVE-2021-22553

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary