CVE-2026-46055

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. The CNA's CVSS baseline 7.1; sources differ by 0.0.

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

Also known asEUVD-2026-32437 (ENISA EUVD) · GHSA-mx5h-mw9c-r2fh (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.1%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

apparmor: Fix string overrun due to missing termination

When booting Ubuntu 26.04 with Linux 7.0-rc4 on an ARM64 Qualcomm Snapdragon X1 we see a string buffer overrun:

BUG: KASAN: slab-out-of-bounds in aa_dfa_match (security/apparmor/match.c:535) Read of size 1 at addr ffff0008901cc000 by task snap-update-ns/2120

CPU: 5 UID: 60578 PID: 2120 Comm: snap-update-ns Not tainted 7.0.0-rc4+ #22 PREEMPTLAZY Hardware name: LENOVO 83ED/LNVNB161216, BIOS NHCN60WW 09/11/2025 Call trace: show_stack (arch/arm64/kernel/stacktrace.c:501) (C) dump_stack_lvl (lib/dump_stack.c:122) print_report (mm/kasan/report.c:379 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:597) __asan_report_load1_noabort (mm/kasan/report_generic.c:378) aa_dfa_match (security/apparmor/match.c:535) match_mnt_path_str (security/apparmor/mount.c:244 security/apparmor/mount.c:336) match_mnt (security/apparmor/mount.c:371) aa_bind_mount (security/apparmor/mount.c:447 (discriminator 4)) apparmor_sb_mount (security/apparmor/lsm.c:719 (discriminator 1)) security_sb_mount (security/security.c:1062 (discriminator 31)) path_mount (fs/namespace.c:4101) __arm64_sys_mount (fs/namespace.c:4172 fs/namespace.c:4361 fs/namespace.c:4338 fs/namespace.c:4338) invoke_syscall.constprop.0 (arch/arm64/kernel/syscall.c:35 arch/arm64/kernel/syscall.c:49) el0_svc_common.constprop.0 (./include/linux/thread_info.h:142 (discriminator 2) arch/arm64/kernel/syscall.c:140 (discriminator 2)) do_el0_svc (arch/arm64/kernel/syscall.c:152) el0_svc (arch/arm64/kernel/entry-common.c:80 arch/arm64/kernel/entry-common.c:725) el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:744) el0t_64_sync (arch/arm64/kernel/entry.S:596)

Allocated by task 2120: kasan_save_stack (mm/kasan/common.c:58) kasan_save_track (./arch/arm64/include/asm/current.h:19 mm/kasan/common.c:70 mm/kasan/common.c:79) kasan_save_alloc_info (mm/kasan/generic.c:571) __kasan_kmalloc (mm/kasan/common.c:419) __kmalloc_noprof (./include/linux/kasan.h:263 mm/slub.c:5260 mm/slub.c:5272) aa_get_buffer (security/apparmor/lsm.c:2201) aa_bind_mount (security/apparmor/mount.c:442) apparmor_sb_mount (security/apparmor/lsm.c:719 (discriminator 1)) security_sb_mount (security/security.c:1062 (discriminator 31)) path_mount (fs/namespace.c:4101) __arm64_sys_mount (fs/namespace.c:4172 fs/namespace.c:4361 fs/namespace.c:4338 fs/namespace.c:4338) invoke_syscall.constprop.0 (arch/arm64/kernel/syscall.c:35 arch/arm64/kernel/syscall.c:49) el0_svc_common.constprop.0 (./include/linux/thread_info.h:142 (discriminator 2) arch/arm64/kernel/syscall.c:140 (discriminator 2)) do_el0_svc (arch/arm64/kernel/syscall.c:152) el0_svc (arch/arm64/kernel/entry-common.c:80 arch/arm64/kernel/entry-common.c:725) el0t_64_sync_handler (arch/arm64/kernel/entry-common.c:744) el0t_64_sync (arch/arm64/kernel/entry.S:596)

The buggy address belongs to the object at ffff0008901ca000 which belongs to the cache kmalloc-rnd-06-8k of size 8192 The buggy address is located 0 bytes to the right of allocated 8192-byte region [ffff0008901ca000, ffff0008901cc000)

The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x9101c8 head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:-1 pincount:0 flags: 0x8000000000000040(head|zone=2) page_type: f5(slab) raw: 8000000000000040 ffff000800016c40 fffffdffe2d14e10 ffff000800015c70 raw: 0000000000000000 0000000800010001 00000000f5000000 0000000000000000 head: 8000000000000040 ffff000800016c40 fffffdffe2d14e10 ffff000800015c70 head: 0000000000000000 0000000800010001 00000000f5000000 0000000000000000 head: 8000000000000003 fffffdffe2407201 fffffdffffffffff 00000000ffffffff head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000008 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff0008901cbf00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0008 ---truncated---

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
4th
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). 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 27, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
Patch available.
Web page

apparmor: Fix string overrun due to missing termination - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/828bf7929bedcb79b560b5b4e44f22abee07d31b
Web page

apparmor: Fix string overrun due to missing termination - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b877ef27adc8ec187b0418629169856e7264e01

Vendor Advisories for CVE-2026-46055(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 7.0.4 (fixes >=7.0.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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (135 versions)
  • every version up to 7.0.4-1: fixed in 7.0.4-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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 100 of 284 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. None are among the latest 100 rows. The 184 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-46055?
CVE-2026-46055 is a high-severity vulnerability; its CVE record was published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix string overrun due to missing termination When booting Ubuntu 26.04 with Linux 7.0-rc4 on an ARM64 Qualcomm Snapdragon X1 we see a string buffer overrun: BUG: KASAN: slab-out-of-bounds in aa_dfa_match…
When was the CVE record for CVE-2026-46055 published?
The CVE record for CVE-2026-46055 was published on May 27, 2026. 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-2026-46055 actively exploited?
CVE-2026-46055 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46055?
CVE-2026-46055 has a CVSS base score of 7.1 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-46055?
A fix for CVE-2026-46055 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46055 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-2026-46055

Explore →

Is Your Infrastructure Affected by CVE-2026-46055?

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

Book a Demo →Browse All CVEs