CVE-2025-38166

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-07-03. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
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: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

bpf: fix ktls panic with sockmap

[ 2172.936997] ------------[ cut here ]------------ [ 2172.936999] kernel BUG at lib/iov_iter.c:629! ...... [ 2172.944996] PKRU: 55555554 [ 2172.945155] Call Trace: [ 2172.945299] [ 2172.945428] ? die+0x36/0x90 [ 2172.945601] ? do_trap+0xdd/0x100 [ 2172.945795] ? iov_iter_revert+0x178/0x180 [ 2172.946031] ? iov_iter_revert+0x178/0x180 [ 2172.946267] ? do_error_trap+0x7d/0x110 [ 2172.946499] ? iov_iter_revert+0x178/0x180 [ 2172.946736] ? exc_invalid_op+0x50/0x70 [ 2172.946961] ? iov_iter_revert+0x178/0x180 [ 2172.947197] ? asm_exc_invalid_op+0x1a/0x20 [ 2172.947446] ? iov_iter_revert+0x178/0x180 [ 2172.947683] ? iov_iter_revert+0x5c/0x180 [ 2172.947913] tls_sw_sendmsg_locked.isra.0+0x794/0x840 [ 2172.948206] tls_sw_sendmsg+0x52/0x80 [ 2172.948420] ? inet_sendmsg+0x1f/0x70 [ 2172.948634] __sys_sendto+0x1cd/0x200 [ 2172.948848] ? find_held_lock+0x2b/0x80 [ 2172.949072] ? syscall_trace_enter+0x140/0x270 [ 2172.949330] ? __lock_release.isra.0+0x5e/0x170 [ 2172.949595] ? find_held_lock+0x2b/0x80 [ 2172.949817] ? syscall_trace_enter+0x140/0x270 [ 2172.950211] ? lockdep_hardirqs_on_prepare+0xda/0x190 [ 2172.950632] ? ktime_get_coarse_real_ts64+0xc2/0xd0 [ 2172.951036] __x64_sys_sendto+0x24/0x30 [ 2172.951382] do_syscall_64+0x90/0x170 ......

After calling bpf_exec_tx_verdict(), the size of msg_pl->sg may increase, e.g., when the BPF program executes bpf_msg_push_data().

If the BPF program sets cork_bytes and sg.size is smaller than cork_bytes, it will return -ENOSPC and attempt to roll back to the non-zero copy logic. However, during rollback, msg->msg_iter is reset, but since msg_pl->sg.size has been increased, subsequent executions will exceed the actual size of msg_iter. ''' iov_iter_revert(&msg->msg_iter, msg_pl->sg.size - orig_size); '''

The changes in this commit are based on the following considerations:

  • When cork_bytes is set, rolling back to non-zero copy logic is
pointless and can directly go to zero-copy logic.
  • We can not calculate the correct number of bytes to revert msg_iter.

Assume the original data is "abcdefgh" (8 bytes), and after 3 pushes by the BPF program, it becomes 11-byte data: "abc?de?fgh?". Then, we set cork_bytes to 6, which means the first 6 bytes have been processed, and the remaining 5 bytes "?fgh?" will be cached until the length meets the cork_bytes requirement.

However, some data in "?fgh?" is not within 'sg->msg_iter' (but in msg_pl instead), especially the data "?" we pushed.

So it doesn't seem as simple as just reverting through an offset of msg_iter.

  • For non-TLS sockets in tcp_bpf_sendmsg, when a "cork" situation occurs,
the user-space send() doesn't return an error, and the returned length is the same as the input length parameter, even if some data is cached.

Additionally, I saw that the current non-zero-copy logic for handling corking is written as: ''' line 1177 else if (ret != -EAGAIN) { if (ret == -ENOSPC) ret = 0; goto send_end; '''

So it's ok to just return 'copied' without error when a "cork" situation occurs.

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 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
9th
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 3, 2025

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 2, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web page

bpf: fix ktls panic with sockmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/603943f022a7fe5cc83ca7005faf34798fb7853f
Web page

bpf: fix ktls panic with sockmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/57fbbe29e86042bbaa31c1a30d2afa16c427e3f7
Web page

bpf: fix ktls panic with sockmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54a3ecaeeeae8176da8badbd7d72af1017032c39
Web page

bpf: fix ktls panic with sockmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/328cac3f9f8ae394748485e769a527518a9137c8
Web page

bpf: fix ktls panic with sockmap - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2e36a81d388ec9c3f78b6223f7eda2088cd40adb

Vendor Advisories for CVE-2025-38166(3)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1044.44~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-32.32) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1012.12) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1012.12) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1012.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1013.13~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
linuxKernel @ 6.1.142 (fixes >=4.20.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 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
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.35-1: fixed in 6.12.35-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.35-1: fixed in 6.12.35-1
—

Additional Vendor Advisories

(22)

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 10× in last 7d / 28× 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 156 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 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-38166?
CVE-2025-38166 is a medium-severity vulnerability; its CVE record was published on July 3, 2025. In the Linux kernel, the following vulnerability has been resolved: bpf: fix ktls panic with sockmap [ 2172.936997] ------------[ cut here ]------------ [ 2172.936999] kernel BUG at lib/iov_iter.c:629! ...... [ 2172.944996] PKRU: 55555554 [ 2172.945155] Call Trace: [ 2172.945299] <TASK> […
When was the CVE record for CVE-2025-38166 published?
The CVE record for CVE-2025-38166 was published on July 3, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38166 actively exploited?
CVE-2025-38166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38166?
CVE-2025-38166 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38166?
A fix for CVE-2025-38166 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38166 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-38166

Explore →

Is Your Infrastructure Affected by CVE-2025-38166?

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

Book a Demo →Browse All CVEs