# CVE-2025-26401: Weak cryptography in HMI ViewJet C-more series

> A local authenticated attacker can obtain authentication information due to weak password encoding in JTEKT HMI ViewJet C-more series devices.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-2qpq-x4m7-gjf3

## What is CVE-2025-26401?

CVE-2025-26401 is a medium-severity vulnerability in JTEKT ELECTRONICS CORPORATION HMI ViewJet C-more series, published on 4 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Weak encoding for password vulnerability exists in HMI ViewJet C-more series. If this vulnerability is exploited, authentication information may be obtained by a local authenticated attacker.

Weakness: CWE-261 (Weak Encoding for Password)

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


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

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

## Is CVE-2025-26401 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26401 is a medium-severity vulnerability in JTEKT ELECTRONICS CORPORATION HMI ViewJet C-more series, published on 4 Apr 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-26401 in the wild and no public exploit code.

Affected product: JTEKT ELECTRONICS CORPORATION HMI ViewJet C-more series. 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-26401/ (Markdown: https://insights.sbomify.com/CVE-2025-26401/index.md)
```

## Sources

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

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