NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2019-12423 — apache-cxf

HIGH

CVE-2019-12423 is a high-severity (CVSS 7.5) CWE-522 vulnerability in org.apache.cxf:apache-cxf. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.cxf:apache-cxf — see the affected versions and patch details below.

Private key leak in Apache CXF

Also known asGHSA-42f2-f9vc-6365
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
4 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
6.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk
0.00%2.51%5.02%7.53%1.2%6.1%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
☕org.apache.cxf:apache-cxf☕org.apache.cxf:apache-cxf☕org.apache.cxf:cxf☕org.apache.cxf:cxf

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

Apache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter "rs.security.keystore.type" to "jwk". For this case all keys are returned in this file "as is", including all private key and secret key credentials. This is an obvious security risk if the user has configured the signature keystore file with private or secret key credentials. From CXF 3.3.5 and 3.2.12, it is mandatory to specify an alias corresponding to the id of the key in the JWK file, and only this key is returned. In addition, any private key information is omitted by default. "oct" keys, which contain secret keys, are not returned at all.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:apache-cxfall versions3.2.12org.apache.cxf:apache-cxf:3.2.12
☕Mavenorg.apache.cxf:apache-cxf≥ 3.3.0&&< 3.3.53.3.5org.apache.cxf:apache-cxf:3.3.5
☕Mavenorg.apache.cxf:cxfall versions3.2.12org.apache.cxf:cxf:3.2.12
☕Mavenorg.apache.cxf:cxf≥ 3.3.0&&< 3.3.53.3.5org.apache.cxf:cxf:3.3.5

Affected Products

8 products · 12 configurations
Application
cxfapache
≥ 3.3.0 && < 3.3.5
range
Application
commerce guided searchoracle
1 version
11.3.2
Application
communications diameter signaling routeroracle
≥ 8.0.0 && ≤ 8.2.2
range
Application
communications element manageroracle
≥ 8.2.0 && ≤ 8.2.2
range
Application
communications session report manageroracle
≥ 8.2.0 && ≤ 8.2.2
range
Application
communications session route manageroracle
3 versions
8.1.18.2.08.2.1
Exploits & PoCs
4

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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:apache-cxf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.cxf:apache-cxf to 3.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-12423 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
EAP-CD 19 Tech Previewcxf-coreRHSA-2020:2333
Red Hat Decision Manager 7cxf-coreRHSA-2020:3196
Red Hat Fuse 7.8.0cxf-coreRHSA-2020:5568
Red Hat JBoss EAP 7cxf-coreRHSA-2020:2515
Red Hat JBoss EAP 7.2cxf-coreRHSA-2020:2061
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el6eapRHSA-2020:2058
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el7eapRHSA-2020:2059
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8eap7-activemq-artemis-0:2.9.0-4.redhat_00010.1.el8eapRHSA-2020:2060

Frequently Asked Questions

Apache CXF ships with a OpenId Connect JWK Keys service, which allows a client to obtain the public keys in JWK format, which can then be used to verify the signature of tokens issued by the service. Typically, the service obtains the public key from a local keystore (JKS/PKCS12) by specifing the path of the keystore and the alias of the keystore entry. This case is not vulnerable. However it is also possible to obtain the keys from a JWK keystore file, by setting the configuration parameter "rs.security.keystore.type" to "jwk". For this case all keys are returned in this file "as is", includi
O3 Security · Impact-Aware SCA

Is CVE-2019-12423 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2019-12423: apache-cxf — Fixed in 3.2.12