# CVE-2025-65002: Auth bypass in iRMC

> Attackers can bypass authentication on Fujitsu iRMC S6 firmware by using a 16-character username, gaining unauthorized access to Redfish or WebUI interfaces.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-fwh6-gc6c-w62q

## What is CVE-2025-65002?

CVE-2025-65002 is a high-severity authentication bypass vulnerability in Fujitsu / Fsas Technologies iRMC, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fujitsu / Fsas Technologies iRMC S6 on M5 before 1.37S mishandles Redfish/WebUI access if the length of a username is exactly 16 characters.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-65002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65002 is a high-severity authentication bypass vulnerability in Fujitsu / Fsas Technologies iRMC, published on 12 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-65002 in the wild and no public exploit code.

Affected product: Fujitsu / Fsas Technologies iRMC. 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-65002/ (Markdown: https://insights.sbomify.com/CVE-2025-65002/index.md)
```

## Sources

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

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