A flaw was found in polkit. When processing an XML policy with 32 or more nested elements in depth, an out-of-bounds write can be triggered. This issue can lead to a crash or other unexpected behavior, and arbitrary code execution is not discarded. To exploit this flaw, a high-privilege account is needed as it's required to place the malicious policy file properly.
CVE-2025-7519
Score 6.7 from GitHub Security Advisory published 2025-07-14. a secondary CVSS source baseline 6.7; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.7
- EG Score
- 6.7(medium)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity67% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
July 14, 2025
Last Modified
September 1, 2026
Advisory Details (4)
Auto-updated Jun 25, 2026Nested .policy files cause xml parsing overflow leading to crash
Patch available: polkit-org/polkit 127 (PR #570 merged 2025-07-05)
https://github.com/polkit-org/polkit/pull/570commit 107d3801361b (polkit-org/polkit)
Patch available: polkit-org/polkit 127 (contains commit 107d3801361b)
https://github.com/polkit-org/polkit/commit/107d3801361b9f9084f78710178e683391f1d2452379675 – (CVE-2025-7519) CVE-2025-7519 polkit: XML policy file with a large number of nested elements may lead to out-of-bounds write
https://bugzilla.redhat.com/show_bug.cgi?id=2379675Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | polkitd (126-2ubuntu0.1) @ questing | 2026-09-01 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policykit-1 | 0.105-31 ... 127-3 (64 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policykit-1 | 122-3 ... 127-3 (15 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policykit-1 | 126-2, 127-1, 127-2, 127-3 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policykit-1 | 126-2 | 127-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(2)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 7× in last 7d / 37× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 167 total refreshes for this CVE.
- 2026-09-20 20:15 UTCEPSS rescore
- 2026-09-20 09:03 UTCOSV refresh
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 03:10 UTCEPSS rescore
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 12:31 UTCEG score recompute
- 2026-09-01 12:31 UTCVendor advisory
- 2026-09-01 12:30 UTCGHSA enrichment
- 2026-09-01 11:57 UTCEG score recompute
- 2026-09-01 11:57 UTCVendor advisory
- 2026-09-01 11:57 UTCGHSA enrichment
- 2026-08-31 16:43 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-31 16:43 UTCVendor advisory
- 2026-08-31 16:43 UTCGHSA enrichment
- 2026-08-31 15:09 UTCEG score recompute
- 2026-08-31 15:09 UTCVendor advisory
- 2026-08-31 15:09 UTCGHSA enrichment
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 14:16 UTCEPSS rescore
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 12:20 UTCEG score recompute
- 2026-08-21 12:20 UTCVendor advisory
- 2026-08-21 12:20 UTCGHSA enrichment
- 2026-08-21 12:15 UTCEG score recompute
- 2026-08-21 12:15 UTCVendor advisory
- 2026-08-21 12:15 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 01:50 UTCOSV refresh
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-07 16:27 UTCEPSS rescore
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 10:37 UTCEPSS rescore
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 01:11 UTCOSV refresh
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:03 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:59 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 19:19 UTCOSV refresh
Related CVEs(same vendor + same CWE)
Same CWE
10 shownCWE-787
Frequently asked(5)
What is CVE-2025-7519?
When was CVE-2025-7519 disclosed?
Is CVE-2025-7519 actively exploited?
What is the CVSS score of CVE-2025-7519?
How do I remediate CVE-2025-7519?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-7519
Is Your Infrastructure Affected by CVE-2025-7519?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.