CVE-2025-10729

CRITICALNVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-32489 (ENISA EUVD) · GHSA-cprv-rgr4-v7vh (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The module will parse a node which is not a child of a structural node. The node will be deleted after creation but might be accessed later leading to a use after free.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 3, 2025

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
Patch available.

Vendor Advisories for CVE-2025-10729(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatqt6-qtsvg-0:6.9.1-2.el10_1.12025-11-11redhat
redhatqt6-qtsvg-0:6.8.1-1.el10_0.12025-11-05redhat

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

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
qt6-svg6.10.2-1 ... 6.9.2-5 (35 versions)
  • every version on: no fix on record
—
qtsvg-opensource-src5.15.10-1 ... 5.15.9-1 (15 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
qt6-svg6.10.2-1 ... 6.9.2-5 (19 versions)
  • every version on: no fix on record
—
qtsvg-opensource-src5.15.15-2 ... 5.15.19-2 (7 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
qt6-svg6.10.2-1 ... 6.9.2-5 (12 versions)
  • every version up to 6.10.2-5: fixed in 6.10.2-5
—
qtsvg-opensource-src5.15.15-2 ... 5.15.19-2 (7 versions)
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
qtsvg-opensource-src5.15.10-1 ... 5.15.9-1 (27 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 28× in last 7d / 101× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 298 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 198 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 07:49 UTCEG score recompute
  2. 2026-11-02 07:49 UTCVendor advisory
  3. 2026-11-02 07:49 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  4. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-11-01 08:14 UTCEG score recompute
  6. 2026-11-01 08:14 UTCVendor advisory
  7. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  8. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-31 08:39 UTCEG score recompute
  10. 2026-10-31 08:39 UTCVendor advisory
  11. 2026-10-31 08:39 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  12. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-30 09:04 UTCEG score recompute
  14. 2026-10-30 09:04 UTCVendor advisory
  15. 2026-10-30 09:03 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  16. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-29 09:29 UTCEG score recompute
  18. 2026-10-29 09:29 UTCVendor advisory
  19. 2026-10-29 09:29 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  20. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-28 09:53 UTCEG score recompute
  22. 2026-10-28 09:53 UTCVendor advisory
  23. 2026-10-28 09:53 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  24. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-27 09:27 UTCEG score recompute
Show 75 more
  1. 2026-10-27 09:27 UTCVendor advisory
  2. 2026-10-27 09:27 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  3. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-26 09:46 UTCVendor advisory
  5. 2026-10-26 09:46 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  6. 2026-10-25 16:49 UTCEG score recompute
  7. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-25 10:11 UTCEG score recompute
  9. 2026-10-25 10:11 UTCVendor advisory
  10. 2026-10-25 10:11 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-10-24 10:35 UTCEG score recompute
  13. 2026-10-24 10:35 UTCVendor advisory
  14. 2026-10-24 10:35 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-23 11:00 UTCEG score recompute
  17. 2026-10-23 11:00 UTCVendor advisory
  18. 2026-10-23 11:00 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  19. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-22 11:24 UTCEG score recompute
  21. 2026-10-22 11:24 UTCVendor advisory
  22. 2026-10-22 11:24 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  23. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-21 11:49 UTCEG score recompute
  25. 2026-10-21 11:49 UTCVendor advisory
  26. 2026-10-21 11:49 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  27. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-10-20 12:15 UTCEG score recompute
  29. 2026-10-20 12:15 UTCVendor advisory
  30. 2026-10-20 12:15 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  31. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-10-19 12:37 UTCEG score recompute
  33. 2026-10-19 12:37 UTCVendor advisory
  34. 2026-10-19 12:37 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  35. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-10-18 10:57 UTCVendor advisory
  37. 2026-10-18 10:56 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  38. 2026-10-18 05:52 UTCEG score recompute
  39. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-10-17 08:07 UTCEG score recompute
  41. 2026-10-17 08:07 UTCVendor advisory
  42. 2026-10-17 08:07 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  43. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-10-16 08:31 UTCEG score recompute
  45. 2026-10-16 08:31 UTCVendor advisory
  46. 2026-10-16 08:31 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  47. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-10-15 07:40 UTCEG score recompute
  49. 2026-10-15 07:40 UTCVendor advisory
  50. 2026-10-15 07:40 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  51. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-10-14 03:37 UTCEG score recompute
  53. 2026-10-14 03:37 UTCVendor advisory
  54. 2026-10-14 03:37 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  55. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-10-12 23:34 UTCVendor advisory
  57. 2026-10-12 23:34 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  58. 2026-10-12 17:27 UTCEG score recompute
  59. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  60. 2026-10-12 12:39 UTCVendor advisory
  61. 2026-10-12 12:38 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  62. 2026-10-11 20:57 UTCEG score recompute
  63. 2026-10-11 19:07 UTCEG score recompute
  64. 2026-10-11 15:48 UTCEG score recompute
  65. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  66. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  68. 2026-10-08 22:23 UTCEG score recompute
  69. 2026-10-08 22:23 UTCVendor advisory
  70. 2026-10-08 22:23 UTCGHSA enrichmentGHSA-cprv-rgr4-v7vh · GitHub severity CRITICAL
  71. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  72. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  73. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  74. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  75. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 11th percentile

Frequently asked(5)

What is CVE-2025-10729?
CVE-2025-10729 is a critical-severity vulnerability; its CVE record was published on October 3, 2025. The module will parse a <pattern> node which is not a child of a structural node. The node will be deleted after creation but might be accessed later leading to a use after free.
When was CVE-2025-10729 made public?
CVE-2025-10729 was made public on October 3, 2025: that is the date its CVE record's CNA, TQtC, gives for when the vulnerability was made public. The CVE record itself was published on October 3, 2025. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2025-10729 actively exploited?
CVE-2025-10729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-10729?
CVE-2025-10729 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2025-10729?
A fix for CVE-2025-10729 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-10729 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-10729

Explore →

Is Your Infrastructure Affected by CVE-2025-10729?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.