Path TraversalWeakness · CWE-22

CVE-2025-59890

HIGH · 7.3 CVSS v3.1 Published 2025-11-27

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

75/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

Improper input sanitization in the file archives upload functionality of Eaton Galileo software allows traversing paths which could lead into an attacker with local access to execute unauthorized code or commands. This security issue has been fixed in the latest version of Galileo which is available on the Eaton download center.

Technical summary

dbcve analysis · high confidence

Eaton Galileo software contains a path traversal vulnerability in its file archive upload functionality. Insufficient input validation allows attackers with local access to manipulate archive extraction paths using directory traversal sequences (e.g., ../../), potentially writing files to arbitrary locations and achieving unauthorized code or command execution.

MitigationUpdate to the latest version of Galileo available from the Eaton download center. Additionally, implement strict input validation and path sanitization on all file archive upload handling to prevent directory traversal attacks.

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

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: High
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H

Am I affected?

dbcve checks

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

Identify if Eaton Galileo is installed

Search system for Eaton Galileo installation directories or check Programs and Features (Windows) or package manager listings (Linux) for Galileo software.

Affected if Eaton Galileo software is found on the system.
Determine the installed Galileo version

Locate the Galileo application binary or installation folder and query its version property, or run 'galileo -v' or similar version command if available.

Affected if The installed version matches the vulnerable version range for CVE-2025-59890.
Verify if file archive upload functionality exists

Examine Galileo configuration files, menus, or documentation to determine whether the file archive upload feature is present in this installation.

Affected if The file archive upload feature is available and accessible in the installed Galileo version.
Check for path traversal input validation

Inspect Galileo configuration or code files related to archive handling to see if path sanitization or input validation is implemented on the archive extraction process.

Affected if No path traversal validation is found in the archive upload/extraction handling code or configuration.
Review access controls on archive upload

Examine user permissions or access control settings to determine if local unprivileged users can access or trigger the archive upload functionality.

Affected if Local users with limited privileges can access or trigger the file archive upload feature.

A system is affected if it runs Eaton Galileo with the file archive upload feature enabled and the installed version lacks the path traversal fix for CVE-2025-59890.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update to the latest version of Galileo available from the Eaton download center. Additionally, implement strict input validation and path sanitization on all file archive upload handling to prevent directory traversal attacks.

Recommended fix Moderate confidence

latest version of Eaton Galileo (available on Eaton download center)

Navigate to the Eaton download center at www.eaton.com
Locate the Eaton Galileo software download page
Download the latest available version of Eaton Galileo
Install the latest version following standard installation procedures
Verify that the path traversal vulnerability is resolved by testing file upload functionality

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

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA3.0 h

19.0 hours of engineering $3,380

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-59890 — 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

Primary sources

www.eaton.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-59890?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.1%

Remediation

A high-priority fix

Have this fixed 19 hrs · Moderate

Typical engagement from $3,380

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-59890 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References