How severe is GHSA-h5rh-w6vm-9ghc?

GHSA-h5rh-w6vm-9ghc has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-h5rh-w6vm-9ghc?

GHSA-h5rh-w6vm-9ghc affects the following packages: github.com/grafana/grafana (Go). Ecosystems affected: Go.

How do I fix GHSA-h5rh-w6vm-9ghc?

Update github.com/grafana/grafana to 7.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5rh-w6vm-9ghc is resolved across your whole dependency graph.

How do I detect GHSA-h5rh-w6vm-9ghc in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana. 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.

How do I mitigate GHSA-h5rh-w6vm-9ghc if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-h5rh-w6vm-9ghc?

O3 pinpoints whether GHSA-h5rh-w6vm-9ghc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h5rh-w6vm-9ghc actively exploited in the wild?

No public exploit code has been indexed for GHSA-h5rh-w6vm-9ghc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-h5rh-w6vm-9ghc?

GHSA-h5rh-w6vm-9ghc has an EPSS (Exploit Prediction Scoring System) score of 83.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for GHSA-h5rh-w6vm-9ghc?

A Nuclei detection template exists for GHSA-h5rh-w6vm-9ghc, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-h5rh-w6vm-9ghc published, and has it been updated?

GHSA-h5rh-w6vm-9ghc was published on February 15, 2022 and was last updated on December 6, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-h5rh-w6vm-9ghc: Denial of service in Grafana (High 8.2)

EPSS Exploitation Probability

via FIRST.org ↗

83.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/grafana/grafana

Real-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

The snapshot feature in Grafana before 7.4.2 can allow an unauthenticated remote attackers to trigger a Denial of Service via a remote API call if a commonly used configuration is set.

Specific Go Packages Affected

github.com/grafana/grafana/pkg/middleware

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/grafana/grafana`	≥ 6.7.3&&< 7.4.2	7.4.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana. 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/grafana/grafana to 7.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h5rh-w6vm-9ghc 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-h5rh-w6vm-9ghc 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-h5rh-w6vm-9ghc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The snapshot feature in Grafana before 7.4.2 can allow an unauthenticated remote attackers to trigger a Denial of Service via a remote API call if a commonly used configuration is set. ### Specific Go Packages Affected github.com/grafana/grafana/pkg/middleware

O3 Security · Impact-Aware SCA

Is GHSA-h5rh-w6vm-9ghc in your dependencies?

O3 detects GHSA-h5rh-w6vm-9ghc across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-h5rh-w6vm-9ghc