CVE-2025-8341 is a medium-severity (CVSS 5) Server-Side Request Forgery (SSRF) vulnerability in github.com/grafana/grafana-infinity-datasource. A fix is available for github.com/grafana/grafana-infinity-datasource — see the affected versions and patch details below.
SSRF in Infinity Datasource Plugin
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-2025-8341.
EPSS Exploitation Probability
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
github.com/grafana/grafana-infinity-datasourceReal-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. The Infinity datasource plugin, maintained by Grafana Labs, allows visualizing data from JSON, CSV, XML, GraphQL, and HTML endpoints.
If the plugin was configured to allow only certain URLs, an attacker could bypass this restriction using a specially crafted URL. This vulnerability is fixed in version 3.4.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/grafana-infinity-datasource | all versions | 1.4.2-0.20250731100004-9c736aa21b3ago get github.com/grafana/grafana-infinity-datasource@v1.4.2-0.20250731100004-9c736aa21b3a |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/grafana-infinity-datasource, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/grafana-infinity-datasource to 1.4.2-0.20250731100004-9c736aa21b3a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-8341 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
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.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-8341 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-8341 in your dependencies?
Find it across Go, including transitive dependencies.