CVE-2023-53053

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 2025-05-02. 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-2025-13210 (ENISA EUVD) · GHSA-hhvq-g7gp-5v2c (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:

erspan: do not use skb_mac_header() in ndo_start_xmit()

Drivers should not assume skb_mac_header(skb) == skb->data in their ndo_start_xmit().

Use skb_network_offset() and skb_transport_offset() which better describe what is needed in erspan_fb_xmit() and ip6erspan_tunnel_xmit()

syzbot reported: WARNING: CPU: 0 PID: 5083 at include/linux/skbuff.h:2873 skb_mac_header include/linux/skbuff.h:2873 [inline] WARNING: CPU: 0 PID: 5083 at include/linux/skbuff.h:2873 ip6erspan_tunnel_xmit+0x1d9c/0x2d90 net/ipv6/ip6_gre.c:962 Modules linked in: CPU: 0 PID: 5083 Comm: syz-executor406 Not tainted 6.3.0-rc2-syzkaller-00866-gd4671cb96fa3 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023 RIP: 0010:skb_mac_header include/linux/skbuff.h:2873 [inline] RIP: 0010:ip6erspan_tunnel_xmit+0x1d9c/0x2d90 net/ipv6/ip6_gre.c:962 Code: 04 02 41 01 de 84 c0 74 08 3c 03 0f 8e 1c 0a 00 00 45 89 b4 24 c8 00 00 00 c6 85 77 fe ff ff 01 e9 33 e7 ff ff e8 b4 27 a1 f8 <0f> 0b e9 b6 e7 ff ff e8 a8 27 a1 f8 49 8d bf f0 0c 00 00 48 b8 00 RSP: 0018:ffffc90003b2f830 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 000000000000ffff RCX: 0000000000000000 RDX: ffff888021273a80 RSI: ffffffff88e1bd4c RDI: 0000000000000003 RBP: ffffc90003b2f9d8 R08: 0000000000000003 R09: 000000000000ffff R10: 000000000000ffff R11: 0000000000000000 R12: ffff88802b28da00 R13: 00000000000000d0 R14: ffff88807e25b6d0 R15: ffff888023408000 FS: 0000555556a61300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055e5b11eb6e8 CR3: 0000000027c1b000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace:

__netdev_start_xmit include/linux/netdevice.h:4900 [inline] netdev_start_xmit include/linux/netdevice.h:4914 [inline] __dev_direct_xmit+0x504/0x730 net/core/dev.c:4300 dev_direct_xmit include/linux/netdevice.h:3088 [inline] packet_xmit+0x20a/0x390 net/packet/af_packet.c:285 packet_snd net/packet/af_packet.c:3075 [inline] packet_sendmsg+0x31a0/0x5150 net/packet/af_packet.c:3107 sock_sendmsg_nosec net/socket.c:724 [inline] sock_sendmsg+0xde/0x190 net/socket.c:747 __sys_sendto+0x23a/0x340 net/socket.c:2142 __do_sys_sendto net/socket.c:2154 [inline] __se_sys_sendto net/socket.c:2150 [inline] __x64_sys_sendto+0xe1/0x1b0 net/socket.c:2150 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f123aaa1039 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 14 00 00 90 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 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffc15d12058 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f123aaa1039 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 0000000000000000 R08: 0000000020000040 R09: 0000000000000014 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f123aa648c0 R13: 431bde82d7b634db R14: 0000000000000000 R15: 0000000000000000

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 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
13th
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-28). 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, and whom BOD 26-04 binds: 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 (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.

The score's inputs: 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

May 2, 2025

Last Modified

November 12, 2025

Advisory Details (7)

Auto-updated Oct 20, 2026
Patch available.
Web page

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c7d6803689c99d55bbb862260d0ba486ff23c0b
Web page

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8e50ed774554f93d55426039b27b1e38d7fa64d8
Web page

erspan: do not use skb_mac_header() in ndo_start_xmit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d4172732f0ee1639a361a6cc5c3114bbb397386

Vendor Advisories for CVE-2023-53053(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.19.280 (fixes >=4.18.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 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—

Data Freshness Timeline

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

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-53053?
CVE-2023-53053 is a high-severity vulnerability; its CVE record was published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: erspan: do not use skb_mac_header() in ndo_start_xmit() Drivers should not assume skb_mac_header(skb) == skb->data in their ndo_start_xmit(). Use skb_network_offset() and skb_transport_offset() which better describe what is needed…
When was the CVE record for CVE-2023-53053 published?
The CVE record for CVE-2023-53053 was published on May 2, 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 November 12, 2025; the record at its source may have been updated since.
Is CVE-2023-53053 actively exploited?
CVE-2023-53053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53053?
CVE-2023-53053 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53053?
A fix for CVE-2023-53053 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53053 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-53053

Explore →

Is Your Infrastructure Affected by CVE-2023-53053?

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

Book a Demo →Browse All CVEs