Privileged file reads via external entity expansion
Published Jun 18, 2026 · Updated Jun 18, 2026
XML external entity processing in mcdope pam_usb before 0.9.2 allows local users to read files or initiate network connections. The pusb_conf_parse() function in src/conf.c passes flags=0 to xmlReadFile(), leaving libxml2 free to resolve local and network entity URIs. Exploitation requires write access to root-owned /etc/pamusb.conf; parsing occurs inside an authenticating sudo or su process, so entity access inherits that privileged context.
Summary
What happened
XML external entity processing in mcdope pam_usb before 0.9.2 allows local users to read files or initiate network connections. The pusb_conf_parse() function in src/conf.c passes flags=0 to xmlReadFile(), leaving libxml2 free to resolve local and network entity URIs. Exploitation requires write access to root-owned /etc/pamusb.conf; parsing occurs inside an authenticating sudo or su process, so entity access inherits that privileged context.
The record
- CVE
- CVE-2026-48981
- Published
- Jun 18, 2026
- Updated
- Jun 18, 2026
- Vendor
- mcdope
- Product
- pam_usb
- Classifications
- CWE-611, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 18, 2026CVE publishedPublication date reported by the CVE source.
- Jun 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.9.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo