Skip to main content
VulnerabilityPublished Updated

CVE-2026-50634: Apache CXF · WS JSON request filter trusts metadata from an unvalidated first signature entry

Affects org.apache.cxf:cxf-rt-rs-security-jose-jaxrsSource GCVE Database

0
Authoritative record:CVE-2026-50634· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.2.2 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.2.2, 4.1.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade org.apache.cxf:cxf-rt-rs-security-jose-jaxrs to 4.2.2; org.apache.cxf:cxf-rt-rs-security-jose-jaxrs to 4.1.7.

Affected software

ProductAffectedFixed in
Mavenorg.apache.cxf:cxf-rt-rs-security-jose-jaxrsAffected
  • >=4.2.0 <4.2.2
Fixed in
  • 4.2.2
Mavenorg.apache.cxf:cxf-rt-rs-security-jose-jaxrsAffected
  • <4.1.7
Fixed in
  • 4.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A vulnerability in Apache CXF's JwsJsonContainerRequestFilter can be exploited to cause CXF to process metadata that was not authenticated by the accepted signature. This can bypass the application's assumption that accepted `Content-Type` or protected HTTP-header metadata came from a verified signature entry, and may steer downstream JAX-RS entity parsing or signed-header consistency checks. Users are recommended to upgrade to versions 4.2.2 or 4.1.7, which fix this issue.

References

Community reviews

Loading reviews…