The host name verification missing in Apache Tomcat

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2018-8034: 21.05% estimated exploitation activity in the next 30 days; percentile 97.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The host name verification when using TLS with the WebSocket client was missing. It is now enabled by default. Versions Affected: Apache Tomcat 9.0.0.M1 to 9.0.9, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.35 to 7.0.88.

Published by the source

17 Oct 2018, 16:32 UTC

Last modified by the source

21 Oct 2024, 19:06 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-46j3-r4pj-4835

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-8034

Advisory: The host name verification missing in Apache Tomcat
IDs: CVE-2018-8034, GHSA-46j3-r4pj-4835
Record: https://patchnext.com/advisories/cve-2018-8034 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.tomcat.embed:tomcat-embed-core 9.0.10, 8.5.32, 8.0.53, 7.0.90. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat.embed:tomcat-embed-core: affected >= 9.0.0, <= 9.0.9; >= 8.5.0, < 8.5.32; >= 8.0.0, < 8.0.53; >= 7.0.35, <= 7.0.88; fixed in 8.5.32, 7.0.90, 8.0.53, 9.0.10

## Suggested inspection (read-only)
- Maven org.apache.tomcat.embed:tomcat-embed-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.tomcat.embed:tomcat-embed-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-46j3-r4pj-4835 (GitHub-reviewed advisory GHSA-46j3-r4pj-4835 lists affected ranges: Maven org.apache.tomcat.embed:tomcat-embed-core >=9.0.0 =8.5.0 =8.0.0 =7.0.35 <=7.0.88)

Commands are suggestions: review each one before running it.