CVE-2026-41163
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 · uneditedbubblewrap is a low-level unprivileged sandboxing tool. From version 0.11.0 to before version 0.11.2, if bubblewrap is installed in setuid mode then the user can use ptrace to attach to bubblewrap and control the unprivileged part of the sandbox setup phase. This allows the attacker to arbitrarily use the privileged operations, and in particular the "overlay mount" operation, allowing the creation of overlay mounts which is otherwise not allowed in the setuid version of bubblewrap. This issue has been patched in version 0.11.2.
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 · high confidenceIn bubblewrap versions 0.11.0 through 0.11.1, when installed in setuid mode, an attacker can use ptrace to attach to the bubblewrap process during the unprivileged sandbox setup phase. This allows control of otherwise restricted privileged operations, specifically enabling the creation of overlay mounts which are normally blocked in the setuid version.
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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check installed bubblewrap versionRun `bubblewrap --version` or `rpm -q bubblewrap` (RHEL) or `dpkg -l bubblewrap` (Debian)Affected if version is below 0.11.2
-
Verify if bubblewrap binary has setuid bit setRun `ls -l $(which bubblewrap)` and look for 's' in the owner execute field (e.g., `-rwsr-xr-x`)Affected if the setuid bit ('s') is present in the owner permissions
-
Confirm setuid binary locationRun `stat $(which bubblewrap)` and check the Setuid attribute in the outputAffected if the Setuid file attribute is set
-
Check running bubblewrap processes in setuid contextRun `ps aux | grep bubblewrap` to see if any setuid bubblewrap instances are activeAffected if any bubblewrap process is running with setuid privileges
You are affected if bubblewrap version is below 0.11.2 AND the setuid bit is enabled on the bubblewrap binary, as the vulnerability only applies to setuid mode during the unprivileged sandbox setup phase.
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.
dbcve · scopedUpgrade bubblewrap to version 0.11.2 or later to receive the security patch.
bubblewrap version 0.11.2 or later
- Check the current installed version of bubblewrap (e.g., `bwrap --version` or `rpm -q bubblewrap`)
- Upgrade bubblewrap to version 0.11.2 or later using your system's package manager (e.g., `dnf update bubblewrap` or `apt-get update && apt-get install bubblewrap`)
- Verify the new version is installed and is 0.11.2 or later
- If bubblewrap is installed in setuid mode, confirm the patch is applied by checking release notes or verifying ptrace restrictions are in place
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41163 — 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-41163 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