CVE-2026-95502
Git Sync memory exhaustion via a malicious Git server
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.7.0, 13.0.11, 13.1.8, 13.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A Git server that Grafana's Git Sync (provisioning) is configured to use can exhaust Grafana's memory by returning oversized or highly compressed responses (uncontrolled resource consumption). Exploitation requires an administrator to have configured Git Sync with that server.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Grafana Nanogit
fixed in 1.7.0
- Grafana Grafana OSS
From 13.0.0 · fixed in 13.0.11; From 13.1.0 · fixed in 13.1.8; From 13.2.0 · fixed in 13.2.4
- Grafana Grafana Enterprise
From 13.0.0 · fixed in 13.0.11; From 13.1.0 · fixed in 13.1.8; From 13.2.0 · fixed in 13.2.4