Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-65905: 0.76% estimated exploitation activity in the next 30 days; percentile 55.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Authentication Bypass by Capture-replay vulnerability in Apache Tomcat's DIGEST authenticator. If, before windowSize requests have been made, a client makes a DIGEST authenticated request with a nonceCount on the upper boundary of the replay window then that request is replayable once only while the associated nonceCount remains within the replay window. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.30 through 7.0.109. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fix the issue.

Published by the source

26 Aug 2026, 00:30 UTC

Last modified by the source

11 Sep 2026, 08:25 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9xv2-5v5q-p794

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9xv2-5v5q-p794

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-65905

Advisory: Apache Tomcat's DIGEST authenticator has an Authentication Bypass by Capture-replay vulnerability
IDs: CVE-2026-65905, GHSA-9xv2-5v5q-p794
Record: https://patchnext.com/advisories/cve-2026-65905 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.apache.tomcat:tomcat-catalina 11.0.25, 10.1.58, 9.0.121; org.apache.tomcat.embed:tomcat-embed-core 11.0.25, 10.1.58, 9.0.121; org.apache.tomcat:tomcat 11.0.25, 10.1.58, 9.0.121. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.tomcat:tomcat-catalina: affected >= 11.0.0-M1, < 11.0.25; >= 10.1.0-M1, < 10.1.58; >= 9.0.0.M1, < 9.0.121; >= 8.5.0, <= 8.5.100; >= 7.0.30, <= 7.0.109; fixed in 11.0.25, 9.0.121, 10.1.58
- Maven org.apache.tomcat.embed:tomcat-embed-core: affected >= 11.0.0-M1, < 11.0.25; >= 10.1.0-M1, < 10.1.58; >= 9.0.0.M1, < 9.0.121; >= 8.5.0, <= 8.5.100; >= 7.0.30, <= 7.0.109; fixed in 11.0.25, 9.0.121, 10.1.58
- Maven org.apache.tomcat:tomcat: affected >= 11.0.0-M1, < 11.0.25; >= 10.1.0-M1, < 10.1.58; >= 9.0.0.M1, < 9.0.121; >= 8.5.0, <= 8.5.100; >= 7.0.30, <= 7.0.109; fixed in 11.0.25, 9.0.121, 10.1.58

## Suggested inspection (read-only)
- Maven org.apache.tomcat:tomcat-catalina: check the installed version with your package manager.
- Maven org.apache.tomcat.embed:tomcat-embed-core: check the installed version with your package manager.
- Maven org.apache.tomcat:tomcat: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.tomcat:tomcat-catalina, org.apache.tomcat.embed:tomcat-embed-core, org.apache.tomcat:tomcat.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9xv2-5v5q-p794 (OSV record GHSA-9xv2-5v5q-p794 lists affected ranges: Maven org.apache.tomcat:tomcat >=11.0.0-M1 =10.1.0-M1 =9.0.0.M1 =8.5.0 =7.0.30 =11.0.0-M1 =10.1.0-M1 =9.0.0.M1 =8.5.0 =7.0.30 =11.0.0-M1 =10.1.0-M1 <10.1.58 (fixed),…)
- Verified: https://github.com/advisories/GHSA-9xv2-5v5q-p794 (GitHub-reviewed advisory GHSA-9xv2-5v5q-p794 lists affected ranges: Maven org.apache.tomcat:tomcat >=11.0.0-M1 =10.1.0-M1 =9.0.0.M1 =8.5.0 =7.0.30 =11.0.0-M1 =10.1.0-M1 =9.0.0.M1 =8.5.0 =7.0.30 =11.0.0-M1 =10.1.0-M1 =9.0.0.M1 =8.5.0 =7.0.30 <=7.0.109)

Commands are suggestions: review each one before running it.