NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2022-21703 — web

MEDIUMFix: grafana/grafana#45083

CVE-2022-21703 is a medium-severity (CVSS 6.3) Cross-Site Request Forgery (CSRF) vulnerability in github.com/grafana/grafana/pkg/web. A fix is available for github.com/grafana/grafana/pkg/web — see the affected versions and patch details below.

Cross Site Request Forgery in Grafana

Also known asBIT-grafana-2022-21703GHSA-cmf4-h3xc-jw8w
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-21703.

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
1.37%1.84%2.31%2.78%1.9%2.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/grafana/grafana/pkg/web🐹github.com/grafana/grafana/pkg/web

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

Today we are releasing Grafana 8.3.5 and 7.5.15. This patch release includes MEDIUM severity security fix for Cross Site Request Forgery for Grafana.

Release v.8.3.5, only containing security fixes:

Release v.7.5.15, only containing security fixes:

CSRF (CVE-2022-21703)

Summary

On Jan. 18, security researchers jub0bs and abrahack contacted Grafana to disclose a CSRF vulnerability which allows anonymous attackers to elevate their privileges by mounting cross-origin attacks against authenticated high-privilege Grafana users (for example, Editors or Admins).

We believe that this vulnerability is rated at CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N).

Impact

An attacker can exploit this vulnerability for privilege escalation by tricking an authenticated user into inviting the attacker as a new user with high privileges.

Affected versions with MEDIUM severity

All Grafana >=3.0-beta1 versions are affected by this vulnerability.

Solutions and mitigations

All installations after Grafana v3.0-beta1 should be upgraded as soon as possible.

Note that if you are running Grafana behind any reverse proxy, you need to make sure that you are passing the original Host and Origin headers from the client request to Grafana.

In the case of Apache Server, you need to add ProxyPreserveHost on in your proxy configuration. In case of NGINX, you can need to add proxy_set_header Host $http_host; in your configuration.

Appropriate patches have been applied to Grafana Cloud and as always, we closely coordinated with all cloud providers licensed to offer Grafana Pro. They have received early notification under embargo and confirmed that their offerings are secure at the time of this announcement. This is applicable to Amazon Managed Grafana.

Timeline and postmortem

Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.

  • 2022-01-18 03:00 Issue submitted by external researchers
  • 2022-01-18 17:25 Vulnerability confirmed reproducible
  • 2022-01-19 07:40 CVSS score confirmed 6.8 at maximum and MEDIUM impact
  • 2022-01-19 07:40 Begin mitigation for Grafana Cloud
  • 2022-01-19 17:00 CVE requested
  • 2022-01-19 19:50 GitHub issues CVE-2022-21703
  • 2022-01-21 10:50 PR with fix opened
  • 2022-01-21 14:13 Private release planned for 2022-01-25, and public release planned for 2022-02-01.
  • 2022-01-25 12:00 Private release
  • 2022-02-01 12:00 During the public release process, we realized that private 7.x release was incomplete. Abort public release, send second private release to customers using 7.x
  • 2022-02-08 12:00 Public release

Acknowledgement

We would like to thank jub0bs and abrahack for responsibly disclosing the vulnerability.

Reporting security issues

If you think you have found a security vulnerability, please send a report to [email protected]. This address can be used for all of Grafana Labs' open source and commercial products (including, but not limited to Grafana, Grafana Cloud, Grafana Enterprise, and grafana.com). We can accept only vulnerability reports at this address. We would prefer that you encrypt your message to us by using our PGP key. The key fingerprint is

F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA

The key is available from keyserver.ubuntu.com.

Security announcements

We maintain a security category on our blog, where we will always post a summary, remediation, and mitigation details for any patch containing security fixes.

You can also subscribe to our RSS feed.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/grafana/grafana/pkg/web≥ 3.0-beta1&&< 7.5.157.5.15go get github.com/grafana/grafana/pkg/web@v7.5.15
🐹Gogithub.com/grafana/grafana/pkg/web≥ 8.0.0&&< 8.3.58.3.5go get github.com/grafana/grafana/pkg/web@v8.3.5

Affected Products

3 products · 13 configurations
OS
fedorafedoraproject
3 versions
343536
Application
grafanagrafana
≥ 8.0.0 && < 8.3.5
1 version
3.0.0
Application
e-series performance analyzernetapp
< 3.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana/pkg/web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
Workaround published by Red Hat
Please refer to the Grafana upstream advisory for possible workarounds for this issue.
Source: Red Hat security advisory for CVE-2022-21703 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 8grafana-0:7.5.15-3.el8RHSA-2022:7519
Red Hat Enterprise Linux 9grafana-0:7.5.15-3.el9RHSA-2022:8057

Frequently Asked Questions

Today we are releasing Grafana 8.3.5 and 7.5.15. This patch release includes MEDIUM severity security fix for Cross Site Request Forgery for Grafana. Release v.8.3.5, only containing security fixes: - [Download Grafana 8.3.5](https://grafana.com/grafana/download/8.3.5) - [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-3-5/) Release v.7.5.15, only containing security fixes: - [Download Grafana 7.5.15](https://grafana.com/grafana/download/7.5.15) - [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-15/) ## CSRF ([CVE
O3 Security · Impact-Aware SCA

Is CVE-2022-21703 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-21703: web CSRF — Fixed in 7.5.15