CVE-2025-21729

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-5218 (ENISA EUVD) · GHSA-pc9x-vqhx-p2xg (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
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: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion

The rtwdev->scanning flag isn't protected by mutex originally, so cancel_hw_scan can pass the condition, but suddenly hw_scan completion unset the flag and calls ieee80211_scan_completed() that will free local->hw_scan_req. Then, cancel_hw_scan raises null-ptr-deref and use-after-free. Fix it by moving the check condition to where protected by mutex.

KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f] CPU: 2 PID: 6922 Comm: kworker/2:2 Tainted: G OE Hardware name: LENOVO 2356AD1/2356AD1, BIOS G7ETB6WW (2.76 ) 09/10/2019 Workqueue: events cfg80211_conn_work [cfg80211] RIP: 0010:rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core] Code: 00 45 89 6c 24 1c 0f 85 23 01 00 00 48 8b 85 20 ff ff ff 48 8d RSP: 0018:ffff88811fd9f068 EFLAGS: 00010206 RAX: dffffc0000000000 RBX: ffff88811fd9f258 RCX: 0000000000000001 RDX: 0000000000000011 RSI: 0000000000000001 RDI: 0000000000000089 RBP: ffff88811fd9f170 R08: 0000000000000000 R09: 0000000000000000 R10: ffff88811fd9f108 R11: 0000000000000000 R12: ffff88810e47f960 R13: 0000000000000000 R14: 000000000000ffff R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8881d6f00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007531dfca55b0 CR3: 00000001be296004 CR4: 00000000001706e0 Call Trace: ? show_regs+0x61/0x73 ? __die_body+0x20/0x73 ? die_addr+0x4f/0x7b ? exc_general_protection+0x191/0x1db ? asm_exc_general_protection+0x27/0x30 ? rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core] ? rtw89_fw_h2c_scan_offload_be+0x458/0x13c3 [rtw89_core] ? __pfx_rtw89_fw_h2c_scan_offload_be+0x10/0x10 [rtw89_core] ? do_raw_spin_lock+0x75/0xdb ? __pfx_do_raw_spin_lock+0x10/0x10 rtw89_hw_scan_offload+0xb5e/0xbf7 [rtw89_core] ? _raw_spin_unlock+0xe/0x24 ? __mutex_lock.constprop.0+0x40c/0x471 ? __pfx_rtw89_hw_scan_offload+0x10/0x10 [rtw89_core] ? __mutex_lock_slowpath+0x13/0x1f ? mutex_lock+0xa2/0xdc ? __pfx_mutex_lock+0x10/0x10 rtw89_hw_scan_abort+0x58/0xb7 [rtw89_core] rtw89_ops_cancel_hw_scan+0x120/0x13b [rtw89_core] ieee80211_scan_cancel+0x468/0x4d0 [mac80211] ieee80211_prep_connection+0x858/0x899 [mac80211] ieee80211_mgd_auth+0xbea/0xdde [mac80211] ? __pfx_ieee80211_mgd_auth+0x10/0x10 [mac80211] ? cfg80211_find_elem+0x15/0x29 [cfg80211] ? is_bss+0x1b7/0x1d7 [cfg80211] ieee80211_auth+0x18/0x27 [mac80211] cfg80211_mlme_auth+0x3bb/0x3e7 [cfg80211] cfg80211_conn_do_work+0x410/0xb81 [cfg80211] ? __pfx_cfg80211_conn_do_work+0x10/0x10 [cfg80211] ? __kasan_check_read+0x11/0x1f ? psi_group_change+0x8bc/0x944 ? __kasan_check_write+0x14/0x22 ? mutex_lock+0x8e/0xdc ? __pfx_mutex_lock+0x10/0x10 ? __pfx___radix_tree_lookup+0x10/0x10 cfg80211_conn_work+0x245/0x34d [cfg80211] ? __pfx_cfg80211_conn_work+0x10/0x10 [cfg80211] ? update_cfs_rq_load_avg+0x3bc/0x3d7 ? sched_clock_noinstr+0x9/0x1a ? sched_clock+0x10/0x24 ? sched_clock_cpu+0x7e/0x42e ? newidle_balance+0x796/0x937 ? __pfx_sched_clock_cpu+0x10/0x10 ? __pfx_newidle_balance+0x10/0x10 ? __kasan_check_read+0x11/0x1f ? psi_group_change+0x8bc/0x944 ? _raw_spin_unlock+0xe/0x24 ? raw_spin_rq_unlock+0x47/0x54 ? raw_spin_rq_unlock_irq+0x9/0x1f ? finish_task_switch.isra.0+0x347/0x586 ? __schedule+0x27bf/0x2892 ? mutex_unlock+0x80/0xd0 ? do_raw_spin_lock+0x75/0xdb ? __pfx___schedule+0x10/0x10 process_scheduled_works+0x58c/0x821 worker_thread+0x4c7/0x586 ? __kasan_check_read+0x11/0x1f kthread+0x285/0x294 ? __pfx_worker_thread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x29/0x6f ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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
14th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

February 27, 2025

Last Modified

October 30, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available.
Web page

wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba4bb0402c60e945c4c396c51f0acac3c3e3ea5c
Web page

wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5afcd6fcd1e1c1fd6bcc9a360c121d10eddade67
Web page

wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2403cb3c235d5e339b580cc3a825493769fadca8

Vendor Advisories for CVE-2025-21729(3)

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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-ibm-edge (6.8.0-1041.41~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1044.50) @ noble2026-10-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1020.21) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1044.50+fips1) @ noble2026-10-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1038.39) @ noble2026-10-30ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1027.30) @ noble2026-10-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1044.47+fips1) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-88.89~22.04.2) @ jammy2026-10-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-88.89) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1029.32) @ noble2026-10-30ubuntu
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 6.12.13 (fixes >=5.18.0)—osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

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 14× in last 7d / 52× 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 96 of 213 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21729?
CVE-2025-21729 is a high-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion The rtwdev->scanning flag isn't protected by mutex originally, so cancel_hw_scan can pass the condition, but suddenly hw_scan completion unset the flag and calls…
When was the CVE record for CVE-2025-21729 published?
The CVE record for CVE-2025-21729 was published on February 27, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2025-21729 actively exploited?
CVE-2025-21729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21729?
CVE-2025-21729 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-21729?
A fix for CVE-2025-21729 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21729 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-21729

Explore →

Is Your Infrastructure Affected by CVE-2025-21729?

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

Book a Demo →Browse All CVEs