Veeam ONE 13.1.0.7233: scanners still report finding (Reporter shows 13.1.0.7034)
Summary
After installing Veeam ONE 13.1 Patch 0 (build 13.1.0.7233), some vulnerability scanners keep reporting the finding for CVE-2026-65641. The Veeam ONE Reporter executable stays at version 13.1.0.7034 because the patch does not modify it. This is a false positive; Veeam documents an exception in the scanner as the way to handle it.
Symptoms
A vulnerability scanner still flags Veeam ONE after build 13.1.0.7233 was installed. The finding is based only on the Reporter component version 13.1.0.7034.
Affected
- Veeam ONE 13.1 with Patch 0 (build 13.1.0.7233) installed
- Vulnerability scanners that rely only on the Veeam ONE Reporter executable version
Workaround
- Confirm that build 13.1.0.7233 is installed on the Veeam ONE server.
- If the scanner finding is based only on the Reporter component version, configure an exception for that specific detection in the scanner.
Fix
Not a product defect: the Reporter component is unchanged by this patch, so its version number stays the same. Verify the installed build 13.1.0.7233 instead. The later build 13.1.0.7940 (Patch 1, 2026-10-27) is also available; the sources do not state whether it changes the Reporter version.
Recommendation
Check the installed Veeam ONE build, document the verification and set a narrowly scoped scanner exception for this detection only. Do not suppress other findings. Plan the update to Patch 1 (13.1.0.7940), which Veeam recommends for all Veeam ONE 13.1 deployments.
Sources
- List of Security Fixes and Improvements in Veeam ONE Vendor · www.veeam.com
- Release Information for Veeam ONE 13 and Updates Vendor · www.veeam.com
Compiled from the sources listed and translated with AI (Claude); status and dates come from the vendor. The vendor’s statements are authoritative. Updated 1 Nov 2026, 15:36.
Where the information comes from
We continuously read the vendors’ official sources, community reports and trade media and summarise them in our own words, with a link to the source:
- Microsoft: Windows release health (Windows 10/11, Server 2016 to 2025), Windows message center, known issues of Microsoft 365 Apps (Outlook, Excel, Word, PowerPoint), Edge, Intune, Autopilot, Windows 365 and Entra Connect, Microsoft KB articles with timelines, Exchange and Windows IT Pro blogs, optionally Microsoft 365 service health and message center
- other vendors: Veeam KB, Citrix (known issues), Ubuntu and Debian (regressions), Broadcom (VMware), Fortinet, Cisco, Mozilla, Let’s Encrypt
- community (title, short excerpt and link only, without the names of the authors): Microsoft Q&A, Microsoft Tech Community (discussions), Veeam R&D Forums, Eleven Forum
- targeted web research with AI (Claude), e.g. on the updates of the month – this also finds discussions on Reddit and in forums; such entries are labelled as community reports until the vendor confirms them
- early warning from trade media (title and link only): Born’s Tech and Windows World, BleepingComputer, AskWoody, Windows Latest, Windows Central, gHacks, The Windows Club, Deskmodder, Dr. Windows, WindowsArea, Frankys Web, heise online
Summary and translation with AI (Claude by Anthropic) – without any data of visitors.
Affected? We can help.
We check whether your systems are affected, apply workarounds properly and plan for dated changes in good time.