# CVE-2025-59890: Path traversal in Eaton Galileo Software

> Local attackers can exploit path traversal in file uploads to execute unauthorized code in Eaton Galileo software.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2025
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-3c2h-289j-mhp4

## What is CVE-2025-59890?

CVE-2025-59890 is a high-severity path traversal vulnerability in Eaton Galileo Software, published on 27 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-59890?


## How do I fix CVE-2025-59890?

No fix has been published for CVE-2025-59890 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59890 being exploited?

There is no known exploitation of CVE-2025-59890 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59890 and fix it if it is affected.

What it is: CVE-2025-59890 is a high-severity path traversal vulnerability in Eaton Galileo Software, published on 27 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59890 in the wild and no public exploit code.

Affected product: Eaton Galileo Software. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59890/ (Markdown: https://insights.sbomify.com/CVE-2025-59890/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59890
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59890
- OSV: https://osv.dev/vulnerability/CVE-2025-59890

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59890/
Summaries are generated and may contain mistakes; the official description above is the record.