# CVE-2025-10205: Predictable Salt and Weak Hashing Algorithm

> Attackers can exploit predictable salts and weak hashing in ABB FLXEON to bypass authentication or compromise credentials.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** GHSA-pj22-7pjr-wrh3

## What is CVE-2025-10205?

CVE-2025-10205 is a high-severity vulnerability in ABB FLXEON, published on 17 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use of a One-Way Hash with a Predictable Salt vulnerability in ABB FLXEON.This issue affects FLXEON: through 9.3.5. and newer versions

Weakness: CWE-759 (Use of a One-Way Hash without a Salt)

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


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

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

## Is CVE-2025-10205 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10205 is a high-severity vulnerability in ABB FLXEON, published on 17 Sep 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-10205 in the wild and no public exploit code.

Affected product: ABB FLXEON. 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-10205/ (Markdown: https://insights.sbomify.com/CVE-2025-10205/index.md)
```

## Sources

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

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