CVE-2023-52610

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

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

A fix is available — apply it.

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

net/sched: act_ct: fix skb leak and crash on ooo frags

act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in:

inet_frag_reasm_prepare skb_morph

which is not straightforward.

However when frags arrive out of order, nobody unref the last frag, and all frags are leaked. The situation is even worse, as initiating packet capture can lead to a crash[0] when skb has been cloned and shared at the same time.

Fix the issue by removing skb_get() before defragmentation. act_ct returns TC_ACT_CONSUMED when defrag failed or in progress.

[0]: [ 843.804823] ------------[ cut here ]------------ [ 843.809659] kernel BUG at net/core/skbuff.c:2091! [ 843.814516] invalid opcode: 0000 [#1] PREEMPT SMP [ 843.819296] CPU: 7 PID: 0 Comm: swapper/7 Kdump: loaded Tainted: G S 6.7.0-rc3 #2 [ 843.824107] Hardware name: XFUSION 1288H V6/BC13MBSBD, BIOS 1.29 11/25/2022 [ 843.828953] RIP: 0010:pskb_expand_head+0x2ac/0x300 [ 843.833805] Code: 8b 70 28 48 85 f6 74 82 48 83 c6 08 bf 01 00 00 00 e8 38 bd ff ff 8b 83 c0 00 00 00 48 03 83 c8 00 00 00 e9 62 ff ff ff 0f 0b <0f> 0b e8 8d d0 ff ff e9 b3 fd ff ff 81 7c 24 14 40 01 00 00 4c 89 [ 843.843698] RSP: 0018:ffffc9000cce07c0 EFLAGS: 00010202 [ 843.848524] RAX: 0000000000000002 RBX: ffff88811a211d00 RCX: 0000000000000820 [ 843.853299] RDX: 0000000000000640 RSI: 0000000000000000 RDI: ffff88811a211d00 [ 843.857974] RBP: ffff888127d39518 R08: 00000000bee97314 R09: 0000000000000000 [ 843.862584] R10: 0000000000000000 R11: ffff8881109f0000 R12: 0000000000000880 [ 843.867147] R13: ffff888127d39580 R14: 0000000000000640 R15: ffff888170f7b900 [ 843.871680] FS: 0000000000000000(0000) GS:ffff889ffffc0000(0000) knlGS:0000000000000000 [ 843.876242] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 843.880778] CR2: 00007fa42affcfb8 CR3: 000000011433a002 CR4: 0000000000770ef0 [ 843.885336] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 843.889809] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 843.894229] PKRU: 55555554 [ 843.898539] Call Trace: [ 843.902772] [ 843.906922] ? __die_body+0x1e/0x60 [ 843.911032] ? die+0x3c/0x60 [ 843.915037] ? do_trap+0xe2/0x110 [ 843.918911] ? pskb_expand_head+0x2ac/0x300 [ 843.922687] ? do_error_trap+0x65/0x80 [ 843.926342] ? pskb_expand_head+0x2ac/0x300 [ 843.929905] ? exc_invalid_op+0x50/0x60 [ 843.933398] ? pskb_expand_head+0x2ac/0x300 [ 843.936835] ? asm_exc_invalid_op+0x1a/0x20 [ 843.940226] ? pskb_expand_head+0x2ac/0x300 [ 843.943580] inet_frag_reasm_prepare+0xd1/0x240 [ 843.946904] ip_defrag+0x5d4/0x870 [ 843.950132] nf_ct_handle_fragments+0xec/0x130 [nf_conntrack] [ 843.953334] tcf_ct_act+0x252/0xd90 [act_ct] [ 843.956473] ? tcf_mirred_act+0x516/0x5a0 [act_mirred] [ 843.959657] tcf_action_exec+0xa1/0x160 [ 843.962823] fl_classify+0x1db/0x1f0 [cls_flower] [ 843.966010] ? skb_clone+0x53/0xc0 [ 843.969173] tcf_classify+0x24d/0x420 [ 843.972333] tc_run+0x8f/0xf0 [ 843.975465] __netif_receive_skb_core+0x67a/0x1080 [ 843.978634] ? dev_gro_receive+0x249/0x730 [ 843.981759] __netif_receive_skb_list_core+0x12d/0x260 [ 843.984869] netif_receive_skb_list_internal+0x1cb/0x2f0 [ 843.987957] ? mlx5e_handle_rx_cqe_mpwrq_rep+0xfa/0x1a0 [mlx5_core] [ 843.991170] napi_complete_done+0x72/0x1a0 [ 843.994305] mlx5e_napi_poll+0x28c/0x6d0 [mlx5_core] [ 843.997501] __napi_poll+0x25/0x1b0 [ 844.000627] net_rx_action+0x256/0x330 [ 844.003705] __do_softirq+0xb3/0x29b [ 844.006718] irq_exit_rcu+0x9e/0xc0 [ 844.009672] common_interrupt+0x86/0xa0 [ 844.012537] [ 844.015285] [ 844.017937] asm_common_interrupt+0x26/0x40 [ 844.020591] RIP: 0010:acpi_safe_halt+0x1b/0x20 [ 844.023247] Code: ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 65 48 8b 04 25 00 18 03 00 48 8b 00 a8 08 75 0c 66 90 0f 00 2d 81 d0 44 00 fb ---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.6% × 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.6%
EPSS %ILE
50th
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.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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: 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.

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

March 18, 2024

Last Modified

August 5, 2026

References (5)

Vendor Advisories for CVE-2023-52610(10)

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-22.04-edge (6.5.0.41.41) @ mantic2026-05-24ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-05-24ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-05-24ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-05-24ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-05-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-05-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1057.58) @ jammy2026-05-24ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.102.99) @ jammy2026-05-24ubuntu
redhatkernel-0:5.14.0-70.157.1.el9_02025-12-10redhat
redhatkernel-rt-0:5.14.0-70.157.1.rt21.229.el9_02025-12-10redhat
redhatkernel-rt-0:5.14.0-284.148.1.rt14.433.el9_22025-11-25redhat
redhatkernel-0:5.14.0-284.148.1.el9_22025-11-25redhat
redhatkernel-0:4.18.0-372.119.1.el8_62024-08-21redhat
redhatkernel-0:4.18.0-477.67.1.el8_82024-08-13redhat
redhatkernel-0:4.18.0-553.5.1.el8_102024-06-05redhat
redhatkernel-rt-0:4.18.0-553.5.1.rt7.346.el8_102024-06-05redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 5.15.148 (fixes >=5.3.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.76-1~bpo11+1 (17 versions)
  • every version up to 6.1.76-1: fixed in 6.1.76-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.15-1: fixed in 6.6.15-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

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 9× in last 7d / 33× 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 92 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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52610?
CVE-2023-52610 is a medium-severity vulnerability; its CVE record was published on March 18, 2024. In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix skb leak and crash on ooo frags act_ct adds skb->users before defragmentation. If frags arrive in order, the last frag's reference is reset in: inetfragreasm_prepare skb_morph which is not straightforward.…
When was the CVE record for CVE-2023-52610 published?
The CVE record for CVE-2023-52610 was published on March 18, 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-52610 actively exploited?
CVE-2023-52610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52610?
CVE-2023-52610 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52610?
A fix for CVE-2023-52610 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52610 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-52610

Explore →

Is Your Infrastructure Affected by CVE-2023-52610?

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

Book a Demo →Browse All CVEs