Unauthenticated code execution via EJB object deserialization
Published Apr 7, 2025 · Updated Aug 19, 2026
Deserialization in Red Hat WildFly and JBoss EAP remote EJB invocation allows remote attackers to execute code with a crafted object. The server passes attacker-supplied serialized data to JBoss Marshalling with an incomplete FilterSpecClassResolverFilter denylist, allowing gadget classes to trigger a JNDI lookup. An exposed remote EJB endpoint is required, and successful gadget-chain execution runs code in the application server's security context.
Summary
What happened
Deserialization in Red Hat WildFly and JBoss EAP remote EJB invocation allows remote attackers to execute code with a crafted object. The server passes attacker-supplied serialized data to JBoss Marshalling with an incomplete FilterSpecClassResolverFilter denylist, allowing gadget classes to trigger a JNDI lookup. An exposed remote EJB endpoint is required, and successful gadget-chain execution runs code in the application server's security context.
The record
- CVE
- CVE-2025-2251
- Published
- Apr 7, 2025
- Updated
- Aug 19, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat JBoss Enterprise Application Platform 8
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2025CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo