CVE-2026-15815: CVE-2026-15815 CVE Record
Noroxi assessment
Priority: Monitor (action score 35/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.68% (FIRST EPSS); higher than 52.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: grafana (AlmaLinux:8) 9.2.10-35.el8_10; grafana-selinux (AlmaLinux:8) 9.2.10-35.el8_10; grafana (Alpine:v3.24) 12.4.14-r0.
Low priority for now. Upgrade to grafana (AlmaLinux:8) 9.2.10-35.el8_10; grafana-selinux (AlmaLinux:8) 9.2.10-35.el8_10; grafana (Alpine:v3.24) 12.4.14-r0 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
Grafana OSS and Grafana Enterprise did not safely resolve symbolic links when extracting plugin archives. A crafted plugin archive can chain relative symbolic link entries to escape the plugin installation directory, writing arbitrary files and an executable backend binary outside that directory. The dropped executable runs with the privileges of the Grafana server process, resulting in remote code execution. Plugin archives are extracted before their signature is verified, so a valid plugin signature does not prevent the write. An operator can therefore be affected by installing a plugin that appears legitimate, as well as by installing a plugin from an arbitrary archive using grafana-cli, the GF_INSTALL_PLUGINS environment variable, or preinstall configuration. Grafana Enterprise is affected because it includes the same plugin extraction code as Grafana OSS.
- Published
- Sep 17, 2026
- Updated
- Sep 19, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-22
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GRAFANA
- 8.8
- 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, 12.1.0, 12.2.0, 12.3.0affected
- 11.6.0 and later · up to and including 11.6.17affected · semver
- 12.4.0 and later · up to and including 12.4.10affected · semver
- 13.0.0 and later · up to and including 13.0.8affected · semver
- 13.1.0 and later · up to and including 13.1.5affected · semver
- 13.2.0 and later · up to and including 13.2.1affected · semver
Grafana Grafana OSS
- 12.0.0, 12.1.0, 12.2.0, 12.3.0affected
- 11.6.0 and later · up to and including 11.6.17affected · semver
- 12.4.0 and later · up to and including 12.4.10affected · semver
- 13.0.0 and later · up to and including 13.0.8affected · semver
- 13.1.0 and later · up to and including 13.1.5affected · semver
- 13.2.0 and later · up to and including 13.2.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | grafana | before 9.2.10-35.el8_10 | 9.2.10-35.el8_10 |
| AlmaLinux:8 | grafana-selinux | before 9.2.10-35.el8_10 | 9.2.10-35.el8_10 |
| Alpine:v3.24 | grafana | before 12.4.14-r0 | 12.4.14-r0 |
| openSUSE:Tumbleweed | grafana | before 12.4.11-1.1 | 12.4.11-1.1 |
| Red Hat:enterprise_linux:8::appstream | grafana | before 0:9.2.10-35.el8_10 | 0:9.2.10-35.el8_10 |
| Red Hat:enterprise_linux:8::appstream | grafana-debuginfo | before 0:9.2.10-35.el8_10 | 0:9.2.10-35.el8_10 |
| Red Hat:enterprise_linux:8::appstream | grafana-debugsource | before 0:9.2.10-35.el8_10 | 0:9.2.10-35.el8_10 |
| Red Hat:enterprise_linux:8::appstream | grafana-selinux | before 0:9.2.10-35.el8_10 | 0:9.2.10-35.el8_10 |
| Rocky Linux:8 | grafana | before 0:9.2.10-35.el8_10 | 0:9.2.10-35.el8_10 |
Same product
grafana: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-33379Dashboard snapshot permission bypass34Monitor
- CVE-2026-76154CVE-2026-76154 CVE Record29Monitor
- CVE-2026-17183CVE-2026-17183 CVE Record28Monitor
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-13720Sep 30, 2026 · Editor can forge file-provisioning provenance on dashboards via the dashboard API21Monitor
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 |
|---|---|---|
| almalinux:grafana | 9.2.10-35.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:grafana-selinux | 9.2.10-35.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| alpine:grafana | 12.4.14-r0 · Alpine:v3.24 | Package registry (OSV) |
| opensuse:grafana | 12.4.11-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:grafana | 0:9.2.10-35.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-debuginfo | 0:9.2.10-35.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-debugsource | 0:9.2.10-35.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:grafana-selinux | 0:9.2.10-35.el8_10 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:grafana | 0:9.2.10-35.el8_10 · Rocky Linux:8 | 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.
No dated events beyond publication.
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.
No credits in the CNA record.
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.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);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)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.