CVE-2024-57999

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 2025-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-5253 (ENISA EUVD) · GHSA-2qw8-jh79-6qc9 (GitHub Security Advisories)Source: ENISA EUVD

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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW

Power Hypervisor can possibily allocate MMIO window intersecting with Dynamic DMA Window (DDW) range, which is over 32-bit addressing.

These MMIO pages needs to be marked as reserved so that IOMMU doesn't map DMA buffers in this range.

The current code is not marking these pages correctly which is resulting in LPAR to OOPS while booting. The stack is at below

BUG: Unable to handle kernel data access on read at 0xc00800005cd40000 Faulting instruction address: 0xc00000000005cdac Oops: Kernel access of bad area, sig: 11 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries Modules linked in: af_packet rfkill ibmveth(X) lpfc(+) nvmet_fc nvmet nvme_keyring crct10dif_vpmsum nvme_fc nvme_fabrics nvme_core be2net(+) nvme_auth rtc_generic nfsd auth_rpcgss nfs_acl lockd grace sunrpc fuse configfs ip_tables x_tables xfs libcrc32c dm_service_time ibmvfc(X) scsi_transport_fc vmx_crypto gf128mul crc32c_vpmsum dm_mirror dm_region_hash dm_log dm_multipath dm_mod sd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua t10_pi crc64_rocksoft_generic crc64_rocksoft sg crc64 scsi_mod Supported: Yes, External CPU: 8 PID: 241 Comm: kworker/8:1 Kdump: loaded Not tainted 6.4.0-150600.23.14-default #1 SLE15-SP6 b44ee71c81261b9e4bab5e0cde1f2ed891d5359b Hardware name: IBM,9080-M9S POWER9 (raw) 0x4e2103 0xf000005 of:IBM,FW950.B0 (VH950_149) hv:phyp pSeries Workqueue: events work_for_cpu_fn NIP: c00000000005cdac LR: c00000000005e830 CTR: 0000000000000000 REGS: c00001400c9ff770 TRAP: 0300 Not tainted (6.4.0-150600.23.14-default) MSR: 800000000280b033 CR: 24228448 XER: 00000001 CFAR: c00000000005cdd4 DAR: c00800005cd40000 DSISR: 40000000 IRQMASK: 0 GPR00: c00000000005e830 c00001400c9ffa10 c000000001987d00 c00001400c4fe800 GPR04: 0000080000000000 0000000000000001 0000000004000000 0000000000800000 GPR08: 0000000004000000 0000000000000001 c00800005cd40000 ffffffffffffffff GPR12: 0000000084228882 c00000000a4c4f00 0000000000000010 0000080000000000 GPR16: c00001400c4fe800 0000000004000000 0800000000000000 c00000006088b800 GPR20: c00001401a7be980 c00001400eff3800 c000000002a2da68 000000000000002b GPR24: c0000000026793a8 c000000002679368 000000000000002a c0000000026793c8 GPR28: 000008007effffff 0000080000000000 0000000000800000 c00001400c4fe800 NIP [c00000000005cdac] iommu_table_reserve_pages+0xac/0x100 LR [c00000000005e830] iommu_init_table+0x80/0x1e0 Call Trace: [c00001400c9ffa10] [c00000000005e810] iommu_init_table+0x60/0x1e0 (unreliable) [c00001400c9ffa90] [c00000000010356c] iommu_bypass_supported_pSeriesLP+0x9cc/0xe40 [c00001400c9ffc30] [c00000000005c300] dma_iommu_dma_supported+0xf0/0x230 [c00001400c9ffcb0] [c00000000024b0c4] dma_supported+0x44/0x90 [c00001400c9ffcd0] [c00000000024b14c] dma_set_mask+0x3c/0x80 [c00001400c9ffd00] [c0080000555b715c] be_probe+0xc4/0xb90 [be2net] [c00001400c9ffdc0] [c000000000986f3c] local_pci_probe+0x6c/0x110 [c00001400c9ffe40] [c000000000188f28] work_for_cpu_fn+0x38/0x60 [c00001400c9ffe70] [c00000000018e454] process_one_work+0x314/0x620 [c00001400c9fff10] [c00000000018f280] worker_thread+0x2b0/0x620 [c00001400c9fff90] [c00000000019bb18] kthread+0x148/0x150 [c00001400c9fffe0] [c00000000000ded8] start_kernel_thread+0x14/0x18

There are 2 issues in the code

  • The index is "int" while the address is "unsigned long". This results in
negative value when setting the bitmap.
  • The DMA offset is page shifted but the MMIO range is used as-is (64-bit
address). MMIO address needs to be page shifted as well.

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.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
19th
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

February 27, 2025

Last Modified

October 30, 2026

Advisory Details (3)

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

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

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

powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7043d58ecd1381674f5b2c894deb6986a1a4896b

Vendor Advisories for CVE-2024-57999(2)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (6.8.0-1033.35~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2026.27) @ noble2026-10-30ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1031.35) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1022.23) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26~24.04.1) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-64.67~22.04.1) @ jammy2026-10-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-64.67.1) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1029.30) @ noble2026-10-30ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-64.67) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-64k (6.11.0-1016.17) @ oracular2026-10-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1025.26) @ noble2026-10-30ubuntu
linuxKernel @ 6.12.13 (fixes >=5.15.0)—osv
linuxKernel @ 6.6.160 (fixes >=5.15.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.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.13-1: fixed in 6.12.13-1
—

Additional Vendor Advisories

(12)

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 7× in last 7d / 52× 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 95 of 221 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 126 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-57999?
CVE-2024-57999 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries/iommu: IOMMU incorrectly marks MMIO range in DDW Power Hypervisor can possibily allocate MMIO window intersecting with Dynamic DMA Window (DDW) range, which is over 32-bit addressing. These MMIO pages needs to be…
When was the CVE record for CVE-2024-57999 published?
The CVE record for CVE-2024-57999 was published on February 27, 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2024-57999 actively exploited?
CVE-2024-57999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-57999?
CVE-2024-57999 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-57999?
A fix for CVE-2024-57999 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-57999 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-2024-57999

Explore →

Is Your Infrastructure Affected by CVE-2024-57999?

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

Book a Demo →Browse All CVEs