CVE Intelligence
Skip to main content
highPath Traversalpublic exploit

CVE-2026-104809

CVE-2026-104809 — Mitel MiVoice Office 400 Shared Object Hijacking Leading to Arbitrary Code Execution

DigitalCanion has discovered a vulnerability that allows an attacker to cause the system to load an attacker-controlled .so file instead of the expected legitimate module. The loading mechanism relies on a predictable module name without adequately verifying the file’s origin or integrity. A malicious shared object using the expected name can therefore be loaded by a privileged process. The module code then executes within the context and privileges of that process. This results in arbitrary code execution and full compromise of the Mitel Linux virtual machine.

Published Updated Sources: NVD, Mitel (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

Mitel

Mitel MiVoice Office 400

CVSS base

8.4

high

Remediation

The vendor's own words where we have them.

Upgrade Mitel MiVoice Office 400 to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
MitelMitel MiVoice Office 40011.0.96.0Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

X

Attack Complexity

Low

Attack Vector

Local

Privileges Req

High

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.4CVSS 4.0high——Mitel (CNA)

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/AU:Y/U:Amber

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-829 · Inclusion of Functionality from Untrusted Control Sphere

  • Execute Unauthorized Code or Commands

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

CWE-73 · External Control of File Name or Path

  • Read Files or Directories
  • Modify Files or Directories
  • Execute Unauthorized Code or Commands
  • DoS: Crash, Exit, or Restart

Mitigation: When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap provide this capability.

Weakness & attack patterns

  • CWE-73
  • CWE-494
  • CWE-829
  • CWE-426
  • CWE-427

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-13 · Subverting Environment Variable ValuesCAPEC-72 · URL EncodingCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-80 · Using UTF-8 Encoding to Bypass Validation LogicCAPEC-79 · Using Slashes in Alternate EncodingCAPEC-64 · Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-267 · Leverage Alternate EncodingCAPEC-78 · Using Escaped Slashes in Alternate Encoding
  • T1562.003Impair Defenses: Impair Command History Logging
  • T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026

  2. Added · CVSS 3.1 8.4 (AV:L)

    Oct 5, 2026 · NVD

  3. Initial · CVE published

    Oct 5, 2026 · NVD

  4. Added · GHSA-vr7j-w64f-pgvw published (high)

    Oct 5, 2026 · GitHub Security Advisory

  5. CVE published by MITRE.

    Oct 5, 2026 · SOCRadar CTI

References

3 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-104809 is Mitel MiVoice Office 400 Shared Object Hijacking Leading to Arbitrary Code Execution, a high vulnerability affecting Mitel MiVoice Office 400 from Mitel. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-104809. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.