CVE-2026-64632

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (HackerOne) lists Veeam ONE versions up to and including 13.0.2 as affected. No release containing a fix is confirmed on record.

A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
The EG Score, 8.5 of 10.
Exploitation0.4% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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.

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

August 26, 2026

Last Modified

September 3, 2026

Advisory Details (1)

Auto-updated Aug 26, 2026
No fix on record yet.
Web page

KB4892: Vulnerabilities Resolved in Veeam ONE 13.1

https://www.veeam.com/kb4892

Vendor Advisories for CVE-2026-64632(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64632?
CVE-2026-64632 is a high-severity vulnerability; its CVE record was published on August 26, 2026. A vulnerability allowing a low-privileged user to capture the NTLM credentials of the Reporter service account.
When was the CVE record for CVE-2026-64632 published?
The CVE record for CVE-2026-64632 was published on August 26, 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 September 3, 2026; the record at its source may have been updated since.
Is CVE-2026-64632 actively exploited?
CVE-2026-64632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64632?
CVE-2026-64632 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64632?
No fix for CVE-2026-64632 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (HackerOne) lists Veeam ONE versions up to and including 13.0.2 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-64632 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64632

Explore →

Is Your Infrastructure Affected by CVE-2026-64632?

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

Book a Demo →Browse All CVEs