Quick answers
- Is CVE-2026-107938 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107938 being exploited in the wild.
- How severe is CVE-2026-107938?
- Critical severity, with a CVSS score of 9.1, published 9 October 2026.
- Which products and versions are affected?
- Apache CXF Below 3.6.13, 4.1.x before 4.1.9, 4.2.x before 4.2.4.
- Is there a fix for CVE-2026-107938?
- Yes: fixed in Apache 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-107938 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107938?
- 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: Apache CXF 3.6.13, 4.1.9, 4.2.4
Technical details
The cxf-rt-transports-http-netty-client component does not perform hostname verification on TLS certificates despite the disableCNCheck flag being set to false by default. While the certificate chain is validated against the configured trust store, endpoint identity verification is skipped. A network-positioned attacker can perform a man-in-the-middle attack using any certificate trusted by the client's trust store to intercept and modify SOAP/HTTP traffic.
Affected products
- Apache CXF Below 3.6.13, 4.1.x before 4.1.9, 4.2.x before 4.2.4
Timeline
- 2026-10-09: disclosed