Memory exhaustion via unbounded Git response decoding
Published Oct 13, 2026 · Updated Oct 13, 2026
Memory exhaustion in Grafana OSS and Grafana Enterprise Git Sync allows remote attackers to disrupt service via malicious Git responses. Nanogit's response processing accepts oversized replies or compressed packfile objects that expand beyond wire-byte limits, consuming excessive memory. An administrator must have configured Git Sync with the attacker-controlled server; the record does not specify whether exhaustion causes a hang or crash.
Summary
What happened
Memory exhaustion in Grafana OSS and Grafana Enterprise Git Sync allows remote attackers to disrupt service via malicious Git responses. Nanogit's response processing accepts oversized replies or compressed packfile objects that expand beyond wire-byte limits, consuming excessive memory. An administrator must have configured Git Sync with the attacker-controlled server; the record does not specify whether exhaustion causes a hang or crash.
The record
- CVE
- CVE-2026-95502
- Published
- Oct 13, 2026
- Updated
- Oct 13, 2026
- Vendor
- Grafana Labs
- Product
- Nanogit
- Classifications
- T1499.003
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 13, 2026CVE publishedPublication date reported by the CVE source.
- Oct 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.7.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started