How severe is CVE-2022-31097?

CVE-2022-31097 has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31097?

CVE-2022-31097 affects the following packages: github.com/grafana/grafana (Go), github.com/grafana/grafana (Go), github.com/grafana/grafana (Go), github.com/grafana/grafana (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31097?

Update github.com/grafana/grafana to 9.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31097 is resolved across your whole dependency graph.

How do I detect CVE-2022-31097 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 CVE-2022-31097 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 CVE-2022-31097?

O3 pinpoints whether CVE-2022-31097 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 CVE-2022-31097 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31097 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 CVE-2022-31097?

CVE-2022-31097 has an EPSS (Exploit Prediction Scoring System) score of 68.1%, placing it in the 99th 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.

When was CVE-2022-31097 published, and has it been updated?

CVE-2022-31097 was published on July 15, 2022 and was last updated on June 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-31097: Stored XSS in Grafana's Unified Alerting (High…

EPSS Exploitation Probability

via FIRST.org ↗

68.1%probability of exploitation in next 30 days

High Risk99th percentile+19.99%

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

4 pkgs affected

🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹github.com/grafana/grafana🐹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

Grafana is an open-source platform for monitoring and observability. Versions on the 8.x and 9.x branch prior to 9.0.3, 8.5.9, 8.4.10, and 8.3.10 are vulnerable to stored cross-site scripting via the Unified Alerting feature of Grafana. An attacker can exploit this vulnerability to escalate privilege from editor to admin by tricking an authenticated admin to click on a link. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch. As a workaround, it is possible to disable alerting or use legacy alerting.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/grafana/grafana`	≥ 9.0.0&&< 9.0.3	9.0.3
🐹Go	`github.com/grafana/grafana`	≥ 8.5.0&&< 8.5.9	8.5.9
🐹Go	`github.com/grafana/grafana`	≥ 8.4.0&&< 8.4.10	8.4.10
🐹Go	`github.com/grafana/grafana`	≥ 8.0.0&&< 8.3.10	8.3.10

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 9.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31097 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 CVE-2022-31097 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 CVE-2022-31097. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Grafana is an open-source platform for monitoring and observability. Versions on the 8.x and 9.x branch prior to 9.0.3, 8.5.9, 8.4.10, and 8.3.10 are vulnerable to stored cross-site scripting via the Unified Alerting feature of Grafana. An attacker can exploit this vulnerability to escalate privilege from editor to admin by tricking an authenticated admin to click on a link. Versions 9.0.3, 8.5.9, 8.4.10, and 8.3.10 contain a patch. As a workaround, it is possible to disable alerting or use legacy alerting.

O3 Security · Impact-Aware SCA

Is CVE-2022-31097 in your dependencies?

O3 detects CVE-2022-31097 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

CVE-2022-31097