CVE-2023-52637

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 2024-04-03. 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-2023-57261 (ENISA EUVD) · GHSA-2w67-3g2f-j7p2 (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:

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER)

Lock jsk->sk to prevent UAF when setsockopt(..., SO_J1939_FILTER, ...) modifies jsk->filters while receiving packets.

Following trace was seen on affected system: ================================================================== BUG: KASAN: slab-use-after-free in j1939_sk_recv_match_one+0x1af/0x2d0 [can_j1939] Read of size 4 at addr ffff888012144014 by task j1939/350

CPU: 0 PID: 350 Comm: j1939 Tainted: G W OE 6.5.0-rc5 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Call Trace: print_report+0xd3/0x620 ? kasan_complete_mode_report_info+0x7d/0x200 ? j1939_sk_recv_match_one+0x1af/0x2d0 [can_j1939] kasan_report+0xc2/0x100 ? j1939_sk_recv_match_one+0x1af/0x2d0 [can_j1939] __asan_load4+0x84/0xb0 j1939_sk_recv_match_one+0x1af/0x2d0 [can_j1939] j1939_sk_recv+0x20b/0x320 [can_j1939] ? __kasan_check_write+0x18/0x20 ? __pfx_j1939_sk_recv+0x10/0x10 [can_j1939] ? j1939_simple_recv+0x69/0x280 [can_j1939] ? j1939_ac_recv+0x5e/0x310 [can_j1939] j1939_can_recv+0x43f/0x580 [can_j1939] ? __pfx_j1939_can_recv+0x10/0x10 [can_j1939] ? raw_rcv+0x42/0x3c0 [can_raw] ? __pfx_j1939_can_recv+0x10/0x10 [can_j1939] can_rcv_filter+0x11f/0x350 [can] can_receive+0x12f/0x190 [can] ? __pfx_can_rcv+0x10/0x10 [can] can_rcv+0xdd/0x130 [can] ? __pfx_can_rcv+0x10/0x10 [can] __netif_receive_skb_one_core+0x13d/0x150 ? __pfx___netif_receive_skb_one_core+0x10/0x10 ? __kasan_check_write+0x18/0x20 ? _raw_spin_lock_irq+0x8c/0xe0 __netif_receive_skb+0x23/0xb0 process_backlog+0x107/0x260 __napi_poll+0x69/0x310 net_rx_action+0x2a1/0x580 ? __pfx_net_rx_action+0x10/0x10 ? __pfx__raw_spin_lock+0x10/0x10 ? handle_irq_event+0x7d/0xa0 __do_softirq+0xf3/0x3f8 do_softirq+0x53/0x80 __local_bh_enable_ip+0x6e/0x70 netif_rx+0x16b/0x180 can_send+0x32b/0x520 [can] ? __pfx_can_send+0x10/0x10 [can] ? __check_object_size+0x299/0x410 raw_sendmsg+0x572/0x6d0 [can_raw] ? __pfx_raw_sendmsg+0x10/0x10 [can_raw] ? apparmor_socket_sendmsg+0x2f/0x40 ? __pfx_raw_sendmsg+0x10/0x10 [can_raw] sock_sendmsg+0xef/0x100 sock_write_iter+0x162/0x220 ? __pfx_sock_write_iter+0x10/0x10 ? __rtnl_unlock+0x47/0x80 ? security_file_permission+0x54/0x320 vfs_write+0x6ba/0x750 ? __pfx_vfs_write+0x10/0x10 ? __fget_light+0x1ca/0x1f0 ? __rcu_read_unlock+0x5b/0x280 ksys_write+0x143/0x170 ? __pfx_ksys_write+0x10/0x10 ? __kasan_check_read+0x15/0x20 ? fpregs_assert_state_consistent+0x62/0x70 __x64_sys_write+0x47/0x60 do_syscall_64+0x60/0x90 ? do_syscall_64+0x6d/0x90 ? irqentry_exit+0x3f/0x50 ? exc_page_fault+0x79/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Allocated by task 348: kasan_save_stack+0x2a/0x50 kasan_set_track+0x29/0x40 kasan_save_alloc_info+0x1f/0x30 __kasan_kmalloc+0xb5/0xc0 __kmalloc_node_track_caller+0x67/0x160 j1939_sk_setsockopt+0x284/0x450 [can_j1939] __sys_setsockopt+0x15c/0x2f0 __x64_sys_setsockopt+0x6b/0x80 do_syscall_64+0x60/0x90 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

Freed by task 349: kasan_save_stack+0x2a/0x50 kasan_set_track+0x29/0x40 kasan_save_free_info+0x2f/0x50 __kasan_slab_free+0x12e/0x1c0 __kmem_cache_free+0x1b9/0x380 kfree+0x7a/0x120 j1939_sk_setsockopt+0x3b2/0x450 [can_j1939] __sys_setsockopt+0x15c/0x2f0 __x64_sys_setsockopt+0x6b/0x80 do_syscall_64+0x60/0x90 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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-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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

April 3, 2024

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 5, 2026
Patch available.
Web page

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

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

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dd684d4bb3cd5454e0bf6e2a1bdfbd5c9c872ed
Web page

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41ccb5bcbf03f02d820bc6ea8390811859f558f8
Web page

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/978e50ef8c38dc71bd14d1b0143d554ff5d188ba
Web page

can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08de58abedf6e69396e1207e4f99ef8904b2b532

Vendor Advisories for CVE-2023-52637(1)

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

Patch Availability(14)

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 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
linux-5.105.10.136-1~deb10u1 ... 5.10.209-2~deb10u1 (13 versions)
  • every version up to 5.10.216-1~deb10u1: fixed in 5.10.216-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (39 versions)
  • every version up to 5.10.216-1: fixed in 5.10.216-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (18 versions)
  • every version up to 6.1.82-1: fixed in 6.1.82-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.7-1: fixed in 6.7.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-52637?
CVE-2023-52637 is a high-severity vulnerability; its CVE record was published on April 3, 2024. In the Linux kernel, the following vulnerability has been resolved: can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) Lock jsk->sk to prevent UAF when setsockopt(..., SO_J1939_FILTER, ...) modifies jsk->filters while receiving packets. Following trace was seen on…
When was the CVE record for CVE-2023-52637 published?
The CVE record for CVE-2023-52637 was published on April 3, 2024. 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-2023-52637 actively exploited?
CVE-2023-52637 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-2023-52637?
CVE-2023-52637 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52637?
A fix for CVE-2023-52637 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52637 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-2023-52637

Explore →

Is Your Infrastructure Affected by CVE-2023-52637?

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