CVE-2023-52796

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-05-21. 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-59513 (ENISA EUVD) · GHSA-68x5-x32c-8c8w (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:

ipvlan: add ipvlan_route_v6_outbound() helper

Inspired by syzbot reports using a stack of multiple ipvlan devices.

Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed.

Also make sure ipvlan_process_v4_outbound() is not inlined.

We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices.

BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc9000e804000..ffffc9000e808000) stack guard page: 0000 [#1] SMP KASAN CPU: 0 PID: 13442 Comm: syz-executor.4 Not tainted 6.1.52-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023 RIP: 0010:kasan_check_range+0x4/0x2a0 mm/kasan/generic.c:188 Code: 48 01 c6 48 89 c7 e8 db 4e c1 03 31 c0 5d c3 cc 0f 0b eb 02 0f 0b b8 ea ff ff ff 5d c3 cc 00 00 cc cc 00 00 cc cc 55 48 89 e5 <41> 57 41 56 41 55 41 54 53 b0 01 48 85 f6 0f 84 a4 01 00 00 48 89 RSP: 0018:ffffc9000e804000 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff817e5bf2 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff887c6568 RBP: ffffc9000e804000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff92001d0080c R13: dffffc0000000000 R14: ffffffff87e6b100 R15: 0000000000000000 FS: 00007fd0c55826c0(0000) GS:ffff8881f6800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffc9000e803ff8 CR3: 0000000170ef7000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <#DF>

[] __kasan_check_read+0x11/0x20 mm/kasan/shadow.c:31 [] instrument_atomic_read include/linux/instrumented.h:72 [inline] [] _test_bit include/asm-generic/bitops/instrumented-non-atomic.h:141 [inline] [] cpumask_test_cpu include/linux/cpumask.h:506 [inline] [] cpu_online include/linux/cpumask.h:1092 [inline] [] trace_lock_acquire include/trace/events/lock.h:24 [inline] [] lock_acquire+0xe2/0x590 kernel/locking/lockdep.c:5632 [] rcu_lock_acquire+0x2e/0x40 include/linux/rcupdate.h:306 [] rcu_read_lock include/linux/rcupdate.h:747 [inline] [] ip6_pol_route+0x15d/0x1440 net/ipv6/route.c:2221 [] ip6_pol_route_output+0x50/0x80 net/ipv6/route.c:2606 [] pol_lookup_func include/net/ip6_fib.h:584 [inline] [] fib6_rule_lookup+0x265/0x620 net/ipv6/fib6_rules.c:116 [] ip6_route_output_flags_noref+0x2d9/0x3a0 net/ipv6/route.c:2638 [] ip6_route_output_flags+0xca/0x340 net/ipv6/route.c:2651 [] ip6_route_output include/net/ip6_route.h:100 [inline] [] ipvlan_process_v6_outbound drivers/net/ipvlan/ipvlan_core.c:473 [inline] [] ipvlan_process_outbound drivers/net/ipvlan/ipvlan_core.c:529 [inline] [] ipvlan_xmit_mode_l3 drivers/net/ipvlan/ipvlan_core.c:602 [inline] [] ipvlan_queue_xmit+0xc33/0x1be0 drivers/net/ipvlan/ipvlan_core.c:677 [] ipvlan_start_xmit+0x49/0x100 drivers/net/ipvlan/ipvlan_main.c:229 [] netdev_start_xmit include/linux/netdevice.h:4966 [inline] [] xmit_one net/core/dev.c:3644 [inline] [] dev_hard_start_xmit+0x320/0x980 net/core/dev.c:3660 [] __dev_queue_xmit+0x16b2/0x3370 net/core/dev.c:4324 [] dev_queue_xmit include/linux/netdevice.h:3067 [inline] [] neigh_hh_output include/net/neighbour.h:529 [inline] [

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
15th
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

May 21, 2024

Last Modified

September 23, 2025

Advisory Details (8)

Auto-updated Sep 22, 2026
Patch available.
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18f039428c7df183b09c69ebf10ffd4e521035d2
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03cddc4df8c6be47fd27c8f8b87e5f9a989e1458
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8872dc638c24bb774cd2224a69d72a7f661a4d56
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/732a67ca436887b594ebc43bb5a04ffb0971a760
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43b781e7cb5cd0b435de276111953bf2bacd1f02
Web page

ipvlan: add ipvlan_route_v6_outbound() helper - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f64cad3ac38ac5978b53c40e6c5e6fd3477c68f

Vendor Advisories for CVE-2023-52796(3)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-427.31.1.el9_42024-08-15redhat
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
linuxKernel @ 4.19.300 (fixes >=3.19.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 (35 versions)
  • every version up to 5.10.205-1: fixed in 5.10.205-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (11 versions)
  • every version up to 6.1.64-1: fixed in 6.1.64-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.6.8-1: fixed in 6.6.8-1
—

Weakness Classification(1)

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52796?
CVE-2023-52796 is a high-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an…
When was the CVE record for CVE-2023-52796 published?
The CVE record for CVE-2023-52796 was published on May 21, 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 September 23, 2025; the record at its source may have been updated since.
Is CVE-2023-52796 actively exploited?
CVE-2023-52796 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (15th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52796?
CVE-2023-52796 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52796?
A fix for CVE-2023-52796 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52796 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-52796

Explore →

Is Your Infrastructure Affected by CVE-2023-52796?

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

Book a Demo →Browse All CVEs