# CVE-2025-2900: IBM Semeru Runtime denial of service

> A buffer overflow in the native AES/CBC encryption implementation allows attackers to cause a denial of service via application crash.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2025
- **Updated:** 28 Aug 2025
- **Also known as:** GHSA-6pp6-5h3q-mgg3

## What is CVE-2025-2900?

CVE-2025-2900 is a high-severity memory corruption vulnerability in IBM Semeru Runtime, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Semeru Runtime 8.0.302.0 through 8.0.442.0, 11.0.12.0 through 11.0.26.0, 17.0.0.0 through 17.0.14.0, and 21.0.0.0 through 12.0.6.0 is vulnerable to a denial of service caused by a buffer overflow and subsequent crash, due to a defect in its native AES/CBC encryption implementation.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Ibm Semeru Runtime.

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

Apply the vendor's patch.

## Is CVE-2025-2900 being exploited?

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

## Other vulnerabilities in IBM Semeru Runtime

- [CVE-2024-22361](https://insights.sbomify.com/CVE-2024-22361/): IBM Semeru Runtime information disclosure (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2900 is a high-severity memory corruption vulnerability in IBM Semeru Runtime, published on 14 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2900 in the wild and no public exploit code.

Affected product: IBM Semeru Runtime. 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-2900/ (Markdown: https://insights.sbomify.com/CVE-2025-2900/index.md)
```

## Sources

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

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