CVE-2026-11853 Overview
CVE-2026-11853 affects Debusine, an integrated solution to build, distribute, and maintain a Debian-based distribution. The vulnerability resides in the parser that reads Debian source packages (.dsc) and upload artifacts (.changes). These manifest files name the files that make up an artifact. The parser accepts arbitrary fully user-controlled paths without validation. Attackers can abuse the mergeuploads task to create arbitrary symbolic links on a worker, overwriting any file accessible to the worker user. The flaw is tracked as a link following weakness [CWE-59].
Critical Impact
Attackers can create arbitrary symbolic links on Debusine workers, enabling overwrites of any file accessible to the worker user account.
Affected Products
- Debusine (Freexian team distribution build platform)
- Debian-based distribution build infrastructure relying on Debusine workers
- Deployments processing untrusted .dsc or .changes artifacts
Discovery Timeline
- 2026-06-10 - CVE-2026-11853 published to the National Vulnerability Database (NVD)
- 2026-06-10 - Last updated in NVD database
Technical Details for CVE-2026-11853
Vulnerability Analysis
Debusine processes Debian source packages and upload artifacts that act as manifest files. Each manifest enumerates the files that compose the artifact. The parser does not constrain or sanitize the file paths declared inside these manifests. As a result, fully user-controlled paths reach file system operations performed by a worker.
The mergeuploads task consumes these parsed paths during artifact processing. An attacker who supplies a crafted .dsc or .changes manifest can direct the worker to create symbolic links at attacker-chosen locations. The resulting symlinks can target arbitrary files on the worker host. Subsequent write operations follow the symlinks and overwrite files owned by the worker user.
The issue is classified under [CWE-59] (Improper Link Resolution Before File Access). Exploitation requires no authentication, no user interaction, and is reachable over the network through the artifact submission flow.
Root Cause
The root cause is missing validation of file path components inside .dsc and .changes manifest entries. The parser treats all declared paths as trusted input. There is no enforcement that paths remain within an expected working directory and no check that targets are not symbolic links.
Attack Vector
An attacker submits a crafted Debian source package or upload artifact whose manifest references absolute or traversal-laden paths. When the mergeuploads task processes the artifact, the worker creates symlinks at the attacker-controlled locations. The attacker can then overwrite configuration files, build outputs, or any other file writable by the worker user.
No verified exploit code is published. Technical details and the corrective patch are available in the Debian Commit Update and the Debian Merge Request 3103.
Detection Methods for CVE-2026-11853
Indicators of Compromise
- Unexpected symbolic links inside Debusine worker working directories or scratch paths used by the mergeuploads task.
- .dsc or .changes manifests that reference absolute paths or paths containing .. traversal sequences.
- Modifications to files owned by the worker user that do not correspond to legitimate build outputs.
Detection Strategies
- Audit Debusine task logs for mergeuploads invocations that process artifacts originating from untrusted submitters.
- Inspect parsed manifest entries and flag any path that is not a simple basename within the artifact directory.
- Compare worker file system state before and after artifact ingestion to identify newly created symlinks.
Monitoring Recommendations
- Enable file integrity monitoring on Debusine worker hosts, focused on the worker user's writable paths and configuration files.
- Alert on creation of symbolic links by worker processes outside expected build sandboxes.
- Forward worker process and file system telemetry to a centralized analytics platform for retrospective hunting against the indicators above.
How to Mitigate CVE-2026-11853
Immediate Actions Required
- Upgrade Debusine to a release that includes the fix from commit c24cdc4.
- Restrict artifact submission to authenticated and trusted users until the patch is deployed.
- Review worker user permissions and remove write access to any path the worker does not need.
Patch Information
The Freexian team addressed the issue by validating manifest paths in the .dsc and .changes parser. Details are tracked in Debian Work Item #1484 and merged through Merge Request 3103. Operators should pull the latest Debusine packages and restart worker services after applying the update.
Workarounds
- Run Debusine workers under a dedicated low-privilege user with no access to sensitive host files.
- Execute the mergeuploads task inside an isolated filesystem namespace, container, or chroot to contain symlink targets.
- Reject artifact submissions whose manifests contain absolute paths, .. components, or non-basename file references at an ingress proxy or pre-processing step.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

