# CVE-2026-9765: CVE-2026-9765 CVE Record

> Attackers can bypass access controls in Grafana IRM to access unauthorized resources, read sensitive data, or take over accounts.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-4cgr-9q8v-9x3m

## What is CVE-2026-9765?

CVE-2026-9765 is a high-severity missing authorization vulnerability in Grafana IRM, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Note: The CVE and blog post don't exist because we determined this is actually a cloud-only issue.

Access Controls are “Broken” when a user can access resources they are not authorized to access. An attacker can bypass any access control mechanisms in a web application, and gain unauthorized access to resources that are not available with their permissions. 

Broken access control can allow attackers to:
Access resources only accessible to certain users, thus allowing unauthorized access to data
Perform operations on behalf of other users, leading to account takeovers in the worst cases
Attempt privilege escalation
Attempt to take over an account

Weakness: CWE-284 (Improper Access Control)

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


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

Apply the vendor's patch.

## Is CVE-2026-9765 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9765 is a high-severity missing authorization vulnerability in Grafana IRM, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9765 in the wild and no public exploit code.

Affected product: Grafana IRM. 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-9765/ (Markdown: https://insights.sbomify.com/CVE-2026-9765/index.md)
```

## Sources

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

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