LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24733: Apache Tomcat: Security constraint bypass with HTTP/0.9

Improper Input Validation vulnerability in Apache Tomcat. Tomcat did not limit HTTP/0.9 requests to the GET method. If a security constraint was configured to allow HEAD requests to a URI but deny GET requests, the user could bypass that constraint on GET requests by sending a (specification invalid) HEAD request using HTTP/0.9. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.14, from 10.1.0-M1 through 10.1.49, from 9.0.0.M1 through 9.0.112. Older, EOL versions are also affected. Users are recommended to upgrade to version 11.0.15 or later, 10.1.50 or later or 9.0.113 or later, which fixes the issue.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24733 is an Apache Tomcat flaw where unusual HTTP/0.9 handling could bypass a specific access rule. It matters if an application allowed HEAD requests to a URI while denying GET requests. Apache rates it medium and provides fixed Tomcat versions.

Executive priority

Treat as a moderate-priority patching item. Prioritize internet-facing Tomcat systems and applications using method-specific access controls. The business risk is unauthorized access to protected resources in narrow configurations, not broad server takeover based on current public information.

Technical view

Tomcat did not restrict HTTP/0.9 requests to GET. A specification-invalid HEAD request using HTTP/0.9 could be treated in a way that bypassed security constraints configured to allow HEAD but deny GET for the same URI. Affected branches are 11.0.0-M1 through 11.0.14, 10.1.0-M1 through 10.1.49, and 9.0.0.M1 through 9.0.112.

Likely exposure

Exposure is likely limited to Tomcat deployments on affected versions with security constraints that allow HEAD but deny GET for a URI. Internet-facing Tomcat services with such configurations deserve prompt review. Older end-of-life Tomcat versions are also reported affected.

Exploitation context

The source bundle does not report active exploitation, and this CVE is not marked in KEV. The attack is network-reachable, unauthenticated, and low complexity per CVSS, but depends on a specific Tomcat constraint configuration involving HEAD and GET handling.

Researcher notes

This is CWE-20 improper input validation involving HTTP/0.9 method handling and Tomcat security constraints. The key condition is an allowed HEAD method with denied GET on a URI. No exploit code or exploitation-in-the-wild evidence is included in the provided sources.

Mitigation direction

  • Upgrade Tomcat 11.x to 11.0.15 or later.
  • Upgrade Tomcat 10.1.x to 10.1.50 or later.
  • Upgrade Tomcat 9.0.x to 9.0.113 or later.
  • Review vendor guidance for older end-of-life Tomcat versions.
  • Audit security constraints that allow HEAD while denying GET.

Validation and detection

  • Inventory all Apache Tomcat versions in production and staging.
  • Identify deployments running affected Tomcat version ranges.
  • Review web.xml and related security constraints for HEAD-allowed, GET-denied URI patterns.
  • Confirm upgraded instances report fixed Tomcat versions.
  • Check vendor advisory for any updated remediation details.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24733 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-24733Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Tomcat11.0.0-M1, 10.1.0-M1, 9.0.0.M1, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.