# CVE-2025-6198: Supermicro BMC firmware update validation bypass

> An attacker can bypass firmware validation to install malicious firmware on Supermicro BMCs, leading to full system compromise.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-rffh-wmq4-5xwm

## What is CVE-2025-6198?

CVE-2025-6198 is a high-severity vulnerability in SMCI X13SEM-F, published on 19 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

There is a vulnerability in the Supermicro BMC firmware validation logic at Supermicro MBD-X13SEM-F . An attacker can update the system firmware with a specially crafted image.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2025-6198 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6198 is a high-severity vulnerability in SMCI X13SEM-F, published on 19 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6198 in the wild and no public exploit code.

Affected product: SMCI X13SEM-F. 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-6198/ (Markdown: https://insights.sbomify.com/CVE-2025-6198/index.md)
```

## Sources

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

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