# CVE-2026-115371: Incus 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an improper authorization vulnerability that allows restricted


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115371, GHSA-6w4g-5qrv-grfx, GHSA-x8gj-2q73-qr6j, UBUNTU-CVE-2026-115371

## What is CVE-2026-115371?

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

### Official description

Incus 6.0.3 before 6.0.7, 6.6.0 before 7.0.2, and 7.1.0 before 7.5.0 contains an improper authorization vulnerability that allows restricted TLS clients to read storage bucket keys in the default project. Attackers can query the bucket keys endpoints to obtain S3 access and secret keys, then read, modify or delete objects in those buckets.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115371 is a high-severity vulnerability in lxc incus, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115371 in the wild and no public exploit code.

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

## Sources

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

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