# CVE-2026-11852: Missing authorization in debusine

> Attackers can create or delete artifact relationships in Debusine without proper permission checks, allowing unauthorized modification of distribution data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-11852, GHSA-2wmq-wq3w-j93h, UBUNTU-CVE-2026-11852

## What is CVE-2026-11852?

CVE-2026-11852 is a medium-severity missing authorization vulnerability in Debian debusine, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Debusine is an integrated solution to build, distribute and maintain a Debian-based distribution. Files managed by debusine are organized into artifacts. The endpoints that create and delete relationships between artifacts enforced no permissions checks beyond being able to see the artifacts in question.

Weakness: CWE-862 (Missing Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-11852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11852 is a medium-severity missing authorization vulnerability in Debian debusine, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11852 in the wild and no public exploit code.

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

## Sources

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

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