Is org.apache.cxf:cxf-core 4.0 vulnerable?
Maven · 12 releases from 4.0.0 to 4.0.11 · latest org.apache.cxf:cxf-core is 4.2.4 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. org.apache.cxf:cxf-core 4.0.11, the last 4.0 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2026-49875, CVE-2026-50645. 2 more affect earlier 4.0.x releases. Upgrade to 4.1.7 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.cxf:cxf-core -DdepVersion=4.1.7 -DforceVersion=trueIs your project on an affected org.apache.cxf:cxf-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.apache.cxf:cxf-core 4.0.11
Apache cxf-core: No restriction on attachment headers per message
- Affected
- >=4.2.0 <4.2.2 · >=4.0.0 <4.1.7 · <3.6.12
- Fixed in
- 3.6.12, 4.1.7, 4.2.2
Apache CXF has Improper Restriction of XML External Entity Reference
- Affected
- >=4.2.0 <4.2.2 · >=4.0.0 <4.1.7 · <3.6.12
- Fixed in
- 3.6.12, 4.1.7, 4.2.2
Fixed within 4.0.x, affecting earlier releases
Apache CXF is vulnerable to DoS attacks as entire files are read into memory and logged
- Affected
- <3.5.11 · >=3.6.0 <3.6.6 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.1
- Fixed in
- 3.5.11, 3.6.6, 4.0.7, 4.1.1
Apache CXF: Denial of Service vulnerability with temporary files
- Affected
- <3.5.10 · >=3.6.0 <3.6.5 · >=4.0.0 <4.0.6
- Fixed in
- 3.5.10, 3.6.5, 4.0.6
Every org.apache.cxf:cxf-core 4.0.x release
Affected: 4.0.0 to 4.0.11. Latest org.apache.cxf:cxf-core: 4.2.4.
| Version | Known advisories |
|---|---|
| org.apache.cxf:cxf-core 4.0.11 | CVE-2026-50645, CVE-2026-49875 |
| org.apache.cxf:cxf-core 4.0.10 | CVE-2026-50645, CVE-2026-49875 |
| org.apache.cxf:cxf-core 4.0.9 | CVE-2026-50645, CVE-2026-49875 |
| org.apache.cxf:cxf-core 4.0.8 | CVE-2026-50645, CVE-2026-49875 |
| org.apache.cxf:cxf-core 4.0.7 | CVE-2026-50645, CVE-2026-49875 |
| org.apache.cxf:cxf-core 4.0.6 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795 |
| org.apache.cxf:cxf-core 4.0.5 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
| org.apache.cxf:cxf-core 4.0.4 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
| org.apache.cxf:cxf-core 4.0.3 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
| org.apache.cxf:cxf-core 4.0.2 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
| org.apache.cxf:cxf-core 4.0.1 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
| org.apache.cxf:cxf-core 4.0.0 | CVE-2026-50645, CVE-2026-49875, CVE-2025-48795, CVE-2025-23184 |
Which of your client projects are still on org.apache.cxf:cxf-core 4.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.cxf:cxf-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.cxf:cxf-core versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.