Apache Software Foundation Apache Cxf vulnerabilities
54 known vulnerabilities affecting apache_software_foundation/apache_cxf.
Total CVEs
54
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL16HIGH27MEDIUM11
Vulnerabilities
Page 2 of 3
CVE-2018-8039P3HIGHCVSS 8.1vprior to 3.1.16v3.2.x prior to 3.2.52018-07-02
CVE-2018-8039 [HIGH] CWE-755 CVE-2018-8039: It is possible to configure Apache CXF to use the com.sun.net.ssl implementation via 'System.setProp
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");'. When this system property is set, CXF uses some reflection to try to make the HostnameVerifier work with the old com.sun.net.ssl.HostnameVerifier interface. However, the defaul
nvd
CVE-2026-50633P3HIGHCVSS 8.1≥ 4.2.0, < 4.2.2≥ 4.0.0, < 4.1.7+1 more2026-06-12
CVE-2026-50633 [HIGH] CWE-20 CVE-2026-50633: A JNDI Injection vulnerability has been discovered in Apache CXF's JCA integration module, which can
A JNDI Injection vulnerability has been discovered in Apache CXF's JCA integration module, which can allow for code execution, if an attacker is able to manipulate the JCA deployment descriptor (ra.xml) or runtime activation parameters. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.
nvd
CVE-2021-30468P3HIGHCVSS 7.5≥ Apache CXF, < 3.4.42021-06-16
CVE-2021-30468 [HIGH] CWE-400 CVE-2021-30468: A vulnerability in the JsonMapObjectReaderWriter of Apache CXF allows an attacker to submit malforme
A vulnerability in the JsonMapObjectReaderWriter of Apache CXF allows an attacker to submit malformed JSON to a web service, which results in the thread getting stuck in an infinite loop, consuming CPU indefinitely. This issue affects Apache CXF versions prior to 3.4.4; Apache CXF versions prior to 3.3.11.
nvd
CVE-2026-50631P3HIGHCVSS 7.4≥ 4.2.0, < 4.2.2≥ 4.0.0, < 4.1.7+1 more2026-06-12
CVE-2026-50631 [HIGH] CWE-367 CVE-2026-50631: A race condition in AbstractOAuthDataProvider allows concurrent requests using the same Refresh Toke
A race condition in AbstractOAuthDataProvider allows concurrent requests using the same Refresh Token to bypass single-use semantics and generate multiple valid Access Tokens, when 'recycleRefreshTokens' is set to false. A leaked refresh token can be replayed concurrently by multiple attackers or threads. Users are recommended to upgrade to versions 4
nvd
CVE-2021-22696P3HIGHCVSS 7.5≥ unspecified, < 3.4.3≥ unspecified, < 3.3.102021-04-02
CVE-2021-22696 [HIGH] CWE-400 CVE-2021-22696: CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to que
CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a "request" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the "reques
nvd
CVE-2016-8739P3HIGHCVSS 7.5vprior to 3.0.12v3.1.x prior to 3.1.92017-08-10
CVE-2016-8739 [HIGH] CWE-611 CVE-2016-8739: The JAX-RS module in Apache CXF prior to 3.0.12 and 3.1.x prior to 3.1.9 provides a number of Atom J
The JAX-RS module in Apache CXF prior to 3.0.12 and 3.1.x prior to 3.1.9 provides a number of Atom JAX-RS MessageBodyReaders. These readers use Apache Abdera Parser which expands XML entities by default which represents a major XXE risk.
nvd
CVE-2026-68481P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.3≥ 4.0.0, < 4.1.8+1 more2026-08-06
CVE-2026-68481 [HIGH] CWE-672 CVE-2026-68481: In Apache CXF's DefaultEncryptingOAuthDataProvider, revoked access tokens still decrypt successfully
In Apache CXF's DefaultEncryptingOAuthDataProvider, revoked access tokens still decrypt successfully, and TokenIntrospectionService reports active:true. The same applies to refresh tokens. This violates the RFC stipulations that 'The authorization server MUST invalidate the token.' and 'introspection of a revoked token MUST return {"active":false}'. U
nvd
CVE-2026-65432P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.3≥ 4.0.0, < 4.1.8+1 more2026-08-06
CVE-2026-65432 [HIGH] CWE-611 CVE-2026-65432: Apache CXF reads a top-level WSDL through its hardened StaxUtils path, which disables XML DTDs and e
Apache CXF reads a top-level WSDL through its hardened StaxUtils path, which disables XML DTDs and external entities. However, any or referenced from that top-level WSDL is handed off to WSDL4J, which does not disable DOCTYPE declarations or external entities. As a result, the protections applied to the top-level document do not extend to imported doc
nvd
CVE-2026-78384P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-78384 [HIGH] CWE-409 CVE-2026-78384: CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with no output-size cap. A
CompressionUtils.inflate() decompressed attacker-controlled DEFLATE data with no output-size cap. A small (~KB) crafted payload could expand to gigabytes on the heap. Reachable via JWE decryption when zip=DEF (e.g. JoseSessionTokenProvider with RSA-OAEP key wrap) and via SAML redirect/POST binding token inflation — in both cases decompression happens b
nvd
CVE-2026-100227P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-100227 [HIGH] CWE-362 CVE-2026-100227: Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security m
Improper Verification of Cryptographic Signature vulnerability in Apache CXF's JAX-RS XML Security module. The JAX-RS XML Signature interceptors (XmlSigInHandler, XmlSigInInterceptor and the streaming XmlSecInInterceptor) did not ensure that the XML passed to the application was covered by the signature. An attacker with any document signed by a tru
nvd
CVE-2017-3156P3HIGHCVSS 7.5vprior to 3.0.13v3.1.x prior to 3.1.102017-08-10
CVE-2017-3156 [HIGH] CVE-2017-3156: The OAuth2 Hawk and JOSE MAC Validation code in Apache CXF prior to 3.0.13 and 3.1.x prior to 3.1.10
The OAuth2 Hawk and JOSE MAC Validation code in Apache CXF prior to 3.0.13 and 3.1.x prior to 3.1.10 is not using a constant time MAC signature comparison algorithm which may be exploited by sophisticated timing attacks.
nvd
CVE-2022-46363P3HIGHCVSS 7.5≥ 3.5, < 3.5.5≥ 3.4, < 3.4.102022-12-13
CVE-2022-46363 [HIGH] CWE-20 CVE-2022-46363: A vulnerability in Apache CXF before versions 3.5.5 and 3.4.10 allows an attacker to perform a remot
A vulnerability in Apache CXF before versions 3.5.5 and 3.4.10 allows an attacker to perform a remote directory listing or code exfiltration. The vulnerability only applies when the CXFServlet is configured with both the static-resources-list and redirect-query-check attributes. These attributes are not supposed to be used together, and so the vulnerab
nvd
CVE-2026-57819P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.3≥ 4.0.0, < 4.1.8+1 more2026-08-06
CVE-2026-57819 [HIGH] CWE-400 CVE-2026-57819: Apache CXF allows to set a limit on the number of form parameters in a JAX-RS message via the "maxFo
Apache CXF allows to set a limit on the number of form parameters in a JAX-RS message via the "maxFormParameterCount" configuration option. However, no default limit is set which may lead to denial of service attacks when processing requests with very large numbers of form parameters. Users are recommended to upgrade to versions 4.2.3 or 4.1.8 or 3.6.
nvd
CVE-2026-54225P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.3≥ 4.0.0, < 4.1.8+1 more2026-08-06
CVE-2026-54225 [HIGH] CWE-770 CVE-2026-54225: Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apa
Apache CXF allows to control the maximum attachment size via the "attachment-max-size". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to Apache CXF 4.2.3 or 4.1.8 or 3.6.12 which fixes this p
nvd
CVE-2026-107937P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-107937 [HIGH] CWE-770 CVE-2026-107937: In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the confi
In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured attachment-max-header-size (default 300 characters) and attachment-headers-max-count (default 500) limits. The size limit was applied only to each physical line, not to a header value built from continuation lines or to the combined values of a
nvd
CVE-2026-86463P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-86463 [HIGH] CWE-400 CVE-2026-86463: Apache CXF's FIQL query parser has a vulnerability in how it searches for operators in query express
Apache CXF's FIQL query parser has a vulnerability in how it searches for operators in query expressions. The search pattern can get stuck trying many combinations when it encounters a long string without an operator, causing the parser to consume excessive CPU time. An attacker can send a crafted query to make the server use up CPU resources, potenti
nvd
CVE-2026-97791P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-97791 [HIGH] CWE-362 CVE-2026-97791: In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate
In Apache CXF, STSTokenValidator checks whether a SAML assertion is signed by a trusted certificate before deciding to send it to the STS. That result was stored in one object shared by all requests, so one request could read another's result. A remote, unauthenticated attacker could send a forged assertion signed with an untrusted certificate while le
nvd
CVE-2017-5656P3HIGHCVSS 7.5v3.1.x before 3.1.11vversions before 3.0.132017-04-18
CVE-2017-5656 [HIGH] CWE-384 CVE-2017-5656: Apache CXF's STSClient before 3.1.11 and 3.0.13 uses a flawed way of caching tokens that are associa
Apache CXF's STSClient before 3.1.11 and 3.0.13 uses a flawed way of caching tokens that are associated with delegation tokens, which means that an attacker could craft a token which would return an identifer corresponding to a cached token for another user.
nvd
CVE-2026-108039P3HIGHCVSS 7.5≥ 4.2.0, < 4.2.4≥ 4.0.0, < 4.1.9+1 more2026-10-09
CVE-2026-108039 [HIGH] CWE-776 CVE-2026-108039: By default, StaxUtils placed no limit on the total number of elements or the total number of charact
By default, StaxUtils placed no limit on the total number of elements or the total number of characters in an XML document. A very large request could therefore use a lot of memory and CPU during parsing, especially where CXF builds a DOM from the input (for example SAAJ or WS-Security), and could cause a denial of service when no request size limit
nvd
CVE-2025-23184P3HIGHCVSS 7.5fixed in 3.5.10≥ 3.6.0, < 3.6.5+1 more2025-01-21
CVE-2025-23184 [HIGH] CWE-400 CVE-2025-23184: A potential denial of service vulnerability is present in versions of Apache CXF before 3.5.10, 3.6.
A potential denial of service vulnerability is present in versions of Apache CXF before 3.5.10, 3.6.5 and 4.0.6. In some edge cases, the CachedOutputStream instances may not be closed and, if backed by temporary files, may fill up the file system (it applies to servers and clients).
nvd