CVE-2026-13720: Editor can forge file-provisioning provenance on dashboards via the dashboard API
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Grafana Grafana Enterprise 12.4.12, 13.0.10, 13.1.7; Grafana Grafana OSS 12.4.12, 13.0.10, 13.1.7.
Low priority for now. Upgrade to Grafana Grafana Enterprise 12.4.12, 13.0.10, 13.1.7; Grafana Grafana OSS 12.4.12, 13.0.10, 13.1.7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An Editor can set file-provisioning metadata (the grafana.app/managedBy, grafana.app/managerId and grafana.app/sourcePath annotations) when creating a dashboard through the dashboard API, because these fields were stored without an authorization check. The dashboard then appears file-provisioned, and administrators can no longer update or delete it through Grafana. The impact is limited to the same organization and no data is exposed.
- Published
- Sep 30, 2026
- Updated
- Sep 30, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-285
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GRAFANA
- 5.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GRAFANA). Independent of NVD's CPE analysis and usually ahead of it.
Grafana Grafana Enterprise
- 12.0.0 and later · up to and including 12.0.10affected · semver
- 12.1.0 and later · up to and including 12.1.10affected · semver
- 12.2.0 and later · up to and including 12.2.11affected · semver
- 12.3.0 and later · up to and including 12.3.11affected · semver
- 12.4.0 and later · before 12.4.12affected · semver
- 13.0.0 and later · before 13.0.10affected · semver
- 13.1.0 and later · before 13.1.7affected · semver
- 13.2.0 and later · before 13.2.3affected · semver
Grafana Grafana OSS
- 12.0.0 and later · up to and including 12.0.10affected · semver
- 12.1.0 and later · up to and including 12.1.10affected · semver
- 12.2.0 and later · up to and including 12.2.11affected · semver
- 12.3.0 and later · up to and including 12.3.11affected · semver
- 12.4.0 and later · before 12.4.12affected · semver
- 13.0.0 and later · before 13.0.10affected · semver
- 13.1.0 and later · before 13.1.7affected · semver
- 13.2.0 and later · before 13.2.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.24 | grafana | before 12.4.14-r0 | 12.4.14-r0 |
| Red Hat:hummingbird:1 | grafana12.4 | before 0:12.4.12-0.2.hum1 | 0:12.4.12-0.2.hum1 |
| Red Hat:hummingbird:1 | grafana13.1 | before 0:13.1.7-0.1.hum1 | 0:13.1.7-0.1.hum1 |
| Red Hat:hummingbird:1 | grafana13.2 | before 0:13.2.3-0.1.hum1 | 0:13.2.3-0.1.hum1 |
Same product
grafana: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-15815CVE-2026-15815 CVE Record35Monitor
- CVE-2026-33379Dashboard snapshot permission bypass34Monitor
- CVE-2026-76154CVE-2026-76154 CVE Record29Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-17033Aug 24, 2026 · CVE-2026-17033 CVE Record27Monitor
- ← EarlierCVE-2026-19197Aug 26, 2026 · Broken access control in dashboard snapshots25Monitor
- Later →CVE-2026-88858Oct 28, 2026 · Server-side expression parser denial of service26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Grafana Grafana Enterprise | 12.4.12 | Vendor (CNA) |
| Grafana Grafana Enterprise | 13.0.10 | Vendor (CNA) |
| Grafana Grafana Enterprise | 13.1.7 | Vendor (CNA) |
| Grafana Grafana Enterprise | 13.2.3 | Vendor (CNA) |
| Grafana Grafana OSS | 12.4.12 | Vendor (CNA) |
| Grafana Grafana OSS | 13.0.10 | Vendor (CNA) |
| Grafana Grafana OSS | 13.1.7 | Vendor (CNA) |
| Grafana Grafana OSS | 13.2.3 | Vendor (CNA) |
| alpine:grafana | 12.4.14-r0 · Alpine:v3.24 | Package registry (OSV) |
| red hat:grafana12.4 | 0:12.4.12-0.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:grafana13.1 | 0:13.1.7-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:grafana13.2 | 0:13.2.3-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 9, 2026+40 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- arang (Researcher)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-285 · Improper AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Bypassing ATA Password SecurityCAPEC-402
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
- Data from Local SystemT1005
- Query RegistryT1012
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Unsecured Credentials: Credentials in RegistryT1552.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Data Manipulation: Transmitted Data ManipulationT1565.002
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.