CVE-2025-11539
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 · uneditedGrafana Image Renderer is vulnerable to remote code execution due to an arbitrary file write vulnerability. This is due to the fact that the /render/csv endpoint lacked validation of the filePath parameter that allowed an attacker to save a shared object to an arbitrary location that is then loaded by the Chromium process. Instances are vulnerable if: 1. The default token ("authToken") is not changed, or is known to the attacker. 2. The attacker can reach the image renderer endpoint. This issue affects grafana-image-renderer: from 1.0.0 through 4.0.16.
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 · high confidenceThe grafana-image-renderer /render/csv endpoint lacks validation of the filePath parameter, allowing an attacker to write arbitrary shared objects to any location on the filesystem. These objects are subsequently loaded by the Chromium process, enabling remote code execution. Exploitation requires either the default authToken to remain unchanged or be known to the attacker, plus network access to the renderer endpoint.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if grafana-image-renderer is installedCheck for the grafana-image-renderer package via npm list @grafana/image-renderer, pip list grafana-image-renderer, or equivalent package manager; also inspect Grafana plugin directory for the image-renderer pluginAffected if The renderer plugin is present in the environment
-
Determine renderer versionRun version command for the installed package (npm list @grafana/image-renderer version, pip show grafana-image-renderer, or check package.json)Affected if Running any unpatched version of the image renderer with the /render/csv endpoint enabled
-
Check if /render/csv endpoint is accessibleReview renderer service configuration and routing to confirm the /render/csv endpoint exists and is enabled; inspect the rendered API routes or middleware configurationAffected if The /render/csv endpoint is enabled in the configuration
-
Verify authToken configuration statusExamine renderer configuration files (defaults.ini, custom.ini, grafana.ini, or environment variables GRAFANA_IMAGE_RENDERER_AUTH_TOKEN) to determine if authToken is set to the default value or a custom strong valueAffected if authToken is unchanged from default or is missing/unset
-
Assess network accessibility of rendererReview firewall rules, reverse proxy configuration, and service binding (listen address) to determine if the renderer endpoint is exposed to untrusted network segmentsAffected if Renderer service is accessible from non-localhost networks without proper access controls
Environment is affected if grafana-image-renderer is installed, the /render/csv endpoint is enabled, and either the authToken remains at default or the renderer is network-accessible to attackers
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately change the default authToken to a strong, unique value and restrict network access to the image renderer endpoint. Additionally, upgrade to a patched version once available.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
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 locallyCheck whether your project pulls in CVE-2025-11539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11539 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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