Daemon crash via unchecked XML nesting depth
Published Jul 14, 2025 · Updated Sep 1, 2026
Out-of-bounds write in polkit 126 and earlier allows local users with high privileges to crash polkitd via a deeply nested XML policy. The _start callback in polkitbackendactionpool.c advances fixed-depth parser state without rejecting a 32nd nested element, causing a write beyond its bounds. Exploitation requires permission to place a crafted policy in a monitored actions directory; code execution has not been demonstrated.
Summary
What happened
Out-of-bounds write in polkit 126 and earlier allows local users with high privileges to crash polkitd via a deeply nested XML policy. The _start callback in polkitbackendactionpool.c advances fixed-depth parser state without rejecting a 32nd nested element, causing a write beyond its bounds. Exploitation requires permission to place a crafted policy in a monitored actions directory; code execution has not been demonstrated.
The record
- CVE
- CVE-2025-7519
- Published
- Jul 14, 2025
- Updated
- Sep 1, 2026
- Vendor
- Libslirp Project
- Product
- Polkit
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jul 14, 2025CVE publishedPublication date reported by the CVE source.
- Sep 1, 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 <=126
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.
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