Quick answers
- Is CVE-2026-11852 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11852 being exploited in the wild.
- How severe is CVE-2026-11852?
- Informational severity, with a CVSS score of 5.3, published 10 June 2026.
- Which products and versions are affected?
- Debian Debusine Fixed in commit 98104f46dc546a27a0326d5ef728ac7f426c430a.
- Is there a fix for CVE-2026-11852?
- A patch was published on 2026-03-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11852 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-11852?
- Check whether you run Debian Debusine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A broken access control vulnerability existed in Debusine's artifact relation management. The endpoints for creating and deleting relationships between artifacts only verified 'can_display' (read-only) permissions. Consequently, any user (including anonymous users) who could view an artifact could also create or delete its relationships to other visible artifacts. This could be exploited to manipulate workflows that rely on artifact relationships to locate files for processing. The issue was addressed by implementing 'can_delete' and 'can_create_artifacts' permission checks, requiring appropriate workspace roles (e.g., OWNER) for these actions.
Affected products
- Debian Debusine Fixed in commit 98104f46dc546a27a0326d5ef728ac7f426c430a
Timeline
- 2026-03-11: other: Merge request created to fix the issue
- 2026-03-12: patched: Fix committed to repository
- 2026-06-10: disclosed: CVE published