CVE-2026-44711 pam_usb: Symlink attacks on pad directory and pad files enable authentication bypass and root file corruption
High 7.9
Published
Updated
Check this codebase for CVE-2026-44711 and fix it if it is affected.
What it is: CVE-2026-44711 is a high-severity vulnerability in mcdope pam_usb, published on 27 May 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44711 exists.
Affected product: mcdope pam_usb. 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-44711/ (Markdown: https://insights.sbomify.com/CVE-2026-44711/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-44711?
CVE-2026-44711 is a high-severity vulnerability in mcdope pam_usb, published on 27 May 2026.
Official description
pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.8.7, symlink attacks on pad directory and pad files enable authentication bypass and root file corruption. This vulnerability is fixed in 0.8.7.
Which versions are affected by CVE-2026-44711?
How do I fix CVE-2026-44711?
No fix has been published for CVE-2026-44711 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-44711 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44711 exists.