dbcve.org
TomcatWeb server / proxy · Apache

CVE-2026-41284

HIGH · 7.5 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 9.0.118 / 10.1.55 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allocation of Resources Without Limits or Throttling vulnerability in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117. Older, unsupported versions may also be affected. Users are recommended to upgrade to version [FIXED_VERSION], which fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Apache Tomcat contains an Allocation of Resources Without Limits or Throttling vulnerability (CWE-770) that allows attackers to cause resource exhaustion or denial of service by exploiting insufficient limits on resource allocation within the affected Tomcat versions.

MitigationUpgrade Apache Tomcat to the fixed versions (11.0.22+, 10.1.55+, or 9.0.118+) to resolve the resource allocation vulnerability. For production systems that cannot immediately upgrade, implement request rate limiting at the load balancer or reverse proxy layer as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TomcatWeb server / proxy
Affected:>= 4.0.0, <= 7.0.109>= 8.5.0, <= 8.5.100>= 9.0.0, < 9.0.118>= 10.0.0, <= 10.0.27>= 10.1.0, < 10.1.55>= 11.0.0, < 11.0.22

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Apache Tomcat installation
    Check for Tomcat by looking for the 'catalina.sh' script (Linux/Unix) or 'catalina.bat' (Windows) in common paths such as /opt/tomcat, /usr/share/tomcat, C:\Tomcat, or search using 'find / -name catalina.sh 2>/dev/null' on Linux
    Affected if Tomcat is installed on the system
  2. Determine Tomcat version
    Run 'catalina.sh version' or check the 'RELEASE-NOTES' file in the Tomcat root directory, or look at the serverinfo.properties file in the lib folder
    Affected if The version displayed falls within any of these ranges: 4.0.0-7.0.109, 8.5.0-8.5.100, 9.0.0-9.0.117, 10.0.0-10.0.27, 10.1.0-10.1.54, or 11.0.0-11.0.21
  3. Check if Tomcat is exposed to untrusted network
    Inspect the server.xml configuration file (typically in conf/ directory) to determine if the HTTP connector is bound to a public or unresticted network interface (0.0.0.0 or wildcard) and accessible from untrusted networks
    Affected if The HTTP/AJP connector is exposed to untrusted networks without upstream rate limiting at a reverse proxy or load balancer

The system is affected if Apache Tomcat is installed, the version falls within any of the affected ranges (4.0.0-7.0.109, 8.5.0-8.5.100, 9.0.0-9.0.117, 10.0.0-10.0.27, 10.1.0-10.1.54, 11.0.0-11.0.21), and the service is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.118 / 10.1.55 / 11.0.22 or later
Fixed in 9.0.11810.1.5511.0.22
Interim mitigation

Upgrade Apache Tomcat to the fixed versions (11.0.22+, 10.1.55+, or 9.0.118+) to resolve the resource allocation vulnerability. For production systems that cannot immediately upgrade, implement request rate limiting at the load balancer or reverse proxy layer as a compensating control.

Recommended fix High confidence

Apache Tomcat 9.0.118 or later (9.0.x branch); 10.1.55 or later (10.1.x branch for Jakarta EE); 11.0.22 or later (11.0.x branch for Jakarta EE)

  1. 1. Identify the currently running Apache Tomcat version (check release notes or server info)
  2. 2. Determine the appropriate upgrade path based on your Jakarta EE or Java EE compatibility needs
  3. 3. Download the fixed version from the official Apache Tomcat distribution (tomcat.apache.org)
  4. 4. Backup your current Tomcat installation including conf/, webapps/, and any custom configurations
  5. 5. Stop the running Tomcat service
  6. 6. Install the new version to a clean directory or replace files carefully preserving custom configurations
  7. 7. Restore custom configuration files (server.xml, context.xml, etc.) from the backup
  8. 8. Deploy web applications to the new installation
Caveat Upgrading across major Tomcat branches (e.g., 9.0.x to 10.1.x) may require code changes due to namespace change from javax.* to jakarta.* for Jakarta EE 9+

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41284 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data