A Veeam Agent flaw lets local users gain SYSTEM privileges. A public PoC is available, raising the risk of exploitation on shared Windows systems.
If you’re running Veeam Agent on a Windows endpoint with more than one local user, now’s the time to check the version, not tomorrow.
On September 14, 2026, public technical details and a proof-of-concept exploit dropped for CVE-2026-32996. From that point on, the odds of active exploitation went up considerably, because once working code sits on GitHub, anyone can copy it and adapt it in an afternoon. Arctic Wolf already flagged this in a bulletin.
“On September 14, 2026, public technical details and proof-of-concept (PoC) exploit code were released for CVE-2026-32996, increasing the likelihood of exploitation attempts against affected Veeam Agent for Microsoft Windows deployments.” warns Arctic Wolf.
The flaw hits Veeam Agent for Microsoft Windows up through version 13.0.1.2067, and it covers every earlier version 13 build too. This is a local privilege escalation bug, so an attacker needs local access to the machine first, but the payoff is serious: a low-privileged user can jump all the way to NT AUTHORITY\SYSTEM. On a shared endpoint, that jump is all it takes to fully own the box.
The root cause sits in how the Veeam Endpoint Backup service handles elevated client sessions over its local gRPC named pipe. As Arctic Wolf explains it:
“The issue stems from the Veeam Endpoint Backup service’s handling of elevated client sessions over the local gRPC named pipe \\.\pipe\Veeam\VAW\ServiceConnectionPipe.” continues the report. “The service caches an elevated administrator principal against a client-controlled session UID that is not bound to the requesting user or connection.”
In simple terms, the service trusts a session ID that the user can control. It does not check whether that ID actually belongs to the person making the request. It is like giving someone your house keys just because they know your address, without checking who they are.
The attack is also very easy to carry out. These elevated session IDs are stored in a log file that any standard user can read. An attacker with basic access to the machine can open the file, copy a valid ID, and use it to run commands with SYSTEM privileges. As Arctic Wolf exp
“Because elevated session UIDs are written to C:\ProgramData\Veeam\Endpoint\Svc.VeeamEndpointBackup.log, which standard users can read, an attacker can obtain a valid UID and abuse it to execute commands as SYSTEM.” continues the report. “The public GitHub PoC demonstrates this by running whoami and writing the output to a file.”
The public GitHub PoC proves the point by running whoami and writing the output to a file, just enough to show it works. No sophisticated attack chain required. Reading a text file is the whole exploit.
Arctic Wolf recommends prioritizing patching on shared workstations, servers, administrator workstations, and any system where local user access exists or where compromising a low-privileged account could lead to full endpoint takeover. Basically, anywhere more than one person touches that machine.
The fix is straightforward, but rolling it out across many systems may take some work. Upgrade Veeam Backup & Replication to version 13.0.2.29 or later. This also updates the Agent to build 13.0.3.1220, which includes the fix.
Before upgrading, identify all endpoints still running 13.0.1.2067 or earlier and prioritize systems with multiple local users or privileged tasks. After the update, check that both the service and tray components are running the fixed version. A partially completed update will not protect the system.
There is no official workaround for systems that cannot be patched immediately. As a temporary measure, restrict local and interactive access to affected machines and limit local administrator and backup operator privileges to users who actually need them.
Arctic Wolf says it can detect multiple stages of this exploitation chain, and customers running the AWN Agent or Aurora Focus get multi-stage endpoint coverage. But detection is a safety net, not a fix. As the company puts it, upgrading remains the primary remediation here, and that’s the one step nobody should skip while waiting on anything else.
Follow me on Twitter: @securityaffairs and Facebook and Mastodon
Pierluigi Paganini
(SecurityAffairs – hacking, Veeam)
Entrar
