# CVE-2026-103506: SSO settings authorization bypass


- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-qr52-42rj-4mw4, UBUNTU-CVE-2026-103506

## What is CVE-2026-103506?

CVE-2026-103506 is a high-severity vulnerability in Grafana Enterprise, published on 28 Oct 2026. 

### Official description

An authenticated user in Grafana can read SSO client secrets and modify instance-wide SSO settings without the required permissions (missing authorization). This affects Grafana OSS and Enterprise 13.2 installations with the experimental kubernetesSsoSettingsApi feature toggle enabled, which is disabled by default.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-103506 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103506 is a high-severity vulnerability in Grafana Enterprise, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-103506 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-103506/ (Markdown: https://insights.sbomify.com/CVE-2026-103506/index.md)
```

## Sources

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

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