VulnerabilityPublished 12 Jun 2026Updated 7 Aug 2026

CVE-2026-50634: Apache CXF · Improper Verification of Cryptographic Signature

Affects Apache CXFSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium · fixed in 4.2.2 : update Apache CXF when convenient.

Data as of 30 Oct 2026, 11:52 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 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.2.2, 4.1.7, 3.6.12

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache to 4.2.2, 4.1.7 or 3.6.12.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache CXF	Affected >=4.2.0 <4.2.2	Fixed in 4.2.2
Apache Software FoundationApache CXF	Affected >=4.0.0 <4.1.7	Fixed in 4.1.7
Apache Software FoundationApache CXF	Affected <3.6.12	Fixed in 3.6.12
MavenApache Software Foundation/org.apache.cxf:cxf-rt-rs-security-jose-jaxrs`pkg:maven/Apache Software Foundation/org.apache.cxf:cxf-rt-rs-security-jose-jaxrs`Other threats	Affected >=4.2.0 <4.2.2 >=4.0.0 <4.1.7 <3.6.12	Fixed in 4.2.2 4.1.7 3.6.12

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

AI-suggested

Users are advised to upgrade Apache CXF to versions 4.2.2, 4.1.7, or 3.6.12 where this vulnerability is fixed. Patch status is confirmed by the vendor advisory recommending these versions. No other mitigations or temporary fixes are indicated.

Description

CVE-2026-50634 is a medium severity vulnerability in Apache CXF affecting the JwsJsonContainerRequestFilter component. It allows processing of metadata that was not authenticated by the accepted cryptographic signature, potentially bypassing the application's trust assumptions about signed HTTP headers or content types. This could affect downstream entity parsing or signed-header consistency checks. Fixed versions include Apache CXF 4.2.2, 4.1.7, and 3.6.12.

Impact

An attacker can bypass signature verification checks on HTTP metadata, potentially causing the application to accept and process unauthenticated or tampered metadata. This could lead to partial loss of data integrity and trust in signed HTTP headers or content types, affecting downstream processing logic. There is no indication of confidentiality or availability impact. No known exploits in the wild have been reported.

Summary

This vulnerability (CWE-347) in Apache CXF's JwsJsonContainerRequestFilter permits an attacker to cause the system to process metadata without proper verification of the cryptographic signature. As a result, the application may incorrectly trust unsigned or tampered metadata such as Content-Type or protected HTTP headers. This undermines the integrity guarantees expected from signature verification and may lead to inconsistent or insecure processing of JAX-RS entities or signed headers. The issue is resolved in Apache CXF versions 4.2.2, 4.1.7, and 3.6.12.

CWE-347Improper Verification of Cryptographic Signature (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
Padding Oracle Crypto Attack (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Aug 2026, 16:24 UTC

WeaknessesCWE-347

Technical details

References

Community reviews

Related threats