CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Veeam Recovery Orchestrator

product · product:veeam-recovery-orchestrator

Coverage
1
first 2026-10-31 → last 2026-11-15
Latest activity
2026-11-15
Linux TCP use-after-free: Sophos hotfix and Ubuntu generic kernels out; WatchGuard, Fortinet have no fixed…
Peak priority
notable
1 notable
Targets
technology
sectors: technology
Sources cited
22
21 hosts

Action items (3)

Do-now tasks recorded on the entries about Veeam Recovery Orchestrator, newest first. Check the date before acting on an older one.

  • On every internet-facing Linux server and every XenServer or XCP-ng host with its Workload Balancing and Conversion Manager appliances, install the vendor's fixed kernel or firmware and reboot, then confirm the running version.
    2026-10-31CVE-2026-98432
  • On Veeam estates, run Veeam Updater on the appliances, install the private fix for the Linux helper appliances of Windows-based Backup & Replication and of Recovery Orchestrator 13.1, redeploy virtual labs and helper appliances that stay deployed and replace recovery media made before the update.
    2026-10-31CVE-2026-98432
  • On hosts that cannot reboot yet, drop IPv4 TCP packets that carry IP options ahead of the TCP stack as CIQ, AWS and Vates describe, after testing on one non-production host because it also drops legitimate option-bearing traffic; disabling MPTCP alone does not close the path.
    2026-10-31CVE-2026-98432

Defender insights

What each entry about Veeam Recovery Orchestrator tells a defender to do, newest first.

2026-10-31NOTABLELinux TCP use-after-free: Sophos hotfix and Ubuntu generic kernels out; WatchGuard, Fortinet have no fixed build

Exposure · detection

Story timeline

  1. 2026-10-31CVE-2026-98432, Linux kernel IPv4 TCP: a use-after-free in connection setup, present since 4.4, has an Anthropic-built remote root exploit against MPTCP listeners that CloudLinux could not reproduce; Citrix XenServer, XCP-ng, MikroTik, Red Hat, Debian, CIQ, Amazon Linux, Ubuntu's generic kernels for 22.04 to 26.10 and Sophos have fixes, Ubuntu 20.04 and older and some HWE, FIPS, NVIDIA and Azure variant kernels are in progress and WatchGuard and Fortinet have none for their products (CVSS 9.8)
    trending-vulnerabilitiesLinux TCP use-after-free: Sophos hotfix and Ubuntu generic kernels out; WatchGuard, Fortinet have no fixed build

Hunting pivots

Releases covered
Veeam Recovery Orchestrator
ATT&CK techniques (2 across 2 tactics)

2 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application
  • ImpactEndpoint Denial of Service: Application or System Exploitation

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-31/cve-2026-98432-linux-kernel-tcp-uaf-mptcp-remote-root · ATT&CK page ↗

Impact TA0040

T1499.004Endpoint Denial of Service: Application or System Exploitation×1

Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users. Some systems may automatically restart critical applications and services when crashes occur, but they can likely be re-exploited to cause a persistent denial of service (DoS) condition.

Evidence: 2026-10-31/cve-2026-98432-linux-kernel-tcp-uaf-mptcp-remote-root · ATT&CK page ↗

Entries about Veeam Recovery Orchestrator (1)

2026-10-31 · view entry permalink →

NOTABLECVE-2026-98432updatedNATOB2

CVE-2026-98432, Linux kernel IPv4 TCP: a use-after-free in connection setup, present since 4.4, has an Anthropic-built remote root exploit against MPTCP listeners that CloudLinux could not reproduce; Citrix XenServer, XCP-ng, MikroTik, Red Hat, Debian, CIQ, Amazon Linux, Ubuntu's generic kernels for 22.04 to 26.10 and Sophos have fixes, Ubuntu 20.04 and older and some HWE, FIPS, NVIDIA and Azure variant kernels are in progress and WatchGuard and Fortinet have none for their products (CVSS 9.8)

The Linux kernel CVE team published CVE-2026-98432 on 2026-10-15; the kernel.org CNA scores it 9.8 while upstream rates it 8.1 with high attack complexity (CIQ, 2026-10-30). It is a use-after-free in the IPv4 TCP connection setup path, introduced in Linux 4.4 and fixed upstream in 6.12.113, 6.18.56, 7.2.10 and 7.3-rc7 (Linux kernel CVE team, 2026-10-15). An unauthenticated peer starts it by sending TCP SYN packets that carry IPv4 options, and a retransmitted SYN can then touch the freed option memory (CIQ, 2026-10-30).

Anthropic wrote on 2026-10-27 that Claude produced an exploit that gives a remote attacker root on a Linux server with a multipath TCP (MPTCP) listener (Anthropic, 2026-10-27), but CloudLinux's kernel team could not reproduce the claim (CloudLinux, 2026-11-02). Akamai is not aware of a public working exploit and says disabling MPTCP alone does not prevent exploitation (Akamai, 2026-11-02), whereas Vates, XCP-ng and WatchGuard say a public exploit exists or circulates (XCP-ng, 2026-11-04; Vates, 2026-11-04; WatchGuard, 2026-11-03). No source reports attacks, and NCSC-NL judges large-scale abuse unlikely given the exploit's complexity (NCSC-NL, 2026-10-30).

Debian, Red Hat, CIQ and AWS have fixed kernels (Debian Security Tracker, 2026-11-03; Red Hat, 2026-11-03; CIQ, 2026-11-01; AWS, 2026-11-02), and Ubuntu's tracker, last updated 2026-11-10, lists 22.04 LTS to 26.10 as fixed (linux 5.15.0-203.213, 6.8.0-149.149, 7.0.0-43.43 and 7.3.0-10.10) while 20.04, 18.04 and 16.04 are still in progress (Canonical, 2026-11-10). Citrix has fixed its XenServer appliances (Citrix, 2026-11-03). XCP-ng released a kernel fix (XCP-ng, 2026-11-04), MikroTik's RouterOS 7.25.1 and 7.24.6 changelogs list the CVE (MikroTik, 2026-11-02; MikroTik, 2026-10-30), Sophos released Sophos Firewall hotfix HF110626.1 on 2026-11-06 and SD-RED firmware 3.0.012 on 2026-11-05 (Sophos, 2026-11-06), and Veeam's KB4966 says its Software and Infrastructure Appliances, workers, helper appliances and recovery media include an affected kernel, fixed through Veeam Updater or a private fix (Veeam, 2026-11-10). WatchGuard lists Fireware OS, AP and Dimension as potentially affected with no fix (WatchGuard, 2026-11-03); Fortinet names no fixed build but added an IPS virtual patch in FMWP database update 26.113 on 2026-11-07 (Fortinet, 2026-11-07).

Issue introduced in 4.4

Linux kernel CVE team (linux-cve-announce) 2026-10-15

allows a remote attacker to send packets to Linux servers with a multipath TCP listener to run arbitrary commands as root, without any credentials or user interaction

Anthropic Frontier Red Team 2026-10-27

While the demonstrated exploit requires the target system to expose an MPTCP listener, the underlying bug is not specific to MPTCP.

Go team (golang-announce) 2026-10-29

An unauthenticated network peer can start the flaw by sending TCP SYN packets that carry IPv4 options.

CIQ (Rocky Linux mitigation article) 2026-10-30

There are currently no confirmed reports of CVE-2026-98432 being exploited in the wild.

BleepingComputer 2026-10-30

Our kernel team couldn’t reproduce that claim.

CloudLinux (status post published 2026-10-30, updated 2026-11-02) 2026-11-02

Fortinet is currently investigating the impact of the CVE over Fortinet Products.

Fortinet PSIRT (FG-IR-26-188) 2026-11-02

Disabling MPTCP alone does not prevent exploitation; it only reduces the likelihood of triggering the race condition.

Akamai Security Intelligence Group 2026-11-02

An issue has been identified that may allow an unauthenticated attacker on the management network to compromise the host and/or any running Workload Balancing (WLB) or Conversion Manager appliances.

Citrix (security bulletin CTX697256) 2026-11-03

A public exploit exists. It relies on MPTCP, which the XCP-ng 8.3 kernel doesn't have, so this exploit doesn't work against XCP-ng.

XCP-ng (security update post) 2026-11-04

While Fireware OS and WatchGuard AP run vulnerable versions of the Linux kernel, they do not enable MPTCP and are not affected by the remote code execution (RCE) exploit chain circulating online.

WatchGuard PSIRT (WGSA-2026-0033) 2026-11-03

Veeam components that include a Linux kernel are affected.

Veeam
Updaterun 2026-11-01T1312Z-auditactionsbodycvessourcessourcing_notetitle

CIQ released patched kernels on 2026-10-31 for RLC Pro LTS 9.6 and FIPS 9.6 (kernel-5.14.0-570.60.1+27.2.el9_6_ciq), LTS 9.2 and FIPS 9.2 (kernel-5.14.0-284.30.1+45.1.el9_2_ciq) and LTS 8.6 (kernel-4.18.0-372.32.1+40.1.el8_6_ciq); RLC Pro LTS 8.10 and RLC Pro 10 are still waiting, and CIQ says the same fix was backported to the stable series 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56 and 7.2.10 (CIQ, 2026-10-31). Ubuntu's tracker, last updated 2026-10-30, still lists its kernels as vulnerable with fixes in progress (Canonical, 2026-10-30), and Red Hat's page now gives a preliminary CVSS 3.1 score of 9.8 (Red Hat, 2026-10-31).

