# CVE-2026-16491: CVE-2026-16491 CVE Record


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-6xjg-5qmq-rh74

## What is CVE-2026-16491?

CVE-2026-16491 is a medium-severity vulnerability in Grafana Enterprise, published on 27 Oct 2026. 

### Official description

Grafana’s RBAC service ignored the requested folder when checking whether a user was a folder administrator for deleted dashboard listings. A user with dashboard permission-management rights on any folder could therefore be treated as an administrator of every folder.

This could expose deleted dashboard items from folders where the user lacked administrative access. The fix requires permission on the specified folder, an ancestor, or a wildcard scope.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-16491 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16491 is a medium-severity vulnerability in Grafana Enterprise, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-16491 in the wild and no public exploit code.

Affected product: Grafana Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-16491/ (Markdown: https://insights.sbomify.com/CVE-2026-16491/index.md)
```

## Sources

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

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