# CVE-2026-115373: Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 Authorization Bypass via GET /1.0/operations/{uuid}


- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115373, GHSA-mfwv-x733-9446, GHSA-xv35-979f-75jf, UBUNTU-CVE-2026-115373

## What is CVE-2026-115373?

CVE-2026-115373 is a high-severity vulnerability in lxc incus, published on 22 Oct 2026. 

### Official description

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a missing authorization vulnerability in GET /1.0/operations/{uuid} that lets project-restricted clients read operations in other projects. Attackers holding a restricted certificate and a known operation UUID can retrieve command lines, environment secrets, websocket secrets, and trust enrolment tokens.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115373 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115373 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115373 is a high-severity vulnerability in lxc incus, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115373 exists.

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

## Sources

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

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