Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

GHSA-33j8-j763-4fv5 — cxf-rt-rs-security-jose-j…

MEDIUM

GHSA-33j8-j763-4fv5 is a medium-severity (CVSS 6.5) CWE-347 vulnerability in org.apache.cxf:cxf-rt-rs-security-jose-jaxrs. A fix is available for org.apache.cxf:cxf-rt-rs-security-jose-jaxrs — see the affected versions and patch details below.

Apache CXF: WS JSON request filter trusts metadata from an unvalidated first signature entry

Also known asCVE-2026-50634
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-33j8-j763-4fv5.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-33j8-j763-4fv5 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕org.apache.cxf:cxf-rt-rs-security-jose-jaxrs☕org.apache.cxf:cxf-rt-rs-security-jose-jaxrs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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 or 3.6.12, which fix this issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:cxf-rt-rs-security-jose-jaxrs≥ 4.2.0&&< 4.2.24.2.2org.apache.cxf:cxf-rt-rs-security-jose-jaxrs:4.2.2
☕Mavenorg.apache.cxf:cxf-rt-rs-security-jose-jaxrsall versions4.1.7org.apache.cxf:cxf-rt-rs-security-jose-jaxrs:4.1.7

Affected Products

1 product · 2 configurations
Application
cxfapache
≥ 4.2.0 && < 4.2.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:cxf-rt-rs-security-jose-jaxrs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.cxf:cxf-rt-rs-security-jose-jaxrs to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33j8-j763-4fv5 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-33j8-j763-4fv5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-33j8-j763-4fv5: cxf-rt-rs-security-jose-j… | O3 Security