Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Local Privilege Escalation in Fuji Electric Tellus pcid64 Driver (CVE‑2026‑8108) Risks Industrial Control Systems

A CVE‑2026‑8108 flaw in Fuji Electric’s Tellus pcid64 driver lets a low‑privileged attacker execute code as SYSTEM. The vulnerability scores 7.8 on CVSS, making it a high‑impact risk for OT environments and a control gap for SOC 2 auditors.

Verisq™ Intelligence · 📅 July 16, 2026 · 📰 zerodayinitiative.com
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
zerodayinitiative.com

Local Privilege Escalation in Fuji Electric Tellus pcid64 Driver (CVE‑2026‑8108) Threatens Industrial Control Systems

What It Is — A vulnerability in the pcid64 driver of Fuji Electric’s Tellus platform allows a local attacker who can run low‑privileged code to execute arbitrary code as SYSTEM. The flaw stems from exposed dangerous methods that can be invoked to elevate privileges.

Exploitability — CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit code is known, but the low attack complexity and high impact make it a prime target for threat actors with limited foothold on an OT host.

Affected Products — Fuji Electric Tellus (industrial control system) – all versions prior to the vendor‑released patch.

Why It Matters for Compliance & Audit Readiness

  • SOC 2 CC6.1 – System Operations requires documented evidence that privileged‑access mechanisms are protected; a privilege‑escalation flaw indicates a control gap.
  • Continuous control monitoring must capture patch‑management status for OT assets; missing patches become audit findings.
  • Demonstrating timely remediation and evidence of remediation actions strengthens the Trust Center proof you can present to customers and auditors.

Recommended Actions

  1. Deploy Fuji Electric’s security update immediately on all Tellus installations.
  2. Map the vulnerability to the SOC 2 CC6.1 control and record remediation evidence in your continuous‑compliance platform.
  3. Enable automated patch‑status monitoring for OT devices to provide real‑time audit evidence.
  4. Review and tighten local execution policies to limit the ability of low‑privileged code to invoke driver methods.

Source: Zero Day Initiative advisory ZDI‑26‑439 (CVE‑2026‑8108)

📰 Original Source
http://www.zerodayinitiative.com/advisories/ZDI-26-439/ ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →