# CVE-2026-95502: Git Sync memory exhaustion via a malicious Git server

> A malicious Git server can exhaust Grafana's memory via oversized responses, causing denial of service if Git Sync is configured.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-w2wx-887f-65f8

## What is CVE-2026-95502?

CVE-2026-95502 is a medium-severity denial of service vulnerability in Grafana Enterprise, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-95502?


## How do I fix CVE-2026-95502?

Apply the vendor's patch.

## Is CVE-2026-95502 being exploited?

There is no known exploitation of CVE-2026-95502 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95502 and fix it if it is affected.

What it is: CVE-2026-95502 is a medium-severity denial of service vulnerability in Grafana Enterprise, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95502 in the wild and no public exploit code.

Affected product: Grafana Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95502/ (Markdown: https://insights.sbomify.com/CVE-2026-95502/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95502
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95502
- OSV: https://osv.dev/vulnerability/CVE-2026-95502

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95502/
Summaries are generated and may contain mistakes; the official description above is the record.