dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-8464

HIGH · 8.3 CVSS v4.0 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Golem OEE MES is vulnerable to an unauthenticated path traversal flaw. This vulnerability allows an attacker in the same local network to read arbitrary files from the server's operating system by manipulating HTTP request paths. This issue has been fixed in version 11.6.0

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Golem OEE MES contains an unauthenticated path traversal vulnerability that allows attackers on the same local network to manipulate HTTP request paths and read arbitrary files from the server's operating system. This is a classic directory traversal flaw where input validation on HTTP request paths is insufficient, enabling attackers to escape the web root directory.

MitigationUpgrade Golem OEE MES to version 11.6.0 or later. Additionally, network segmentation should be reviewed to limit exposure to only trusted devices on the local network, as the CVSS vector indicates a network-adjacent attack vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Golem OEE MES version
    Access the application admin interface and navigate to the About or System Information page. If unavailable, check the installation directory for version files or examine startup logs for version strings.
    Affected if The installed version is lower than 11.6.0
  2. Confirm web interface network exposure
    Review network configuration or firewall settings to determine if the MES web service is listening on network interfaces other than localhost/127.0.0.1. Check which IP addresses the web server is bound to.
    Affected if The web interface is bound to IP addresses accessible by other devices on the local network
  3. Inspect HTTP access logs for traversal attempts
    Locate and review the web server access logs for the MES application. Search for patterns containing '../' sequences or absolute file paths in request URLs.
    Affected if Logs contain requests with directory traversal patterns (such as ../../) targeting system files outside the web root

A system is affected if it runs Golem OEE MES version lower than 11.6.0 with the web interface exposed to the local network, allowing unauthenticated path traversal attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Golem OEE MES to version 11.6.0 or later. Additionally, network segmentation should be reviewed to limit exposure to only trusted devices on the local network, as the CVSS vector indicates a network-adjacent attack vector.

Recommended fix High confidence

11.6.0

  1. 1. Identify the current version of Golem OEE MES installation by checking the system configuration or product documentation.
  2. 2. Create a complete backup of the Golem OEE MES database, configuration files, and any custom settings.
  3. 3. Download Golem OEE MES version 11.6.0 from the official vendor or trusted distribution channel.
  4. 4. Follow the vendor's documented upgrade procedure to install version 11.6.0, ensuring all prerequisites are met.
  5. 5. After upgrading, verify that the path traversal vulnerability is resolved by attempting a controlled test of the affected HTTP endpoint (or have the vendor confirm remediation).
  6. 6. Restart the Golem OEE MES service and verify normal operation.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8464 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data