dbcve.org
TomcatWeb server / proxy · Apache

CVE-2025-55668

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 9.0.106 / 10.1.42 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Session Fixation vulnerability in Apache Tomcat via rewrite valve. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.7, from 10.1.0-M1 through 10.1.41, from 9.0.0.M1 through 9.0.105. Older, EOL versions may also be affected. Users are recommended to upgrade to version 11.0.8, 10.1.42 or 9.0.106, 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

Session Fixation vulnerability in Apache Tomcat's rewrite valve allows attackers to manipulate session IDs before user authentication, potentially enabling session hijacking after the user logs in.

MitigationUpgrade Apache Tomcat to version 11.0.8, 10.1.42, or 9.0.106 (or later) to obtain the security fix.

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:>= 9.0.1, < 9.0.106>= 10.0.0, < 10.1.42>= 11.0.0, < 11.0.8= 9.0.0

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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
    Locate the Tomcat installation directory and check the RELEASE-NOTES file or the version info in the bin/version.sh (Unix) or bin/version.bat (Windows) script. Alternatively, check the Server header in HTTP responses or the catalina.jar manifest file.
    Affected if The version is 9.0.0, 9.0.1-9.0.105, 10.0.0-10.1.41, or 11.0.0-11.0.7 (unpatched versions).
  2. Verify if rewrite valve is enabled
    Search for the rewrite valve configuration in the server.xml file (typically in the <Host> section) or in any context.xml file. Look for a line containing 'Valve className="org.apache.catalina.valves.rewrite.RewriteValve"'.
    Affected if The rewrite valve is explicitly configured and enabled in the Tomcat server configuration.
  3. Inspect rewrite rule configuration for session manipulation
    Check for a rewrite.config file (or the rewrite rule configuration within the context) in the conf/Catalina/localhost/ directory or the application's META-INF/context.xml. Look for rules that set or modify the JSESSIONID cookie or URL parameter.
    Affected if Rewrite rules exist that manipulate the JSESSIONID value (such as RewriteRule patterns that include or set session identifiers).
  4. Confirm application uses servlet-based session management
    Verify the web application uses Java servlet session tracking (HttpSession). This is the default in most Java web applications. Check if the application calls request.getSession() or similar session-related methods.
    Affected if The application relies on servlet session management, making it susceptible to session fixation if the rewrite valve manipulates session IDs.

You are affected if you run an unpatched Tomcat version (9.0.0-9.0.105, 10.0.0-10.1.41, or 11.0.0-11.0.7) AND have the rewrite valve enabled with rules that could manipulate session identifiers before authentication.

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.106 / 10.1.42 / 11.0.8 or later
Fixed in 9.0.10610.1.4211.0.8
Interim mitigation

Upgrade Apache Tomcat to version 11.0.8, 10.1.42, or 9.0.106 (or later) to obtain the security fix.

Recommended fix High confidence

9.0.106, 10.1.42, or 11.0.8 depending on your current major version branch

  1. Identify the currently running Tomcat version by checking the $CATALINA_HOME/README or using the version.sh script
  2. Stop the Tomcat service gracefully
  3. Backup the entire Tomcat installation directory including conf/ and webapps/
  4. Download the appropriate fixed version from the official Apache Tomcat download page (https://tomcat.apache.org/)
  5. Extract the new Tomcat version to a temporary location
  6. Copy custom configuration files from the backup conf/ directory to the new installation (server.xml, context.xml, etc.)
  7. Deploy any custom web applications from the backup webapps/ directory if needed
  8. Start the Tomcat service

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

Fix this in Tomcat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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