CVE-2026-53005

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-38873 (ENISA EUVD) · GHSA-6qfx-pmxg-8gxp (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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

af_unix: Drop all SCM attributes for SOCKMAP.

SOCKMAP can hide inflight fd from AF_UNIX GC.

When a socket in SOCKMAP receives skb with inflight fd, sk_psock_verdict_data_ready() looks up the mapped socket and enqueue skb to its psock->ingress_skb.

Since neither the old nor the new GC can inspect the psock queue, the hidden skb leaks the inflight sockets. Note that this cannot be detected via kmemleak because inflight sockets are linked to a global list.

In addition, SOCKMAP redirect breaks the Tarjan-based GC's assumption that unix_edge.successor is always alive, which is no longer true once skb is redirected, resulting in use-after-free below. [0]

Moreover, SOCKMAP does not call scm_stat_del() properly, so unix_show_fdinfo() could report an incorrect fd count.

sk_msg_recvmsg() does not support any SCM attributes in the first place.

Let's drop all SCM attributes before passing skb to the SOCKMAP layer.

[0]: BUG: KASAN: slab-use-after-free in unix_del_edges (net/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) Read of size 8 at addr ffff888125362670 by task kworker/56:1/496

CPU: 56 UID: 0 PID: 496 Comm: kworker/56:1 Not tainted 7.0.0-rc7-00263-gb9d8b856689d #3 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 Workqueue: events sk_psock_backlog Call Trace: dump_stack_lvl (lib/dump_stack.c:122) print_report (mm/kasan/report.c:379) kasan_report (mm/kasan/report.c:597) unix_del_edges (net/unix/garbage.c:118 net/unix/garbage.c:181 net/unix/garbage.c:251) unix_destroy_fpl (net/unix/garbage.c:317) unix_destruct_scm (./include/net/scm.h:80 ./include/net/scm.h:86 net/unix/af_unix.c:1976) sk_psock_backlog (./include/linux/skbuff.h:?) process_scheduled_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:258)

Allocated by task 955: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) __kasan_slab_alloc (mm/kasan/common.c:369) kmem_cache_alloc_noprof (mm/slub.c:4539) sk_prot_alloc (net/core/sock.c:2240) sk_alloc (net/core/sock.c:2301) unix_create1 (net/unix/af_unix.c:1099) unix_create (net/unix/af_unix.c:1169) __sock_create (net/socket.c:1606) __sys_socketpair (net/socket.c:1811) __x64_sys_socketpair (net/socket.c:1863 net/socket.c:1860 net/socket.c:1860) do_syscall_64 (arch/x86/entry/syscall_64.c:?) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)

Freed by task 496: kasan_save_track (mm/kasan/common.c:58 mm/kasan/common.c:78) kasan_save_free_info (mm/kasan/generic.c:587) __kasan_slab_free (mm/kasan/common.c:287) kmem_cache_free (mm/slub.c:6165) __sk_destruct (net/core/sock.c:2282 net/core/sock.c:2384) sk_psock_destroy (./include/net/sock.h:?) process_scheduled_works (kernel/workqueue.c:?) worker_thread (kernel/workqueue.c:?) kthread (kernel/kthread.c:438) ret_from_fork (arch/x86/kernel/process.c:164) ret_from_fork_asm (arch/x86/entry/entry_64.S:258)

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.1% × 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.1%
EPSS %ILE
2nd
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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: 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.

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

June 24, 2026

Last Modified

October 19, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
Patch available.
Web page

af_unix: Drop all SCM attributes for SOCKMAP. - kernel/git/stable/linux.git - Linux kernel stable tree

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

af_unix: Drop all SCM attributes for SOCKMAP. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/965dc93481d1b80d341bdd16c27b16fe197175ee

Vendor Advisories for CVE-2026-53005(4)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-27ubuntu
redhatkernel-0:6.12.0-211.60.1.el10_22026-09-24redhat
redhatkernel-0:5.14.0-687.51.1.el9_82026-09-24redhat

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

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

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 / 53× 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 336 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 236 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53005?
CVE-2026-53005 is a high-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: af_unix: Drop all SCM attributes for SOCKMAP. SOCKMAP can hide inflight fd from AF_UNIX GC. When a socket in SOCKMAP receives skb with inflight fd, skpsockverdictdataready() looks up the mapped socket and enqueue skb to its…
When was the CVE record for CVE-2026-53005 published?
The CVE record for CVE-2026-53005 was published on June 24, 2026. 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-53005 actively exploited?
CVE-2026-53005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53005?
CVE-2026-53005 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53005?
A fix for CVE-2026-53005 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53005 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-2026-53005

Explore →

Is Your Infrastructure Affected by CVE-2026-53005?

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

Book a Demo →Browse All CVEs