CVE-2026-64252

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 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-48661 (ENISA EUVD) · GHSA-4gm6-q4p9-46cj (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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS

In 64-bit configurations calling the initial console output handler from a kernel thread other than the initial one will result in a situation where the stack has been placed in the XKPHYS 64-bit memory segment and consequently so has been the buffer allocated there that is used as the argument corresponding to the `%s' output conversion specifier for the firmware's printf() entry point.

This 64-bit address will then be truncated by 32-bit firmware, resulting in an attempt to access the wrong memory location, which in turn will cause all kinds of unpredictable behaviour, such as a kernel crash:

Console: colour dummy device 160x64 Calibrating delay loop... 49.36 BogoMIPS (lpj=192512) pid_max: default: 32768 minimum: 301 CPU 0 Unable to handle kernel paging request at virtual address 000000000203bd00, epc == ffffffffbfc08364, ra == ffffffffbfc08800 Oops[#1]: CPU: 0 PID: 0 Comm: swapper Not tainted 5.18.0-rc2-00254-gfb649bda6f56-dirty #121 $ 0 : 0000000000000000 0000000000000001 0000000000000023 ffffffff80684ba0 $ 4 : 000000000203bd00 ffffffffbfc0f3b4 ffffffffffffffff 0000000000000073 $ 8 : 0a303d7469000000 0000000000000000 0000000000000073 ffffffffbfc0f473 $12 : 0000000000000002 0000000000000000 ffffffff80684c1c 0000000000000000 $16 : 0000000000000000 ffffffff80596dc9 0000000000000000 ffffffffbfc09240 $20 : ffffffff80684c40 ffffffffbfc0f400 000000000000002d 000000000000002b $24 : ffffffffffffffbf 000000000203bd00 $28 : ffffffff805f0000 ffffffff80684b58 0000000000000030 ffffffffbfc08800 Hi : 0000000000000000 Lo : 0000000000000aa8 epc : ffffffffbfc08364 0xffffffffbfc08364 ra : ffffffffbfc08800 0xffffffffbfc08800 Status: 140120e2 KX SX UX KERNEL EXL Cause : 00000008 (ExcCode 02) BadVA : 000000000203bd00 PrId : 00000430 (R4000SC) Modules linked in: Process swapper (pid: 0, threadinfo=(____ptrval____), task=(____ptrval____), tls=0000000000000000) Stack : 0000000000000000 0000000000000000 0000000000000000 0000004d0000004d 80684cc0806a2a40 80596dc80000004d 8061000000000000 bfc0850c80684c38 0000000000000000 000000000203bd00 0000000000000000 0000000000000000 0000000000000000 00000000bfc0f3b4 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000002500000000 0000000000000000 0000000000000000 802c1a7400000000 0203bd0080596dc8 0203bd4d69000000 6c61632000000018 5f746567646e6172 6c616320625f6d6f 5f736e5f6d6f7266 206361323778302b 303d74696e726320 806a0a38806b0000 806a0a38806b0000 00000000806b0000 80683c58806b0000 ... Call Trace:

Code: a082ffff 03e00008 00601021 <80820000> 00001821 10400005 24840001 80820000 24630001

---[ end trace 0000000000000000 ]--- Kernel panic - not syncing: Fatal exception in interrupt

KN04 V2.1k (PC: 0xa0026768, SP: 0x806848e8) >>

In this case the pointer in $4 was truncated from 0x980000000203bd00 to 0x000000000203bd00.

This may happen when no final console driver has been enabled in the configuration and consequently the initial console continues being used late into bootstrap or with an upcoming change that will switch the zs driver to use a platform device, which in turn will make the console handover happen only after other kernel threads have already been started.

Fix the issue by making the buffer static and initdata, and therefore placed in the CKSEG0 32-bit compatibility segment, observing that the console output handler is called with the console lock held, implying no need for this code to be reentrant. Add an assertion to verify the buffer actually has been placed in a compatibility segment.

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.2% × 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.2%
EPSS %ILE
5th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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: 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.

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

July 24, 2026

Last Modified

August 17, 2026

Advisory Details (8)

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

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

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

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e22b6fc6532cd566dad6d89d8fb3885248e364a
Web page

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

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

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7fb13fd35110ebe95eb053faf79d018f51144d85
Web page

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e61fc2e06e44b6d30248cc5bc47a58e75c2b43e
Web page

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35212f2adc2cf15122b96b987519de235b855e46
Web page

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

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

MIPS: DEC: Prevent initial console buffer from landing in XKPHYS - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07c245bc39f94481fd75ff1ed54f7ab97111f3dd

Vendor Advisories for CVE-2026-64252(2)

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 @ 5.10.260 (fixes >=2.6.12)—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)
  • every version up to 5.10.262-1: fixed in 5.10.262-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)
  • every version up to 6.1.177-1~deb11u1: fixed in 6.1.177-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)
  • every version up to 6.1.177-1: fixed in 6.1.177-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)
  • every version up to 6.12.95-1: fixed in 6.12.95-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)
  • every version up to 7.1.3-1: fixed in 7.1.3-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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 185 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 85 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-64252?
CVE-2026-64252 is a medium-severity vulnerability; its CVE record was published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: MIPS: DEC: Prevent initial console buffer from landing in XKPHYS In 64-bit configurations calling the initial console output handler from a kernel thread other than the initial one will result in a situation where the stack has…
When was the CVE record for CVE-2026-64252 published?
The CVE record for CVE-2026-64252 was published on July 24, 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 17, 2026; the record at its source may have been updated since.
Is CVE-2026-64252 actively exploited?
CVE-2026-64252 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64252?
CVE-2026-64252 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64252?
A fix for CVE-2026-64252 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64252 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-64252

Explore →

Is Your Infrastructure Affected by CVE-2026-64252?

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

Book a Demo →Browse All CVEs