dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-8341

MEDIUM · 5.0 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Grafana Infinity datasource plugin versions before 3.4.1 contain a URL allowlist bypass vulnerability. When configured to restrict requests to specific URLs, an attacker can use a specially crafted URL to bypass this restriction and cause the plugin to query unauthorized endpoints.

MitigationUpgrade the Infinity datasource plugin to version 3.4.1 or later. After upgrading, verify that URL restrictions function correctly and test with crafted URLs to confirm the bypass is no longer possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Grafana Infinity datasource plugin is installed
    Access Grafana via UI: Navigate to Configuration > Plugins, or use the Grafana CLI: grafana-cli plugins ls. Look for 'Infinity datasource' in the plugin list.
    Affected if The Infinity datasource plugin appears in the installed plugins list.
  2. Determine the installed version of the Infinity datasource plugin
    In Grafana UI: Go to Configuration > Plugins, find Infinity datasource, and note the version displayed. If using CLI: grafana-cli plugins version-override <plugin-id> or check the plugin's manifest file in the Grafana plugins directory.
    Affected if The version shown is any version prior to 3.4.1 (for example: 3.4.0, 3.3.0, 3.2.1, etc.).
  3. Verify whether URL allowlist restrictions are configured
    In Grafana UI: Navigate to Configuration > Data Sources, select the Infinity datasource, and inspect the settings for any URL restriction, allowlist, or approved URLs configuration. Look for fields such as 'Allowed URLs', 'URL Restrictions', or 'Approved Endpoints'.
    Affected if URL allowlist or URL restriction settings are defined, indicating the plugin is configured to limit outbound requests.
  4. Confirm the bypass condition applies
    This vulnerability is present when BOTH conditions are true: (1) the Infinity plugin version is before 3.4.1, AND (2) URL allowlist restrictions are enabled. There is no specific command to test the bypass without potential security risk; the mere presence of both conditions indicates potential exposure.
    Affected if The plugin version is below 3.4.1 AND URL allowlist restrictions are actively configured in the datasource settings.

A user is affected if the Grafana Infinity datasource plugin version is 3.4.0 or earlier AND the URL allowlist restriction feature is enabled in the datasource configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Infinity datasource plugin to version 3.4.1 or later. After upgrading, verify that URL restrictions function correctly and test with crafted URLs to confirm the bypass is no longer possible.

Recommended fix Moderate confidence

Infinity datasource plugin version 3.4.1

  1. 1. Identify all Grafana instances running the Infinity datasource plugin.
  2. 2. Check the current version of the Infinity datasource plugin installed on each Grafana instance.
  3. 3. If the installed version is earlier than 3.4.1, upgrade the plugin to version 3.4.1 or later.
  4. 4. In Grafana, this can typically be done through the UI: Configuration > Plugins > Infinity > Update, or via the Grafana CLI: grafana-cli plugins update infinity.
  5. 5. After upgrading, verify the plugin version is 3.4.1 or higher.
  6. 6. Test that URL allowlist restrictions work correctly with the updated plugin version.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8341 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8341 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data