CVE.org (no NVD analysis yet)· CNA apache

CVE-2026-107938: Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Apache Software Foundation Apache CXF 3.6.13, 4.1.9, 4.2.4.

Low priority for now. Upgrade to Apache Software Foundation Apache CXF 3.6.13, 4.1.9, 4.2.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In Apache CXF, the Netty-based HTTP client transport (cxf-rt-transports-http-netty-client) did not verify that the hostname in the server’s TLS certificate matched the host being called. This applied over both HTTP/1.1 and HTTP/2, even when disableCNCheck was left at its default value of false. The certificate chain was validated against the configured trust store, but the endpoint’s identity was not. A network attacker able to intercept traffic could present any certificate trusted by the client, such as a publicly issued certificate for a domain they control, and impersonate the target service. They could then read or modify the exchanged messages, including credentials. Users are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.

EUVD-2026-95703

Published: Oct 9, 2026
Updated: Oct 16, 2026
EPSS: 0.1% · 9th percentile
CWE: CWE-297

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 36 / 40 · 9.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Check your site's encryptionRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	cxf	cpe:2.3:a:apache:cxf

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache CXF
- 4.2.0 and later · before 4.2.4affected · semver
- 4.0.0 and later · before 4.1.9affected · semver
- before 3.6.13affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache cxfbefore 3.6.13
apache cxf4.0.0 and later · before 4.1.9
apache cxf4.2.0 and later · before 4.2.4

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2019-12419Apache 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.
43Plan
CVE-2010-2076Apache 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…
42Plan
CVE-2012-2379Apache CXF 2.4.x before 2.4.8, 2.5.x before 2.5.4, and 2.6.x before 2.6.1, when a Supporting Token specifies a child WS-SecurityPolicy 1.1…
41Plan

Published before and after this one in the same product

← EarlierCVE-2026-100227Oct 9, 2026 · Apache CXF: XML Signature wrapping in JAX-RS XML Security
30Monitor
← EarlierCVE-2026-107937Oct 9, 2026 · Apache CXF: The attachment header size and count limits can be bypassed, which allows denial of service through memory exhaustion.
30Monitor
Later →CVE-2026-108039Oct 9, 2026 · Apache CXF: Prevent unbounded XML document size in StaxUtils by adding default element and character limits
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache CXF	3.6.13	Vendor (CNA)
Apache Software Foundation Apache CXF	4.1.9	Vendor (CNA)
Apache Software Foundation Apache CXF	4.2.4	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.