Skip to main content
← CVEs

Insufficient IOCTL access control allows local relocation of arbitrary physical memory

Affects TcRouter.sys for Windows on x64 and x86 before 3.1.0.2365, and TwinCAT.XAR.Base.KM before 3.18.1. Fixed in TcRouter.sys 3.1.0.2365 and TwinCAT.XAR.Base.KM 3.18.1.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in TcRouter.sys for Windows on x64 <3.1.0.2365 3.1.0.2365 · TcRouter.sys for Windows on x86 <3.1.0.2365 3.1.0.2365 · TwinCAT.XAR.Base.KM <3.18.1 3.18.1
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Beckhoff TcRouter.sys for Windows on x64 or x86 at version 3.1.0.2364 or earlier than 3.1.0.2365, or TwinCAT.XAR.Base.KM 3.16.29 or earlier than 3.18.1

Published
Last modified
Reference
Last checked
14/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

The vulnerability affects TcRouter.sys for Windows (x86 and x64) and TwinCAT.XAR.Base.KM from Beckhoff Automation, in the versions listed. A local attacker with low privileges can use exposed IOCTL function calls in TcRouter.sys to move arbitrary physical memory contents, which can lead to full compromise of the affected devices.

Read the original description

A local low privileged attacker can move arbitrary physical memory content via TcRouter.sys because of exposed IOCTL function calls resulting in a full compromise of the affected devices.

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Beckhoff TcRouter.sys for Windows on x64 or x86 at version 3.1.0.2364 or earlier than 3.1.0.2365, or TwinCAT.XAR.Base.KM 3.16.29 or earlier than 3.18.1
  • Upgrade to a fixed version: TcRouter.sys for Windows on x64 <3.1.0.2365 3.1.0.2365 · TcRouter.sys for Windows on x86 <3.1.0.2365 3.1.0.2365 · TwinCAT.XAR.Base.KM <3.18.1 3.18.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-18769 (Insufficient IOCTL access control allows local relocation of arbitrary physical memory), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-18769 (entry last updated 2026-11-11):
Affected:
- Beckhoff Automation TcRouter.sys for Windows on x64 3.1.0.2364: versions 3.1.0.2364
- Beckhoff Automation TcRouter.sys for Windows on x64 <3.1.0.2365: from 1.0.0, fixed in 3.1.0.2365
- Beckhoff Automation TcRouter.sys for Windows on x86 3.1.0.2364: versions 3.1.0.2364
- Beckhoff Automation TcRouter.sys for Windows on x86 <3.1.0.2365: from 1.0.0, fixed in 3.1.0.2365
- Beckhoff Automation TwinCAT.XAR.Base.KM 3.16.29: versions 3.16.29
- Beckhoff Automation TwinCAT.XAR.Base.KM <3.18.1: from 1.0.0, fixed in 3.18.1
Fixed versions: 3.1.0.2365, 3.18.1.
Conditions (all must be true for the bug to be hit):
- Beckhoff TcRouter.sys for Windows on x64 or x86 at version 3.1.0.2364 or earlier than 3.1.0.2365, or TwinCAT.XAR.Base.KM 3.16.29 or earlier than 3.18.1 (source: https://certvde.com/en/advisories/VDE-2026-087/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-18769 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-18769 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.certvde.com/en/advisories/VDE-2026-087/
- https://certvde.com/en/advisories/VDE-2026-087/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-18769
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-18769.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Beckhoff Automation TcRouter.sys for Windows on x64 3.1.0.2364

    3.1.0.2364

  • Beckhoff Automation TcRouter.sys for Windows on x64 <3.1.0.2365

    From 1.0.0 · fixed in 3.1.0.2365

  • Beckhoff Automation TcRouter.sys for Windows on x86 3.1.0.2364

    3.1.0.2364

  • Beckhoff Automation TcRouter.sys for Windows on x86 <3.1.0.2365

    From 1.0.0 · fixed in 3.1.0.2365

  • Beckhoff Automation TwinCAT.XAR.Base.KM 3.16.29

    3.16.29

  • Beckhoff Automation TwinCAT.XAR.Base.KM <3.18.1

    From 1.0.0 · fixed in 3.18.1

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-18769

Is CVE-2026-18769 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An IOCTL interface in the Beckhoff driver lacks sufficient access control, which allows a local user to relocate arbitrary physical memory contents. The advisory describes the result as full compromise of the affected device.Source: certvde.com

Which versions are affected by CVE-2026-18769?

TcRouter.sys for Windows on x64 3.1.0.2364: version 3.1.0.2364. TcRouter.sys for Windows on x64 <3.1.0.2365: from 1.0.0 before 3.1.0.2365. TcRouter.sys for Windows on x86 3.1.0.2364: version 3.1.0.2364. TcRouter.sys for Windows on x86 <3.1.0.2365: from 1.0.0 before 3.1.0.2365. TwinCAT.XAR.Base.KM 3.16.29: version 3.16.29. 1 more package is listed on the page.Source: cve.now feed data

Am I affected, and how do I check?

Beckhoff TcRouter.sys for Windows on x64 or x86 at version 3.1.0.2364 or earlier than 3.1.0.2365, and TwinCAT.XAR.Base.KM at version 3.16.29 or earlier than 3.18.1. To check, look up the installed version of TcRouter.sys or TwinCAT.XAR.Base.KM and compare it with these ranges.Source: certvde.com

How do I fix CVE-2026-18769?

Upgrade TcRouter.sys to 3.1.0.2365 or later, and TwinCAT.XAR.Base.KM to 3.18.1 or later. The checked facts list no workaround.Source: certvde.com