CVE-2026-11853
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDebusine is an integrated solution to build, distribute and maintain a Debian-based distribution. Debian source packages (.dsc) and upload artifacts (.changes) are manifest files that name the files that make up the artifact. The parser used to read these files in Debusine accepted arbitrary fully user-controlled paths. The mergeuploads task could be abused to create arbitrary symbolic links on a worker, overwriting any file that the worker user has access to.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDebusine's parser for Debian source packages (.dsc) and upload artifacts (.changes) accepts arbitrary fully user-controlled paths without validation. The mergeuploads task can be abused to create arbitrary symbolic links on a worker host, enabling an attacker to overwrite any file accessible to the worker user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Debusine installationRun command: which debusine or pip list | grep -i debusine to locate the debusine binary or packageAffected if Debusine is not installed on the system
-
Check Debusine versionRun: debusine --version or python -c "import debusine; print(debusine.__version__)" to obtain the installed version numberAffected if The installed version matches or predates the version where path validation was added (compare to vendor advisory for fixed version)
-
Verify worker mode is enabledCheck configuration files in /etc/debusine/ or ~/.config/debusine/ for worker-related settings; look for [worker] section or worker-specific task configurationsAffected if Debusine worker mode is configured and the system acts as a build worker
-
Inspect mergeuploads task configurationSearch for mergeuploads task definitions in /etc/debusine/tasks/ or within task configuration files; check if mergeuploads is listed as an enabled taskAffected if The mergeuploads task is enabled in the worker's task list
-
Check for symbolic link creation in upload processingReview Debusine logs or source code for .dsc and .changes file parsing behavior; look for symlink() calls without path validation in the mergeuploads moduleAffected if The system processes .dsc/.changes files through mergeuploads without validated path sanitization
A system is affected if it runs Debusine as a worker that processes .dsc and .changes files via the mergeuploads task, allowing arbitrary path symlink creation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict path validation and sanitization for .dsc and .changes file parsing, restricting paths to expected directories. Additionally, add controls to prevent symbolic link creation in mergeuploads or limit symlink targets to safe locations.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11853 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data