External risk intelligence

Apache Tomcat RedirectValve Execution After Redirect Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-118028

Apache Tomcat is a widely used web server and servlet container frequently deployed as an internet-facing edge service to host web applications and APIs. Because the vulnerability exists within the request handling and redirection logic of the server itself, it is exposed by design to traffic originating from the public internet in standard deployment configurations.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Apache Tomcat's redirect functionality could allow unauthorized access and modification of data. This issue affects several versions of the widely used web server, which is often deployed facing the internet. The main concern is confirming relevance and exposure given its potential impact.

  • Redirects in Apache Tomcat are vulnerable.
  • Widely deployed internet-facing technology.
  • Confirm relevance and exposure impact.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by crafting a malicious request that takes advantage of how Apache Tomcat's RedirectValve handles specific redirection flags. This could allow an attacker to execute code or take control of certain aspects of the web server's operation.

  • Network access required.
  • Malicious redirect triggers vulnerability.
  • Leads to unauthorized code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in Apache Tomcat's RedirectValve could allow an attacker to redirect users to malicious websites when processing specific redirect flags. This could occur when a user interacts with a web application hosted on a vulnerable Tomcat server.

  • User navigation to malicious sites.
  • Malicious redirects via server configuration.
  • Deceptive user experiences.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Apache Tomcat RedirectValve EAR vulnerability likely impacts platform and infrastructure teams responsible for web server management, as well as application owners who rely on Tomcat for hosting. The first practical step is to inventory all Tomcat instances, identify externally reachable or business-critical deployments, and confirm the accountable team for each.

  • Platform/Infrastructure teams own remediation.
  • Verify all Tomcat instances and reachability.
  • Plan upgrades in maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Apache Tomcat and how is it used?

Apache Tomcat is an open-source web server and servlet container. Developers use it to host Java-based web applications and APIs, acting as the foundation that manages incoming web requests and executes server-side code to deliver content to users.

What does Execution After Redirect mean for CVE-2026-118028?

This vulnerability falls under the CWE-698 weakness class. It occurs when a server performs a redirect to a new location but continues to execute additional instructions or process requests after that redirect has been initiated, potentially leading to unauthorized operations.

How can an attacker trigger this vulnerability?

An attacker triggers the bug by sending a specifically crafted request to a vulnerable server that utilizes the RedirectValve component. The flaw is triggered by the interaction with specific redirection flags (F, G, or R); requests that do not involve these flags are not subject to this specific redirect logic error.

Why should I be concerned if my Tomcat server is internet-facing?

Halo Surface Signal notes that because this flaw exists in the core request handling logic, any Tomcat instance exposed to the public internet is inherently reachable. This design makes the server a primary target for external requests, increasing the risk of unauthorized activity compared to internal-only deployments.

What should I do first to address this vulnerability?

Begin by conducting an inventory of all Tomcat instances in your environment to identify which are running affected versions. Once mapped, prioritize those reachable from the internet for an upgrade to the patched versions provided by the vendor, ensuring you follow your standard maintenance procedures.

References