dbcve.org
TomcatWeb server / proxy · Apache

CVE-2026-50229

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to 9.0.119 / 10.1.56 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in the number guess example for Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119, which fix 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 · high confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in Apache Tomcat's bundled number guess example application. User-supplied input is not properly sanitized before being reflected in the web page, allowing injection of malicious HTML/JavaScript.

MitigationUpgrade to Apache Tomcat 11.0.23, 10.1.56, or 9.0.119 which contain the fix, or remove/disable the number guess example application if upgrading is not feasible.

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:<= 7.0.109>= 8.5.0, <= 8.5.100>= 9.0.0, < 9.0.119>= 10.1.0, < 10.1.56>= 11.0.0, < 11.0.23

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify installed Apache Tomcat version
    Run 'catalina.sh version' or check the version string in the server startup output, or inspect the JAR file at $CATALINA_HOME/lib/catalina.jar and look for the Implementation-Version attribute
    Affected if The version falls within <= 7.0.109; >= 8.5.0, <= 8.5.100; >= 9.0.0, < 9.0.119; >= 10.1.0, < 10.1.56; >= 11.0.0, < 11.0.23
  2. Locate the number guess example application
    Check if the 'examples' webapp is deployed by examining the $CATALINA_HOME/webapps directory for an 'examples' folder, or look for 'numguess.jsp' and 'numguess.jspx' files within the webapp
    Affected if The examples webapp directory exists and contains the numguess example files
  3. Verify the examples webapp is accessible
    Attempt to access the URL 'http://<server>:<port>/examples/numguess.jsp' or check the webapp configuration in conf/server.xml to see if the examples context is enabled
    Affected if The examples webapp is deployed and accessible via HTTP/HTTPS on a listening port
  4. Confirm the vulnerable JSP file is present
    Within the examples webapp directory, locate the numguess.jsp file (typically in webapps/examples/jsp/numguess/ or similar path) and verify it exists
    Affected if The numguess.jsp file exists in the deployed examples webapp

You are affected if your Tomcat version is within the affected ranges AND the number guess example application (examples webapp containing numguess.jsp) is deployed and accessible on your server.

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.119 / 10.1.56 / 11.0.23 or later
Fixed in 9.0.11910.1.5611.0.23
Interim mitigation

Upgrade to Apache Tomcat 11.0.23, 10.1.56, or 9.0.119 which contain the fix, or remove/disable the number guess example application if upgrading is not feasible.

Recommended fix High confidence

9.0.119 for 9.x branches; 10.1.56 for 10.1.x branches; 11.0.23 for 11.x branches; 8.5.101+ for 8.5.x; 7.0.110+ for 7.0.x

  1. 1. Identify the current Apache Tomcat version by checking the $CATALINA_HOME/README RELEASE-NOTES or using the manager application.
  2. 2. Based on your current version line (7.0.x, 8.5.x, 9.0.x, 10.1.x, or 11.x), download the corresponding fixed release: 7.0.110+, 8.5.101+, 9.0.119, 10.1.56, or 11.0.23 from https://tomcat.apache.org/download-70.cgi or later.
  3. 3. Stop the Tomcat service: $CATALINA_HOME/bin/shutdown.sh (or .bat on Windows).
  4. 4. Back up the entire Tomcat installation directory, including conf/ and any deployed web applications.
  5. 5. Extract the new Tomcat version to a temporary location.
  6. 6. Copy the conf/ directory from the backup to the new installation, preserving custom configurations.
  7. 7. Redeploy web applications from the backup to the new installation if not using a shared appBase.
  8. 8. Start the Tomcat service: $CATALINA_HOME/bin/startup.sh (or .bat).
Caveat Minor: Ensure custom configurations in conf/server.xml, conf/context.xml are compatible with the new minor version; the number guess example may have been removed in newer versions and would need to be restored from source if required.

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

Fix this in Tomcat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50229 — 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-50229 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