Advisory record · GHSA-jc7r-v6fg-2gpf

Apache CXF TLS hostname verification does not work correctly with com.sun.net.ssl.*

CVSS 8.1 HighEPSS 0.082 · 94th percentile

Published by the GitHub Advisory Database at 19 Oct 2018, 16:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.cxf:cxf-rt-transports-httpMaven>=3.2.0, <3.2.5 || <3.1.163.2.5, 3.1.16
org.apache.cxf:apache-cxfMaven>=3.2.0, <3.2.5 || <3.1.163.2.5, 3.1.16
Identifiers
GHSA-jc7r-v6fg-2gpf · CVE-2018-8039
Weakness (CWE)
CWE-755
Published
19 Oct 2018
Updated
29 May 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache CXF (org.apache.cxf:cxf-rt-transports-http and org.apache.cxf:apache-cxf) versions 3.2.0 before 3.2.5 and before 3.1.16 do not properly report TLS hostname verification failures when the com.sun.net.ssl implementation is enabled through the java.protocol.handler.pkgs system property. An attacker in a man-in-the-middle position can then intercept connections from a CXF client without the error being raised. Upgrade to version 3.2.5 or 3.1.16.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.0 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.082, the 94th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:11 UTC First seen by agentprime
  2. 31 Oct 2026, 15:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.