CVE-2023-54090

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-12-24. The CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week

Also known asEUVD-2023-60355 (ENISA EUVD) · GHSA-vfj6-525r-34p4 (GitHub Security Advisories)Source: ENISA EUVD

9.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.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ixgbe: Fix panic during XDP_TX with > 64 CPUs

Commit 4fe815850bdc ("ixgbe: let the xdpdrv work with more than 64 cpus") adds support to allow XDP programs to run on systems with more than 64 CPUs by locking the XDP TX rings and indexing them using cpu % 64 (IXGBE_MAX_XDP_QS).

Upon trying this out patch on a system with more than 64 cores, the kernel paniced with an array-index-out-of-bounds at the return in ixgbe_determine_xdp_ring in ixgbe.h, which means ixgbe_determine_xdp_q_idx was just returning the cpu instead of cpu % IXGBE_MAX_XDP_QS. An example splat:

========================================================================== UBSAN: array-index-out-of-bounds in /var/lib/dkms/ixgbe/5.18.6+focal-1/build/src/ixgbe.h:1147:26 index 65 is out of range for type 'ixgbe_ring *[64]' ========================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000058 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 65 PID: 408 Comm: ksoftirqd/65 Tainted: G IOE 5.15.0-48-generic #54~20.04.1-Ubuntu Hardware name: Dell Inc. PowerEdge R640/0W23H8, BIOS 2.5.4 01/13/2020 RIP: 0010:ixgbe_xmit_xdp_ring+0x1b/0x1c0 [ixgbe] Code: 3b 52 d4 cf e9 42 f2 ff ff 66 0f 1f 44 00 00 0f 1f 44 00 00 55 b9 00 00 00 00 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 08 <44> 0f b7 47 58 0f b7 47 5a 0f b7 57 54 44 0f b7 76 08 66 41 39 c0 RSP: 0018:ffffbc3fcd88fcb0 EFLAGS: 00010282 RAX: ffff92a253260980 RBX: ffffbc3fe68b00a0 RCX: 0000000000000000 RDX: ffff928b5f659000 RSI: ffff928b5f659000 RDI: 0000000000000000 RBP: ffffbc3fcd88fce0 R08: ffff92b9dfc20580 R09: 0000000000000001 R10: 3d3d3d3d3d3d3d3d R11: 3d3d3d3d3d3d3d3d R12: 0000000000000000 R13: ffff928b2f0fa8c0 R14: ffff928b9be20050 R15: 000000000000003c FS: 0000000000000000(0000) GS:ffff92b9dfc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000058 CR3: 000000011dd6a002 CR4: 00000000007706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ixgbe_poll+0x103e/0x1280 [ixgbe] ? sched_clock_cpu+0x12/0xe0 __napi_poll+0x30/0x160 net_rx_action+0x11c/0x270 __do_softirq+0xda/0x2ee run_ksoftirqd+0x2f/0x50 smpboot_thread_fn+0xb7/0x150 ? sort_range+0x30/0x30 kthread+0x127/0x150 ? set_kthread_struct+0x50/0x50 ret_from_fork+0x1f/0x30

I think this is how it happens:

Upon loading the first XDP program on a system with more than 64 CPUs, ixgbe_xdp_locking_key is incremented in ixgbe_xdp_setup. However, immediately after this, the rings are reconfigured by ixgbe_setup_tc. ixgbe_setup_tc calls ixgbe_clear_interrupt_scheme which calls ixgbe_free_q_vectors which calls ixgbe_free_q_vector in a loop. ixgbe_free_q_vector decrements ixgbe_xdp_locking_key once per call if it is non-zero. Commenting out the decrement in ixgbe_free_q_vector stopped my system from panicing.

I suspect to make the original patch work, I would need to load an XDP program and then replace it in order to get ixgbe_xdp_locking_key back above 0 since ixgbe_setup_tc is only called when transitioning between XDP and non-XDP ring configurations, while ixgbe_xdp_locking_key is incremented every time ixgbe_xdp_setup is called.

Also, ixgbe_setup_tc can be called via ethtool --set-channels, so this becomes another path to decrement ixgbe_xdp_locking_key to 0 on systems with more than 64 CPUs.

Since ixgbe_xdp_locking_key only protects the XDP_TX path and is tied to the number of CPUs present, there is no reason to disable it upon unloading an XDP program. To avoid confusion, I have moved enabling ixgbe_xdp_locking_key into ixgbe_sw_init, which is part of the probe path.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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 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.6%
EPSS %ILE
48th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-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-11-01). 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

December 24, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

ixgbe: Fix panic during XDP_TX with > 64 CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

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

ixgbe: Fix panic during XDP_TX with > 64 CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

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

ixgbe: Fix panic during XDP_TX with > 64 CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/785b2b5b47b1aa4c31862948b312ea845401c5ec
Web page

