# CVE-2025-2251: Org.jboss.eap:wildfly-ejb3: improper deserialization in jboss marshalling allows remote code execution

> Untrusted data deserialization in JBoss Marshalling allows remote attackers to execute arbitrary code without authentication.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/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:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-6839-6896-r9mx

## What is CVE-2025-2251?

CVE-2025-2251 is a medium-severity unsafe deserialization vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 7 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security flaw exists in WildFly and JBoss Enterprise Application Platform (EAP) within the Enterprise JavaBeans (EJB) remote invocation mechanism. This vulnerability stems from untrusted data deserialization handled by JBoss Marshalling. This flaw allows an attacker to send a specially crafted serialized object, leading to remote code execution without requiring authentication.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

Apply the vendor's patch.

## Is CVE-2025-2251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2251 is a medium-severity unsafe deserialization vulnerability in Red Hat JBoss Enterprise Application Platform 7, published on 7 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2251 in the wild and no public exploit code.

Affected product: Red Hat JBoss Enterprise Application Platform 7. 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-2251/ (Markdown: https://insights.sbomify.com/CVE-2025-2251/index.md)
```

## Sources

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

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