Cxf vulnerabilitiesRanked by how likely they are to be used.

Product215 versions
The short answer

Cxf is made by Apache. We track 42 published vulnerabilities listed under that exact name, across 215 versions. None of them is on the list of flaws known to be exploited today. Apache lists newer releases under their own names, such as Cxf Fediz, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Cxf listed under other names? Yes.

Apache also lists Cxf under more specific names, such as Cxf Fediz. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Cxf vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Cxf's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Cxf flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 41%

    By default, Apache CXF creates a /services page containing a listing of the available endpoint names and addresses.

    CVSS6.1Published12 Nov 2020
  2. 32%

    The streaming XML parser in Apache CXF 2.5.x before 2.5.10, 2.6.x before 2.6.7, and 2.7.x before 2.7.4 allows remote attackers to cause a denial of service (CPU and memory consumption) via crafted XML with a large...

    CVSS5.0Published19 Aug 2013
  3. 14%

    Apache CXF before 3.3.4 and 3.2.11 provides all of the components that are required to build a fully fledged OpenId Connect service.

    CVSS9.8Published6 Nov 2019
  4. 11%

    JAX-RS XML Security streaming clients in Apache CXF before 3.1.11 and 3.0.13 do not validate that the service response was signed or encrypted, which allows remote attackers to spoof servers.

    CVSS5.3Published18 Apr 2017
  5. 9.8%

    Apache CXF 2.0.x before 2.0.13, 2.1.x before 2.1.10, and 2.2.x before 2.2.9, as used in Apache ServiceMix, Apache Camel, Apache Chemistry, Apache jUDDI, Apache Geronimo, and other products, does not properly reject...

    CVSS9.8Published19 Aug 2010
  6. 9.2%

    Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does not properly enforce the SAML SubjectConfirmation method security...

    CVSS5.0Published30 Oct 2014
  7. 8.9%

    Apache CXF before 2.4.9, 2.5.x before 2.5.5, and 2.6.x before 2.6.2 allows remote attackers to execute unintended web-service operations by sending a header with a SOAP Action String that is inconsistent with the...

    CVSS4.3Published24 Sep 2012
  8. 8.5%

    It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProperty("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");'.

    CVSS8.1Published2 Jul 2018
  9. 8.2%

    The URIMappingInterceptor in Apache CXF before 2.5.8, 2.6.x before 2.6.5, and 2.7.x before 2.7.2, when using the WSS4JInInterceptor, bypasses WS-Security processing, which allows remote attackers to obtain access to...

    CVSS5.8Published12 Mar 2013
  10. 7.5%

    The HTTP transport module in Apache CXF prior to 3.0.12 and 3.1.x prior to 3.1.9 uses FormattedServiceListWriter to provide an HTML page which lists the names and absolute URL addresses of the available service endpoints.

    CVSS6.1Published10 Aug 2017
Precursor Intelligence

Running Cxf? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 42 published vulnerabilities listed under the name Cxf, across 215 versions.

None of Cxf's vulnerabilities is on the list of flaws known to be exploited today.

Apache also lists Cxf under more specific names, such as Cxf Fediz. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Cxf. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.