ixgbe: Fix panic during XDP_TX with > 64 CPUs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1924450175349e64f8dfc3689efcb653dba0418e

Vendor Advisories for CVE-2023-54090(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.1.29 (fixes >=5.16.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1
  • every version up to 6.1.37-1: fixed in 6.1.37-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Data Freshness Timeline

(refreshed 29× in last 7d / 95× 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 99 of 302 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 203 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.6% · 48th percentile
  2. 2026-11-02 15:34 UTCEG score recompute
  3. 2026-11-02 15:34 UTCVendor advisory
  4. 2026-11-02 15:34 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-11-01 16:19 UTCVendor advisory
  7. 2026-11-01 16:19 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-31 16:59 UTCEG score recompute
  9. 2026-10-31 16:59 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-30 17:37 UTCEG score recompute
  12. 2026-10-30 17:37 UTCVendor advisory
  13. 2026-10-30 17:37 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-29 18:23 UTCEG score recompute
  16. 2026-10-29 18:23 UTCVendor advisory
  17. 2026-10-29 18:23 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-28 19:09 UTCEG score recompute
  20. 2026-10-28 19:09 UTCVendor advisory
  21. 2026-10-28 19:09 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-27 19:33 UTCEG score recompute
  24. 2026-10-27 19:33 UTCVendor advisory
  25. 2026-10-27 19:33 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 74 more
  1. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-26 20:19 UTCEG score recompute
  3. 2026-10-26 20:19 UTCVendor advisory
  4. 2026-10-26 20:19 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  6. 2026-10-25 19:15 UTCVendor advisory
  7. 2026-10-25 19:15 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-25 17:27 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-24 19:50 UTCEG score recompute
  11. 2026-10-24 19:50 UTCVendor advisory
  12. 2026-10-24 19:50 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-23 20:36 UTCEG score recompute
  15. 2026-10-23 20:36 UTCVendor advisory
  16. 2026-10-23 20:36 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-22 21:18 UTCEG score recompute
  19. 2026-10-22 21:18 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-21 22:04 UTCEG score recompute
  22. 2026-10-21 22:04 UTCVendor advisory
  23. 2026-10-21 22:04 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-20 22:48 UTCEG score recompute
  26. 2026-10-20 22:48 UTCVendor advisory
  27. 2026-10-20 22:48 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  29. 2026-10-19 23:13 UTCEG score recompute
  30. 2026-10-19 23:13 UTCVendor advisory
  31. 2026-10-19 23:12 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  33. 2026-10-18 22:38 UTCEG score recompute
  34. 2026-10-18 22:38 UTCVendor advisory
  35. 2026-10-18 22:37 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  37. 2026-10-18 07:40 UTCEG score recompute
  38. 2026-10-17 23:22 UTCEG score recompute
  39. 2026-10-17 23:22 UTCVendor advisory
  40. 2026-10-17 23:22 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-10-17 00:05 UTCEG score recompute
  43. 2026-10-17 00:05 UTCVendor advisory
  44. 2026-10-17 00:04 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  46. 2026-10-15 20:59 UTCEG score recompute
  47. 2026-10-15 20:59 UTCVendor advisory
  48. 2026-10-15 20:59 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  50. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  51. 2026-10-14 15:08 UTCEG score recompute
  52. 2026-10-14 15:08 UTCVendor advisory
  53. 2026-10-14 15:07 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-10-13 14:34 UTCEG score recompute
  56. 2026-10-13 14:34 UTCVendor advisory
  57. 2026-10-13 14:33 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  59. 2026-10-12 15:16 UTCEG score recompute
  60. 2026-10-12 15:16 UTCVendor advisory
  61. 2026-10-12 15:16 UTCGHSA enrichmentGHSA-vfj6-525r-34p4 · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-11 21:37 UTCEG score recompute
  63. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  64. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  67. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  68. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  69. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  70. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  71. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-10-03 12:39 UTCOSV refresh
  73. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  74. 2026-09-30 16:38 UTCEG score recompute

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-54090?
CVE-2023-54090 is a critical-severity vulnerability; its CVE record was published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: ixgbe: Fix panic during XDP_TX with > 64 CPUs Commit 4fe815850bdc ("ixgbe: let the xdpdrv work with more than 64 cpus") adds support to allow XDP programs to run on systems with more than 64 CPUs by locking the XDP TX rings and…
When was the CVE record for CVE-2023-54090 published?
The CVE record for CVE-2023-54090 was published on December 24, 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-2023-54090 actively exploited?
CVE-2023-54090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-54090?
CVE-2023-54090 has a CVSS base score of 9.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2023-54090?
A fix for CVE-2023-54090 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54090 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-54090

Explore →

Is Your Infrastructure Affected by CVE-2023-54090?

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

Book a Demo →Browse All CVEs