GHSA-8rm2-7qqf-34qm is a high-severity (CVSS 7.5) vulnerability in github.com/prometheus/prometheus. O3 Security confirms whether GHSA-8rm2-7qqf-34qm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Prometheus: Remote read endpoint allows denial of service via crafted snappy payload
Real-World Exposure
github.com/prometheus/prometheus🐹github.com/prometheus/prometheus🐹github.com/prometheus/prometheusReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The remote read endpoint (/api/v1/read) does not validate the declared decoded length in a snappy-compressed request body before allocating memory.
An unauthenticated attacker can send a small payload that causes a huge heap allocation per request. Under concurrent load this can exhaust available memory and crash the Prometheus process.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 3.11.3 and 3.5.3 LTS. Users should upgrade to these versions or later.
Workarounds
User who can not upgrade can place Prometheus behind a reverse proxy or firewall that requires authentication before requests reach /api/v1/read.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/prometheus/prometheus | ≥ 0.306.0&&< 0.311.3 | 0.311.3 |
| 🐹Go | github.com/prometheus/prometheus | all versions | 0.305.2 |
| 🐹Go | github.com/prometheus/prometheus | ≥ 1.0.0-rc.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/prometheus/prometheus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/prometheus/prometheus to 0.311.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8rm2-7qqf-34qm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8rm2-7qqf-34qm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-8rm2-7qqf-34qm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-8rm2-7qqf-34qm in your dependencies?
O3 detects GHSA-8rm2-7qqf-34qm across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.