CVE-2025-37745

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2025-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-13066 (ENISA EUVD) · GHSA-x3xp-7x67-4cx9 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

PM: hibernate: Avoid deadlock in hibernate_compressor_param_set()

syzbot reported a deadlock in lock_system_sleep() (see below).

The write operation to "/sys/module/hibernate/parameters/compressor" conflicts with the registration of ieee80211 device, resulting in a deadlock when attempting to acquire system_transition_mutex under param_lock.

To avoid this deadlock, change hibernate_compressor_param_set() to use mutex_trylock() for attempting to acquire system_transition_mutex and return -EBUSY when it fails.

Task flags need not be saved or adjusted before calling mutex_trylock(&system_transition_mutex) because the caller is not going to end up waiting for this mutex and if it runs concurrently with system suspend in progress, it will be frozen properly when it returns to user space.

syzbot report:

syz-executor895/5833 is trying to acquire lock: ffffffff8e0828c8 (system_transition_mutex){+.+.}-{4:4}, at: lock_system_sleep+0x87/0xa0 kernel/power/main.c:56

but task is already holding lock: ffffffff8e07dc68 (param_lock){+.+.}-{4:4}, at: kernel_param_lock kernel/params.c:607 [inline] ffffffff8e07dc68 (param_lock){+.+.}-{4:4}, at: param_attr_store+0xe6/0x300 kernel/params.c:586

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #3 (param_lock){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19b/0xb10 kernel/locking/mutex.c:730 ieee80211_rate_control_ops_get net/mac80211/rate.c:220 [inline] rate_control_alloc net/mac80211/rate.c:266 [inline] ieee80211_init_rate_ctrl_alg+0x18d/0x6b0 net/mac80211/rate.c:1015 ieee80211_register_hw+0x20cd/0x4060 net/mac80211/main.c:1531 mac80211_hwsim_new_radio+0x304e/0x54e0 drivers/net/wireless/virtual/mac80211_hwsim.c:5558 init_mac80211_hwsim+0x432/0x8c0 drivers/net/wireless/virtual/mac80211_hwsim.c:6910 do_one_initcall+0x128/0x700 init/main.c:1257 do_initcall_level init/main.c:1319 [inline] do_initcalls init/main.c:1335 [inline] do_basic_setup init/main.c:1354 [inline] kernel_init_freeable+0x5c7/0x900 init/main.c:1568 kernel_init+0x1c/0x2b0 init/main.c:1457 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244

-> #2 (rtnl_mutex){+.+.}-{4:4}: __mutex_lock_common kernel/locking/mutex.c:585 [inline] __mutex_lock+0x19b/0xb10 kernel/locking/mutex.c:730 wg_pm_notification drivers/net/wireguard/device.c:80 [inline] wg_pm_notification+0x49/0x180 drivers/net/wireguard/device.c:64 notifier_call_chain+0xb7/0x410 kernel/notifier.c:85 notifier_call_chain_robust kernel/notifier.c:120 [inline] blocking_notifier_call_chain_robust kernel/notifier.c:345 [inline] blocking_notifier_call_chain_robust+0xc9/0x170 kernel/notifier.c:333 pm_notifier_call_chain_robust+0x27/0x60 kernel/power/main.c:102 snapshot_open+0x189/0x2b0 kernel/power/user.c:77 misc_open+0x35a/0x420 drivers/char/misc.c:179 chrdev_open+0x237/0x6a0 fs/char_dev.c:414 do_dentry_open+0x735/0x1c40 fs/open.c:956 vfs_open+0x82/0x3f0 fs/open.c:1086 do_open fs/namei.c:3830 [inline] path_openat+0x1e88/0x2d80 fs/namei.c:3989 do_filp_open+0x20c/0x470 fs/namei.c:4016 do_sys_openat2+0x17a/0x1e0 fs/open.c:1428 do_sys_open fs/open.c:1443 [inline] __do_sys_openat fs/open.c:1459 [inline] __se_sys_openat fs/open.c:1454 [inline] __x64_sys_openat+0x175/0x210 fs/open.c:1454 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #1 ((pm_chain_head).rwsem){++++}-{4:4}: down_read+0x9a/0x330 kernel/locking/rwsem.c:1524 blocking_notifier_call_chain_robust kerne ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
3rd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

May 1, 2025

Last Modified

November 5, 2025

Vendor Advisories for CVE-2025-37745(1)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-23ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-23ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-23ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-10-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-10-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-23ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-10-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-10-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-10-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-23ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-10-23ubuntu
linuxKernel @ 6.12.24 (fixes >=6.9.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(19)

Data Freshness Timeline

(refreshed 6× in last 7d / 37× 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 183 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 87 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-37745?
CVE-2025-37745 is a medium-severity vulnerability; its CVE record was published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: PM: hibernate: Avoid deadlock in hibernate_compressor_param_set() syzbot reported a deadlock in lock_system_sleep() (see below). The write operation to "/sys/module/hibernate/parameters/compressor" conflicts with the registration…
When was the CVE record for CVE-2025-37745 published?
The CVE record for CVE-2025-37745 was published on May 1, 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 November 5, 2025; the record at its source may have been updated since.
Is CVE-2025-37745 actively exploited?
CVE-2025-37745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37745?
CVE-2025-37745 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-37745?
A fix for CVE-2025-37745 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37745 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-37745

Explore →

Is Your Infrastructure Affected by CVE-2025-37745?

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