CVE-2026-100227
Apache CXF: XML Signature wrapping in JAX-RS XML Security
No exploitation reported by the sources we read.
- Published2026-10-09
- Fixed in4.2.4 · 4.1.9 · 3.6.13
- WeaknessCWE-362
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security module. The JAX-RS XML Signature interceptors (XmlSigInHandler, XmlSigInInterceptor and the streaming XmlSecInInterceptor) did not ensure that the XML passed to the application was covered by the signature. An attacker with any document signed by a trusted key could wrap it in unsigned content, which the application would then treat as signed. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.
Timeline
dates in UTC- 2026-10-0911:17CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-100227?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-100227?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.2 | ≥ 4.2.0, < 4.2.4 | 4.2.4 | NVD |
| 4.x | ≥ 4.0.0, < 4.1.9 | 4.1.9 | NVD |
| 3.6 | < 3.6.13 | 3.6.13 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Apache cxf to 4.2.4 · 4.1.9 · 3.6.13
Advisories and patches
- lists.apache.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2026-10-09
- Last Modified
- 2026-10-16
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-100227?
Is CVE-2026-100227 actively exploited?
What is the CVSS score for CVE-2026-100227?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
- CVE-2026-21589KEVsame week
- CVE-2026-93674same weekLangflow OSS is affected by multiple vulnerabilities
- CVE-2026-94579same week
- CVE-2026-105110same weekIskratel Innbox Unauthenticated Remote Code Execution via login.xgi CLI Parameter
- CVE-2026-87666same week
- CVE-2026-108576same weekTOZED X300 IPPingDiagnostics process_ping os command injection
- CVE-2026-84278same weekIBM Guardium Data Protection Command Injection
- CVE-2026-105484same weekTOTOLINK X6000R UploadFirmwareFile cstecgi.cgi firmware_check os command injection