CVE-2025-22085

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-04-16. 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-11221 (ENISA EUVD) · GHSA-j2pm-rwgr-r5gf (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:

RDMA/core: Fix use-after-free when rename device name

Syzbot reported a slab-use-after-free with the following call trace:

================================================================== BUG: KASAN: slab-use-after-free in nla_put+0xd3/0x150 lib/nlattr.c:1099 Read of size 5 at addr ffff888140ea1c60 by task syz.0.988/10025

CPU: 0 UID: 0 PID: 10025 Comm: syz.0.988 Not tainted 6.14.0-rc4-syzkaller-00859-gf77f12010f67 #0 Hardware name: Google Compute Engine, BIOS Google 02/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0x16e/0x5b0 mm/kasan/report.c:521 kasan_report+0x143/0x180 mm/kasan/report.c:634 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 nla_put+0xd3/0x150 lib/nlattr.c:1099 nla_put_string include/net/netlink.h:1621 [inline] fill_nldev_handle+0x16e/0x200 drivers/infiniband/core/nldev.c:265 rdma_nl_notify_event+0x561/0xef0 drivers/infiniband/core/nldev.c:2857 ib_device_notify_register+0x22/0x230 drivers/infiniband/core/device.c:1344 ib_register_device+0x1292/0x1460 drivers/infiniband/core/device.c:1460 rxe_register_device+0x233/0x350 drivers/infiniband/sw/rxe/rxe_verbs.c:1540 rxe_net_add+0x74/0xf0 drivers/infiniband/sw/rxe/rxe_net.c:550 rxe_newlink+0xde/0x1a0 drivers/infiniband/sw/rxe/rxe.c:212 nldev_newlink+0x5ea/0x680 drivers/infiniband/core/nldev.c:1795 rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline] rdma_nl_rcv+0x6dd/0x9e0 drivers/infiniband/core/netlink.c:259 netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline] netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1339 netlink_sendmsg+0x8de/0xcb0 net/netlink/af_netlink.c:1883 sock_sendmsg_nosec net/socket.c:709 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:724 ____sys_sendmsg+0x53a/0x860 net/socket.c:2564 ___sys_sendmsg net/socket.c:2618 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2650 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f42d1b8d169 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 ... RSP: 002b:00007f42d2960038 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f42d1da6320 RCX: 00007f42d1b8d169 RDX: 0000000000000000 RSI: 00004000000002c0 RDI: 000000000000000c RBP: 00007f42d1c0e2a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f42d1da6320 R15: 00007ffe399344a8

Allocated by task 10025: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x3f/0x80 mm/kasan/common.c:68 poison_kmalloc_redzone mm/kasan/common.c:377 [inline] __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:394 kasan_kmalloc include/linux/kasan.h:260 [inline] __do_kmalloc_node mm/slub.c:4294 [inline] __kmalloc_node_track_caller_noprof+0x28b/0x4c0 mm/slub.c:4313 __kmemdup_nul mm/util.c:61 [inline] kstrdup+0x42/0x100 mm/util.c:81 kobject_set_name_vargs+0x61/0x120 lib/kobject.c:274 dev_set_name+0xd5/0x120 drivers/base/core.c:3468 assign_name drivers/infiniband/core/device.c:1202 [inline] ib_register_device+0x178/0x1460 drivers/infiniband/core/device.c:1384 rxe_register_device+0x233/0x350 drivers/infiniband/sw/rxe/rxe_verbs.c:1540 rxe_net_add+0x74/0xf0 drivers/infiniband/sw/rxe/rxe_net.c:550 rxe_newlink+0xde/0x1a0 drivers/infiniband/sw/rxe/rxe.c:212 nldev_newlink+0x5ea/0x680 drivers/infiniband/core/nldev.c:1795 rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline] rdma_nl_rcv+0x6dd/0x9e0 drivers/infiniband/core/netlink.c:259 netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline] netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1339 netlink_sendmsg+0x8de/0xcb0 net ---truncated---

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 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.2%
EPSS %ILE
10th
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 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

April 16, 2025

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Jul 30, 2026
Patch available.
Web page

RDMA/core: Fix use-after-free when rename device name - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d6a9e7449e2a0c1e2934eee7880ba8bd1e464cd
Web page

RDMA/core: Fix use-after-free when rename device name - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Fix use-after-free when rename device name - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56ec8580be5174b2b9774066e60f1aad56d201db
Web page

RDMA/core: Fix use-after-free when rename device name - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d6460b9d2a3ee380940bdf47680751ef91cb88e

Vendor Advisories for CVE-2025-22085(2)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-10-27ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-10-27ubuntu
redhatkernel-0:6.12.0-55.25.1.el10_02025-08-04redhat
redhatkernel-0:5.14.0-570.30.1.el9_62025-07-28redhat
linuxKernel @ 6.12.23 (fixes >=6.12.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(3)

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 10× in last 7d / 42× 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 96 of 205 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-22085?
CVE-2025-22085 is a high-severity vulnerability; its CVE record was published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix use-after-free when rename device name Syzbot reported a slab-use-after-free with the following call trace: ================================================================== BUG: KASAN: slab-use-after-free in…
When was the CVE record for CVE-2025-22085 published?
The CVE record for CVE-2025-22085 was published on April 16, 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-2025-22085 actively exploited?
CVE-2025-22085 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22085?
CVE-2025-22085 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-22085?
A fix for CVE-2025-22085 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-22085 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-2025-22085

Explore →

Is Your Infrastructure Affected by CVE-2025-22085?

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

Book a Demo →Browse All CVEs