# CVE-2025-7623: Supermicro BMC SMASH services has a Stack-based buffer overflow vulnerability

> An authenticated attacker with SSH access can exploit a stack buffer overflow in the SMASH-CLP shell to achieve arbitrary code execution on the BMC firmware.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 18 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-95mg-3279-c5xh

## What is CVE-2025-7623?

CVE-2025-7623 is a medium-severity memory corruption vulnerability in SMCI MBD-X13SEDW-F, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the SMASH-CLP shell. An authenticated attacker with SSH access to the BMC can exploit a stack buffer overflow via a crafted SMASH command, overwrite the return address and registers, and achieve arbitrary code execution on the BMC firmware operating system

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2025-7623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7623 is a medium-severity memory corruption vulnerability in SMCI MBD-X13SEDW-F, published on 18 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-7623 in the wild and no public exploit code.

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

## Sources

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

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