Private key leak in Apache CXF

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2019-12423: 6.06% estimated exploitation activity in the next 30 days; percentile 93.39 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

22 May 2020, 19:23 UTC

Last modified by the source

1 Feb 2023, 05:03 UTC

Source last checked

26 Oct 2026, 16:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-42f2-f9vc-6365

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-12423

Advisory: Private key leak in Apache CXF
IDs: CVE-2019-12423, GHSA-42f2-f9vc-6365
Record: https://patchnext.com/advisories/cve-2019-12423 (revision 1, source checked 26 Oct 2026, 16:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.cxf:cxf 3.3.5, 3.2.12; org.apache.cxf:apache-cxf 3.3.5, 3.2.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.cxf:cxf: affected < 3.2.12; >= 3.3.0, < 3.3.5; fixed in 3.2.12, 3.3.5
- Maven org.apache.cxf:apache-cxf: affected < 3.2.12; >= 3.3.0, < 3.3.5; fixed in 3.2.12, 3.3.5

## Suggested inspection (read-only)
- Maven org.apache.cxf:cxf: check the installed version with your package manager.
- Maven org.apache.cxf:apache-cxf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.cxf:cxf, org.apache.cxf:apache-cxf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-42f2-f9vc-6365 (GitHub-reviewed advisory GHSA-42f2-f9vc-6365 lists affected ranges: Maven org.apache.cxf:apache-cxf >=0 =3.3.0 =0 =3.3.0 <3.3.5)

Commands are suggestions: review each one before running it.