GHSA-42f2-f9vc-6365
HIGHGHSA-42f2-f9vc-6365 is a high-severity (CVSS 7.5) CWE-522 vulnerability in org.apache.cxf:apache-cxf. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-42f2-f9vc-6365 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Private key leak in Apache CXF
Real-World Exposure
org.apache.cxf:apache-cxf☕org.apache.cxf:apache-cxf☕org.apache.cxf:cxf☕org.apache.cxf:cxfReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.cxf:apache-cxf | all versions | 3.2.12 |
| ☕Maven | org.apache.cxf:apache-cxf | ≥ 3.3.0&&< 3.3.5 | 3.3.5 |
| ☕Maven | org.apache.cxf:cxf | all versions | 3.2.12 |
| ☕Maven | org.apache.cxf:cxf | ≥ 3.3.0&&< 3.3.5 | 3.3.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Apache CXF ships with a OpenId Connect JWK Keys service, which allows a …
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.cxf:apache-cxf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-42f2-f9vc-6365 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-42f2-f9vc-6365 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-42f2-f9vc-6365. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-42f2-f9vc-6365 in your dependencies?
O3 detects GHSA-42f2-f9vc-6365 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.