cve.bz

CVE-2026-18767 Insufficient IOCTL access control allows local access to I/O ports

8.5 highEPSS 0.1%

High (8.5) in beckhoff automation. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A local low privileged attacker or process can access I/O ports via TcRouter.sys because of exposed IOCTL function calls resulting in a full compromise of the affected devices.

Severity

CVSS 4.0

8.5 high
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-782 Exposed IOCTL with Insufficient Access Control
Published
Modified
Assigned by
CERTVDE (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-18767 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18767?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18767?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18767 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-18767

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-18767](https://cve.bz/cve/badge/CVE-2026-18767.svg)](https://cve.bz/cve/CVE-2026-18767)

HTML:

<a href="https://cve.bz/cve/CVE-2026-18767"><img src="https://cve.bz/cve/badge/CVE-2026-18767.svg" alt="CVE-2026-18767"></a>

Affected

  • beckhoff automation:tcrouter.sys for windows on x64 3.1.0.2364
  • beckhoff automation:tcrouter.sys for windows on x64 <3.1.0.2365
  • beckhoff automation:tcrouter.sys for windows on x86 3.1.0.2364
  • beckhoff automation:tcrouter.sys for windows on x86 <3.1.0.2365
  • beckhoff automation:twincat.xar.base.km 3.16.29
  • beckhoff automation:twincat.xar.base.km <3.18.1

Versions

From the CNA's record in the CVE List.

ProductAffected
Beckhoff Automation TcRouter.sys for Windows on x64 3.1.0.23643.1.0.2364
Beckhoff Automation TcRouter.sys for Windows on x64 <3.1.0.2365from 1.0.0 before 3.1.0.2365
Beckhoff Automation TcRouter.sys for Windows on x86 3.1.0.23643.1.0.2364
Beckhoff Automation TcRouter.sys for Windows on x86 <3.1.0.2365from 1.0.0 before 3.1.0.2365
Beckhoff Automation TwinCAT.XAR.Base.KM 3.16.293.16.29
Beckhoff Automation TwinCAT.XAR.Base.KM <3.18.1from 1.0.0 before 3.18.1

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON