CVE-2018-8039
A public proof of concept exists; no exploitation attested.
- Published2018-07-02
- Fixed in3.2.5 · 3.1.16
- WeaknessCWE-755
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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 not implement the method in this interface, and an exception is thrown. However, in Apache CXF prior to 3.2.5 and 3.1.16 the exception is caught in the reflection code and not properly propagated. What this means is that if you are using the com.sun.net.ssl stack with CXF, an error with TLS hostname verification will not be thrown, leaving a CXF client subject to man-in-the-middle attacks.
Timeline
dates in UTC- 2018-07-0213:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-8039?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-8039?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 3.2 | ≥ 3.2.0, < 3.2.5 | 3.2.5 | NVD · OSV |
| 3.1 | < 3.1.16 | 3.1.16 | NVD · OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.1 | = 7.1.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Apache cxf to 3.2.5 · 3.1.16
Advisories and patches
- cxf.apache.orgVendor Advisory
- github.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
Sources
- NVDCVSS 3.08.1read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- NVDweakness (CWE)CWE-755read 2026-10-23
- FIRST EPSSEPSS score8.5 %2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-07-02
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-8039?
Is CVE-2018-8039 actively exploited?
What is the CVSS score for CVE-2018-8039?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.