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

CVE-2019-12406 — cxf

MEDIUM

CVE-2019-12406 is a medium-severity (CVSS 6.5) CWE-770 vulnerability in org.apache.cxf:cxf. 4 public exploit references exist, so weaponization risk is real. A fix is available for org.apache.cxf:cxf — see the affected versions and patch details below.

Potential DOS attack due to unrestricted attachment count in messages

Also known asGHSA-58p8-9g59-q2hr
Published
Nov 6, 2019
Updated
Jul 8, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
4 known
Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2019-12406 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected
☕org.apache.cxf:cxf☕org.apache.cxf:cxf☕org.apache.cxf:apache-cxf☕org.apache.cxf:apache-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 before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property "attachment-max-count".

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.cxf:cxfall versions3.2.11org.apache.cxf:cxf:3.2.11
☕Mavenorg.apache.cxf:cxf≥ 3.3.0&&< 3.3.43.3.4org.apache.cxf:cxf:3.3.4
☕Mavenorg.apache.cxf:apache-cxfall versions3.2.11org.apache.cxf:apache-cxf:3.2.11
☕Mavenorg.apache.cxf:apache-cxf≥ 3.3.0&&< 3.3.43.3.4org.apache.cxf:apache-cxf:3.3.4
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:cxf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-12406 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2019-12406. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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
Red Hat Decision Manager 7cxf-coreRHSA-2020:3196
Red Hat Fuse 7.8.0cxf-coreRHSA-2020:5568
Red Hat Process Automation 7cxf-coreRHSA-2020:3197
Text-Only RHOARsee advisoryRHSA-2020:2067

Frequently Asked Questions

Apache CXF before 3.3.4 and 3.2.11 does not restrict the number of message attachments present in a given message. This leaves open the possibility of a denial of service type attack, where a malicious user crafts a message containing a very large number of message attachments. From the 3.3.4 and 3.2.11 releases, a default limit of 50 message attachments is enforced. This is configurable via the message property "attachment-max-count".
O3 Security · Impact-Aware SCA

Is CVE-2019-12406 in your dependencies?

O3 Security finds CVE-2019-12406 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2019-12406: cxf DoS (Medium 6.5) | O3 Security