Skip to content
VulniPulse
Advisory severityCritical9.8Apache Software Foundation

Critical [CVE-2026-66909] Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place

This critical-severity Apache Software Foundation advisory covers CVE-2026-66909 affecting Apache CXF.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-66909 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Apache CXF's JMS transport deserializes the body of any inbound JMS ObjectMessage using native Java deserialization, with no type restrictions in place.

Any attacker able to place a message on the service's JMS destination can submit a malicious serialized object, leading to denial of service or, if a suitable gadget class is on the classpath, remote code execution. The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed.

Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

Affected versions
  • Apache CXF 4.2.0 before 4.2.3
  • Apache CXF 4.0.0 before 4.1.8
  • Apache CXF before 3.6.12

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 4.2.3
  • 4.1.8
  • 3.6.12

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • The fix disables ObjectMessage deserialization by default, with a configuration switch to re-enable it if needed.
  • Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.12, which fix this issue.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.