maven package report

Is org.apache.cxf:cxf-rt-transports-http safe?

3 known vulnerabilities, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
8.5%

chance of exploitation in the next 30 days

xyz score
3.6

CyberXYZ composite, out of 10

fig. 01 — GHSA-jc7r-v6fg-2gpf, the advisory selected below

// advisories

GHSA-jc7r-v6fg-2gpf

HIGHCVE-2018-8039

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 default HostnameVerifier implementation in CXF does

Affected
>= 3.2.0, < 3.2.5, < 3.1.16
Fixed in
3.2.5
Weakness
CWE-755
Published
2018-10-19
Source
github

GHSANVDMITREreferencereferencereferencereferencereferencereferencereferencereferencereference

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.

Checked 2026-09-22 at 01:49 UTC. The most recent advisory here was published 2024-07-19. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is org.apache.cxf:cxf-rt-transports-http safe? maven package security report | CyberXYZ