# CVE-2026-15815: CVE-2026-15815 CVE Record

> Attackers can achieve remote code execution by installing a crafted plugin archive that exploits symbolic link handling to write and execute arbitrary files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** ALSA-2026:83544, BIT-grafana-2026-15815, GHSA-xp8x-3q7w-cpqr, MINI-2w3q-6www-62p6, MINI-52q5-8q76-qc2w, MINI-5qcf-r26j-fqwq, MINI-6g2r-r28q-76pj, MINI-8mx3-cj6v-pm95, MINI-9gcx-7j57-342h, MINI-frfw-qwmx-j53r, MINI-gj74-g7f4-rfr6, MINI-hrhr-cmmh-7hr6, MINI-jg28-qrw2-723p, MINI-p76x-4f7x-p24c, MINI-qxw9-f979-3f6c, MINI-rqrm-qcrw-2hww, MINI-rwpq-6788-34h4, MINI-v8pc-7rfv-g6x5, MINI-wjq6-cvjx-wrcf, RHSA-2026:83544, RLSA-2026:83544

## What is CVE-2026-15815?

CVE-2026-15815 is a high-severity path traversal vulnerability in Grafana Enterprise, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-15815?

1 open source package ship an affected version, including grafana.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 11.6.0 | 12.0.1, 12.1.1, 12.2.1, 12.3.1, 12.4.11, 13.0.9, 13.1.6, 13.2.2 |
| `grafana` | AlmaLinux:8 | All versions | 9.2.10-35.el8_10 |
| `grafana-selinux` | AlmaLinux:8 | All versions | 9.2.10-35.el8_10 |
| `grafana` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9.2.10-35.el8_10 |
| `grafana-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9.2.10-35.el8_10 |
| `grafana-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9.2.10-35.el8_10 |
| `grafana-selinux` | Red Hat:enterprise_linux:8::appstream | All versions | 0:9.2.10-35.el8_10 |
| `grafana` | Rocky Linux:8 | All versions | 0:9.2.10-35.el8_10 |

## How do I fix CVE-2026-15815?

Upgrade grafana to a fixed version for your release line: 12.0.1, 12.1.1, 12.2.1 or 12.3.1.

## Is CVE-2026-15815 being exploited?

There is no known exploitation of CVE-2026-15815 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15815 and fix it if it is affected.

What it is: CVE-2026-15815 is a high-severity path traversal vulnerability in Grafana Enterprise, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15815 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 11.6.0; fixed in 12.0.1, 12.1.1, 12.2.1, 12.3.1, 12.4.11, 13.0.9, 13.1.6, 13.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15815/ (Markdown: https://insights.sbomify.com/CVE-2026-15815/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15815
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15815
- OSV: https://osv.dev/vulnerability/CVE-2026-15815

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15815/
Summaries are generated and may contain mistakes; the official description above is the record.