Skip to main content
VulnerabilityPublished

CVE-2026-58080: Eclipse Milo · Missing Authorization

Affects Eclipse MiloSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 1.1.5 soon.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade Eclipse Milo to 1.1.5.

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse MiloAffected
  • >=1.0.0 <1.1.5
Fixed in
  • 1.1.5
Mavenorg.eclipse.milo/milopkg:maven/org.eclipse.milo/miloOther threatsAffected
  • =1.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, users should avoid relying on the OpcUaServerConfig.copy() method for constructing running configurations that enforce role permissions or implement additional access control measures to compensate for this issue.

Description

CVE-2026-58080 affects Eclipse Milo versions 1.0.0 through 1.1.4. The vulnerability arises because the OpcUaServerConfig.copy() method does not preserve a configured RoleMapper. This causes sessions to receive no role IDs, leading the default access controller to skip role-permission checks. As a result, anonymous clients can read role-permission metadata, invoke protected methods, or delete protected nodes where anonymous sessions are allowed.

References

Community reviews

Loading reviews…