Quick answers
- Is CVE-2026-100227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100227 being exploited in the wild.
- How severe is CVE-2026-100227?
- High severity, with a CVSS score of 7.5, published 9 October 2026.
- Which products and versions are affected?
- Apache CXF before 3.6.13, 4.1.9, 4.2.4.
- Is there a fix for CVE-2026-100227?
- Yes: fixed in CXF 3.6.13, 4.1.9, 4.2.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100227 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100227?
- Check whether you run Apache CXF at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: CXF 3.6.13, 4.1.9, 4.2.4
Technical details
The JAX-RS XML Signature interceptors (XmlSigInHandler, XmlSigInInterceptor, and XmlSecInInterceptor) fail to verify that all XML content processed by the application is covered by the signature. An attacker can take a document signed with a trusted key, wrap it in unsigned XML content, and the vulnerable interceptors will process the unsigned portions without detecting the tampering, treating the entire document as authenticated.
Affected products
- Apache CXF before 3.6.13, 4.1.9, 4.2.4
Timeline
- 2026-10-09: disclosed