Updaterun 2026-11-03T0256Z-inteltitleheadlinesummarycvessourcesevidencesourcing_noteactionsbody

Fortinet published advisory FG-IR-26-188 on 2026-11-02, saying it is investigating the impact on its products and listing FortiOS, FortiProxy, FortiManager, FortiAnalyzer, FortiWeb and FortiAuthenticator among them, with no fixed build or workaround named (Fortinet, 2026-11-02). CloudLinux's kernel team could not reproduce Anthropic's remote-root claim (CloudLinux, 2026-11-02). AWS says fixed Amazon Linux 2 and 2023 kernels are available, that Network Load Balancer TCP listeners pass client packets, including IP options, to targets, and that Linux targets behind them, Global Accelerator, PrivateLink and VPC Lattice layer 4 need the kernel update or the interim steps themselves, in the bulletin as published on 2026-11-02; its revision of 2026-11-04 says Global Accelerator endpoints are not affected and no longer carries the Network Load Balancer paragraph (AWS, 2026-11-02). Akamai reports a similar flaw when request-socket migration is enabled and lists the stable fixes 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56 and 7.2.10 (Akamai, 2026-11-02). CIQ's table lists patched kernels for RLC Pro 8, 9 and 10 and FIPS 8.6 and 8.10 released on 2026-11-01 (CIQ, 2026-11-01).

Updaterun 2026-11-05T0255Z-inteltitleheadlinesummaryentitiesaffected_productscvessourcesevidencesourcing_noteactionsbody

Citrix's bulletin CTX697256 of 2026-11-03, rated Critical, says an unauthenticated attacker on the management network may compromise a XenServer host and any running Workload Balancing or Conversion Manager appliance; it affects XenServer 8.4 and 9, Workload Balancing before 2026.1.1 and Conversion Manager before 2026.2.0, and Citrix has pushed updates to the Early Access and Normal channels of each XenServer line without naming a build and released Workload Balancing 2026.1.1 or later and Conversion Manager 2026.2.0 (Citrix, 2026-11-03). The bulletin states no exploitation.

Vates's advisory VSA-2026-056, published on 2026-11-03 and updated on 2026-11-04, rates the flaw critical for XCP-ng 8.3 and the Xen Orchestra Appliance, lists the fixed packages kernel-4.19.19-8.0.46.14.xcpng8.3 and, for the appliance, linux 6.1.190-1, requires a reboot, and gives an interim mitigation that drops inbound IP options, because without IP options the vulnerable code path cannot be reached (Vates, 2026-11-04). XCP-ng's post of 2026-11-04 says anyone who can send TCP traffic to the host, for example from its management network, VMs on it included, can attempt the attack, and tells hosts that cannot reboot at once to apply the iptables-based mitigation and not yet the update (XCP-ng, 2026-11-04). XCP-ng says a public exploit exists that relies on MPTCP, which the XCP-ng 8.3 kernel does not have, so it does not work against XCP-ng, while the underlying bug is present and other ways to exploit it cannot be ruled out (XCP-ng, 2026-11-04); Vates says the exploit does not affect XCP-ng and the bug is not specific to MPTCP (Vates, 2026-11-04).

WatchGuard's advisory WGSA-2026-0033 of 2026-11-03 lists Fireware OS, AP and Dimension as potentially affected with no fix, says Fireware OS and AP do not enable MPTCP and are not affected by the exploit chain circulating online, and says it will update the advisory when Ubuntu ships a fix for Dimension (WatchGuard, 2026-11-03). MikroTik's RouterOS 7.25.1 of 2026-11-02 and RouterOS 7.24.6 of 2026-10-30 list the CVE under "improve stability" (MikroTik, 2026-11-02; MikroTik, 2026-10-30). NCSC Switzerland's advisory 13120 of 2026-10-29 rates exploitation unknown with vendor patches available and names MPTCP listeners as the target of the known exploits (NCSC Switzerland, 2026-10-29). Fortinet's advisory is unchanged: still investigating, with no fixed build, and Known Exploited: No (Fortinet, 2026-11-02).

Updaterun 2026-11-08T1309Z-auditactionsbodycvesheadlinesourcessummarytitle

Ubuntu's tracker, updated on 2026-11-07, lists Ubuntu 26.10 as fixed in linux 7.3.0-10.10, while 26.04, 24.04, 22.04, 20.04, 18.04 and 16.04 remain vulnerable with work in progress (Canonical, 2026-11-07). Sophos released Sophos Firewall hotfix HF110626.1 on 2026-11-06 for v23.0 GA, v23.0 EAP1 and v22.0 MR3, which needs a firewall restart and downloads automatically where automatic hotfix installation is enabled, the default, and SD-RED 20 and SD-RED 60 firmware 3.0.012 on 2026-11-05 (Sophos, 2026-11-06). Fortinet added an IPS virtual patch, "Linux.Kernel.tcp_v4_syn_recv_sock.Use.After.Free.", in FMWP database update 26.113 on 2026-11-07; its advisory still names no fixed build (Fortinet, 2026-11-07).

Updaterun 2026-11-11T0256Z-intelentitiesaffected_productssourcesevidenceactionsbodytitleheadlinesummarycvessourcing_note

Veeam's impact statement KB4966, last modified on 2026-11-10, says that every Veeam component that includes a Linux kernel is affected until the kernel is updated: Veeam Software Appliance 13.1, Veeam Infrastructure Appliance 13.1 in any role (backup proxies, repositories including hardened repositories, gateways, mount servers, WAN accelerators and others), workers deployed by the hypervisor plug-ins, the Linux-based helper appliances of Veeam Backup & Replication 13.1 and 12.3, Veeam Recovery Media for the Agent for Linux created before the update, and the public-cloud plug-in appliances; Kasten for Kubernetes is not affected (Veeam, 2026-11-10). The fixed kernel, a CIQ build 5.14.0-570.60.1+27.2.el9_6_ciq, has been in the Veeam repository since 2026-11-02; Veeam Updater checks every 12 hours and, with the default configuration, installs mandatory updates on the nearest Sunday at 14:00 in the backup server's time zone, a restart may be required, Windows-based Backup & Replication servers need a private fix for their helper appliances, and virtual labs and helper appliances that stay deployed must be redeployed (Veeam, 2026-11-10).

Ubuntu's tracker, updated on 2026-11-10, now lists 26.04 LTS (linux 7.0.0-43.43), 24.04 LTS (6.8.0-149.149) and 22.04 LTS (5.15.0-203.213) as fixed alongside 26.10 for the generic linux package, with 20.04, 18.04 and 16.04 and some HWE, FIPS, NVIDIA, Azure and Raspberry Pi variant kernels still in progress (Canonical, 2026-11-10).

Updaterun 2026-11-15T1407Z-auditaffected_productscvessourcesactionsbody

Sophos's advisory, updated to version 5 on 2026-11-12, adds that SD-RED firmware 3.0.012 was released on 2026-11-10 as a manually installed patch for Sophos UTM, which requires UTM 9.724 or later, and that legacy RED models past end of life are affected but will not receive a fix (Sophos, 2026-11-06). Ubuntu's tracker, updated on 2026-11-14, now lists the HWE kernels for 20.04, 22.04 and 24.04, Azure for 22.04 to 26.04, NVIDIA for 22.04 to 26.04 and Raspberry Pi for 22.04 to 26.04 as fixed, while FIPS for 24.04 and 20.04, Azure 7.0 and Azure NVIDIA for 24.04, NVIDIA 6.8 for 22.04 and the generic kernels for 20.04 and older remain in progress (Canonical, 2026-11-10). Veeam's KB4966, last modified on 2026-11-13, adds the helper appliances embedded in Veeam Recovery Orchestrator 13.1, fixed by a private fix, and Recovery Media for Veeam Agent for Linux 6.3, and lists the delivery per component: Veeam Updater for the appliances, an automatic update on launch for workers, a private fix for the helper appliances of Windows-based Backup & Replication and Recovery Orchestrator, and new recovery media (Veeam, 2026-11-10). Debian's tracker lists 6.12.117-1 as the current trixie security build, after the first fixed 6.12.113-1 (Debian Security Tracker, 2026-11-03).

Builds on: Public root exploit for a Linux page-cache write past the Dirty Frag fix; AlmaLinux kernels…

vulnerability31 Oct 03:48Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • upgrade.mikrotik.com2 (9%)
  • access.redhat.com1 (5%)
  • advisories.ncsc.nl1 (5%)
  • akamai.com1 (5%)
  • anthropic.com1 (5%)
  • aws.amazon.com1 (5%)
  • bleepingcomputer.com1 (5%)
  • blog.cloudlinux.com1 (5%)
  • other13 (59%)
All cited sources (22)