Skip to content

Veeam Agent for Microsoft Windows CVE-2026-32996

Summary

CVE-2026-32996 (CVSS 7.3, vendor-scored) is a local privilege escalation in Veeam Agent for Microsoft Windows ≤ 13.0.1.2067 (all earlier version-13 builds) that lets any local user reach NT AUTHORITY\SYSTEM on every endpoint running the agent. The mechanism is a two-part design failure: the Veeam Endpoint Backup service handles elevated client sessions over the local gRPC named pipe \\.\pipe\Veeam\VAW\ServiceConnectionPipe and caches an elevated administrator principal against a client-controlled session UID that is not bound to the requesting user or the connection, and the elevated session UIDs are written in the clear to C:\ProgramData\Veeam\Endpoint\Svc.VeeamEndpointBackup.log, which standard users can read. An unprivileged attacker opens the log, takes a currently-valid elevated UID, replays it over the pipe, and the service executes commands as SYSTEM. A public GitHub PoC (Sep 14, 2026, technical details + exploit code released together) demonstrates it by running whoami and writing the output to a file. Arctic Wolf published a security bulletin on Sep 16 warning the PoC raises exploitation likelihood, and on September 22, 2026 The Hacker News reported Arctic Wolf warning of ACTIVE exploitation of the flaw. Fix = upgrade Veeam Backup & Replication to 13.0.2.29 or later, which updates the Windows agent to build 13.0.3.1220 (Veeam KB4852 / KB4738); Arctic Wolf found no reliable vendor-supported workaround, only access restriction. No CVE is in CISA KEV for this at sweep time (KEV 2026.09.21 / 1,717 checked by this wiki ~07:30 UTC Sep 22); no actor, victim count, or post-compromise activity has been published.

Why this shape is dangerous: backup agents are deliberately deployed everywhere, run as SYSTEM everywhere, and are excluded from the hardening attention given to laptops and servers. This is the second backup-agent local privilege escalation in one week on this wiki's radar, the Acronis Backup plugin for cPanel/Plesk CVE-2026-87886 was KEV-listed Sep 16 with vendor-confirmed "limited, targeted exploitation" (CISA KEV Sep 16 page). Two backup products, same escalation class, one week: backup agents are a standing LPE surface, SYSTEM-resident services with local IPC reachable by unprivileged users.

Tags

Vulnerability mechanics (from Arctic Wolf's bulletin, canonical post fetched full-text by this wiki)

  • Surface: the VeeamEndpointBackup service on Windows endpoints, reachable locally via the gRPC named pipe \\.\pipe\Veeam\VAW\ServiceConnectionPipe.
  • Primitive, part 1, unbound elevated principal: the service caches an elevated administrator principal against a client-controlled session UID. The UID is not bound to the requesting user or to the connection, so possession of a valid UID is the only thing the service checks.
  • Primitive, part 2, the UID leaks to everyone: elevated session UIDs are written to C:\ProgramData\Veeam\Endpoint\Svc.VeeamEndpointBackup.log, a path readable by standard users. No race, no memory scraping, no token theft, the credential is logged in the clear for any local account to read.
  • Result: standard user → read log → replay UID over the pipe → arbitrary command execution as NT AUTHORITY\SYSTEM. PoC demo: whoami output written to a file.
  • Affected: Veeam Agent for Microsoft Windows 13.0.1.2067 and all earlier v13 builds.
  • Fixed: agent build 13.0.3.1220, delivered by upgrading Veeam Backup & Replication to 13.0.2.29+ (KB4852, KB4738). Confirm both the agent service and tray components run the fixed version after upgrade.
  • Workaround: none reliable per Arctic Wolf's review of public sources. Risk reduction = restrict local/interactive access, restrict local-admin and backup-operator privileges, prioritize patching on shared workstations, servers, admin workstations, help-desk and backup-operator machines.

Timeline (public record)

  • Sep 14, 2026, public technical details and PoC exploit code released on GitHub (Arctic Wolf bulletin's trigger date).
  • Sep 16, 2026, Arctic Wolf security bulletin "UPDATE: Active Exploitation CVE-2026-32996 of Veeam Agent" published (canonical: arcticwolf.com/resources/blog/update-active-exploitation-cve-2026-32996-of-veeam-agent/), warning of increased exploitation likelihood; notes its own agents (AWN Agent / Aurora Focus) detect multiple stages of the exploitation chain.
  • Sep 22, 2026, The Hacker News reports Arctic Wolf warning of active exploitation (same article confirms the Zyxel GS1900 CVE-2026-7273 KEV row the day after this wiki captured it, Sep 18 KEV page follow-up). No KEV row for CVE-2026-32996 at this wiki's Sep 22 ~07:30 UTC check.

Durable reads

  1. A world-readable log line is a credential if a service accepts it as one. The primitive is not memory corruption, it's an authorization token written to disk without access control. Any security-relevant identifier written to a service log must be treated as a secret: same class as the on-wiki story about elevated tokens/cookies in request logs. Static hunt against YOUR services: grep service logging paths for session identifiers, principals, nonces, UIDs that any auth path accepts as input.
  2. Caching an elevated principal against caller-supplied identity = confused deputy. "Not bound to the requesting user or connection" is the whole bug in one phrase: the cache key is attacker-chosen and the cache value is SYSTEM. Any elevated session cache keyed on client input fails this way.
  3. Backup agents are a standing LPE surface. Two products in one week (Veeam v13 LPE active- exploitation reported; Acronis cPanel/Plesk plugin CVE-2026-87886 KEV-listed with targeted exploitation). Inventory backup agents like privileged services, not like utilities: they run as SYSTEM, talk over local IPC, and ship to every endpoint including shared and kiosk-class machines.

Hunt guidance

  • On hosts: standard-user reads of C:\ProgramData\Veeam\Endpoint\Svc.VeeamEndpointBackup.log (file-access auditing or EDR file-integrity on that exact path is the pre-exploit signal, the read IS the attack).
  • Post-exploit: SYSTEM-owned child processes parented by the Veeam Endpoint Backup service whose process lineage traces back to a non-elevated interactive user; cmd.exe/whoami-style one-shot SYSTEM spawns on hosts where no admin is logged in.
  • Pipe telemetry (where available): connections to \\.\pipe\Veeam\VAW\ServiceConnectionPipe from processes/binaries other than Veeam's own tray/agent components.
  • Exposure triage: enumerate endpoints on agent 13.0.1.2067 or earlier v13; prioritize multi-user workstations, terminal/RDS hosts, backup-operator and help-desk machines.

Caveats

  • Arctic Wolf's public bulletin (fetched full-text by this wiki Sep 22) documents the PoC-driven exploitation-likelihood framing and its detection posture; the "active exploitation" wording appears in THN's Sep 22 report of Arctic Wolf's warning. Arctic Wolf has not published victim counts, actors, or post-compromise activity; CISA has no KEV row yet. Treat "active exploitation" as the IR vendor's reported observation, scoped accordingly, until a named victim or IOC set lands.
  • Veeam's own advisories (KB4852 / KB4738) were not independently fetched at capture time (bot-gated); version/build data above is per Arctic Wolf's bulletin quoting them.

Sources