CVE-2025-38400

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2025-07-25.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
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.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails.

syzbot reported a warning below [1] following a fault injection in nfs_fs_proc_net_init(). [0]

When nfs_fs_proc_net_init() fails, /proc/net/rpc/nfs is not removed.

Later, rpc_proc_exit() tries to remove /proc/net/rpc, and the warning is logged as the directory is not empty.

Let's handle the error of nfs_fs_proc_net_init() properly.

[0]: FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl (lib/dump_stack.c:123) should_fail_ex (lib/fault-inject.c:73 lib/fault-inject.c:174) should_failslab (mm/failslab.c:46) kmem_cache_alloc_noprof (mm/slub.c:4178 mm/slub.c:4204) __proc_create (fs/proc/generic.c:427) proc_create_reg (fs/proc/generic.c:554) proc_create_net_data (fs/proc/proc_net.c:120) nfs_fs_proc_net_init (fs/nfs/client.c:1409) nfs_net_init (fs/nfs/inode.c:2600) ops_init (net/core/net_namespace.c:138) setup_net (net/core/net_namespace.c:443) copy_net_ns (net/core/net_namespace.c:576) create_new_namespaces (kernel/nsproxy.c:110) unshare_nsproxy_namespaces (kernel/nsproxy.c:218 (discriminator 4)) ksys_unshare (kernel/fork.c:3123) __x64_sys_unshare (kernel/fork.c:3190) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)

[1]: remove_proc_entry: removing non-empty directory 'net/rpc', leaking at least 'nfs' WARNING: CPU: 1 PID: 6120 at fs/proc/generic.c:727 remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727 Modules linked in: CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727 Code: 3c 02 00 0f 85 85 00 00 00 48 8b 93 d8 00 00 00 4d 89 f0 4c 89 e9 48 c7 c6 40 ba a2 8b 48 c7 c7 60 b9 a2 8b e8 33 81 1d ff 90 <0f> 0b 90 90 e9 5f fe ff ff e8 04 69 5e ff 90 48 b8 00 00 00 00 00 RSP: 0018:ffffc90003637b08 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff88805f534140 RCX: ffffffff817a92c8 RDX: ffff88807da99e00 RSI: ffffffff817a92d5 RDI: 0000000000000001 RBP: ffff888033431ac0 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffff888033431a00 R13: ffff888033431ae4 R14: ffff888033184724 R15: dffffc0000000000 FS: 0000555580328500(0000) GS:ffff888124a62000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f71733743e0 CR3: 000000007f618000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: sunrpc_exit_net+0x46/0x90 net/sunrpc/sunrpc_syms.c:76 ops_exit_list net/core/net_namespace.c:200 [inline] ops_undo_list+0x2eb/0xab0 net/core/net_namespace.c:253 setup_net+0x2e1/0x510 net/core/net_namespace.c:457 copy_net_ns+0x2a6/0x5f0 net/core/net_namespace.c:574 create_new_namespaces+0x3ea/0xa90 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:218 ksys_unshare+0x45b/0xa40 kernel/fork.c:3121 __do_sys_unshare kernel/fork.c:3192 [inline] __se_sys_unshare kernel/fork.c:3190 [inline] __x64_sys_unshare+0x31/0x40 kernel/fork.c:3190 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa1a6b8e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c ---truncated---

CVSS v3
—
EG Score
5.5MEDIUMlow confidence
EG Risk
25
EG Risk 25/100

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 computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.2% × 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.2%
EPSS %ILE
8th
KEV
Not listed

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.

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

July 25, 2025

Last Modified

October 15, 2026

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1034.36) @ jammy2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-05-21ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-05-21ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-21ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-21ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-21ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1043.44~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-21ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-21ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-21ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-21ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-21ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1096.81) @ jammy2026-05-21ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1092.96) @ jammy2026-05-21ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1092.82) @ jammy2026-05-21ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1090.96~20.04.1) @ focal2026-05-21ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1056 (5.15.0-1056.60) @ jammy2026-05-21ubuntu
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat
linuxKernel @ 5.4.296 (fixes >=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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 14× in last 7d / 32× 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 90 of 195 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 105 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(4)

What is CVE-2025-38400?
CVE-2025-38400 is a medium-severity vulnerability; its CVE record was published on July 25, 2025. In the Linux kernel, the following vulnerability has been resolved: nfs: Clean up /proc/net/rpc/nfs when nfsfsprocnetinit() fails. syzbot reported a warning below [1] following a fault injection in nfsfsprocnetinit(). [0] When nfsfsprocnetinit() fails, /proc/net/rpc/nfs is not removed. Later,…
When was the CVE record for CVE-2025-38400 published?
The CVE record for CVE-2025-38400 was published on July 25, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2025-38400 actively exploited?
CVE-2025-38400 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-38400?
A fix for CVE-2025-38400 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38400 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-38400

Explore →

Is Your Infrastructure Affected by CVE-2025-38400?

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