On this page (8 sections)

On November 13, 2026, the Debian security team published advisory DSA-6623-1 for the tomcat10 package. It bundles fixes for 19 CVE identifiers in Tomcat, the servlet and JSP engine. Debian describes the possible outcomes as information disclosure, HTTP request smuggling or denial of service.

Anyone running Java web applications on Debian 13 (trixie) with the distribution's own tomcat10 package should plan this update. Only one source covers the story so far, the Debian security announcement, so this article stays within what that notice says.

At a glance

What Debian announced

The notice is brief. It names 19 CVEs, summarizes their combined effect, and says that on trixie the fix ships in tomcat10 10.1.60-1~deb13u1. Debian's recommendation is to upgrade the tomcat10 packages.

It does not tie each CVE to a particular impact, does not give severity ratings and does not say whether anyone is exploiting these flaws. Those gaps are real, and we are not filling them with guesses. The Debian security tracker page for tomcat10, which the advisory links to, is the place to look for per-CVE status.

What the three impact types mean for a site

Debian groups the flaws by outcome, so here is what each outcome means in practice.

  • Information disclosure: the server may hand data to someone who should not see it, such as request contents, files or internal details.
  • HTTP request smuggling: a front-end component (reverse proxy, load balancer or WAF) and Tomcat disagree about where one request ends and the next begins. That mismatch can let crafted requests slip past front-end controls or interfere with other users' traffic. It matters most when a proxy sits in front of Tomcat.
  • Denial of service: crafted traffic makes the service slow, resource-hungry or unresponsive.

Which of these affects you depends on the individual CVEs and your setup, which the advisory does not break down.

Who is affected

The advisory covers the stable release, trixie, and the tomcat10 package. You are most likely in scope if:

  • You installed Tomcat from Debian's tomcat10 package on trixie instead of unpacking a download from the Apache project.
  • Tomcat is reachable from the internet, or sits behind a proxy or load balancer that forwards traffic to it.
  • You host customer applications or internal tools on Tomcat that handle sensitive data.

The notice does not mention other Debian releases, container images or Tomcat installed outside the package system. If that describes your setup, rely on the advisories of the relevant vendor or project rather than assuming this one applies.

How to check your version

This command prints the installed tomcat10 package version on Debian. You want 10.1.60-1~deb13u1 or newer.

Show the installed tomcat10 version (Debian)Shell
dpkg -l tomcat10 | grep tomcat10

This one lists the installed version next to the version your configured repositories offer, so you can see whether the fixed build is waiting for you.

Compare installed and candidate versions (Debian)Shell
apt-cache policy tomcat10

If you are on trixie and the installed version is lower than 10.1.60-1~deb13u1, the update is still outstanding.

What to do now

Caution. Upgrading Tomcat restarts the service, which interrupts running applications and active sessions. Schedule it for a maintenance window and test your applications afterwards.
  1. Find every server running the Debian tomcat10 package with the version check above.
  2. Refresh package lists and upgrade tomcat10 to 10.1.60-1~deb13u1 or newer.
  3. Restart Tomcat if the upgrade did not do it, then confirm your applications start and respond normally.
  4. Re-run the version check to confirm the fixed build is installed.
  5. Review how Tomcat is exposed and, where possible, limit access to a reverse proxy or internal network.
  6. Skim access and error logs from before the update for odd requests, error spikes or resource exhaustion.

The next commands update only the tomcat10 package using standard apt. Run them as root or with sudo, and look for the new version in the output.

Update tomcat10 to the fixed version (Debian trixie)Shell
sudo apt update
sudo apt install --only-upgrade tomcat10

If you restart by hand, this restarts the service and shows its state. Expect it to report active (running).

Restart Tomcat and check its status (Debian, systemd)Shell
sudo systemctl restart tomcat10
systemctl status tomcat10
Tip. If you cannot patch right away, narrow who can reach the Tomcat port and keep any proxy in front of it up to date. This reduces risk but does not replace the update.

Detection and monitoring afterwards

The advisory lists no indicators of compromise, so there is no specific log signature to hunt for. General watchfulness still helps, especially if Tomcat was exposed before you patched:

  • Watch for unexplained restarts, memory or CPU spikes and sudden slowdowns, which can point to denial of service attempts.
  • Compare proxy and Tomcat logs for malformed or unusually shaped requests, or responses that do not line up with the requests received.
  • Follow the debian-security-announce list and the Debian security tracker for follow-up changes.

An outside view helps as well. Uptime monitoring tells you quickly when a Java application stops responding, and a website firewall in front of the application can filter odd traffic, though neither replaces patching the server. For more patching news, browse the Webforta security blog.

What we do not know yet

The Debian announcement is the only source so far. The research includes no CVSS scores, per-CVE descriptions, attacker activity or evidence of exploitation. Treat severity as unknown and exploitation as unconfirmed, and apply the update on an accelerated patch schedule instead of waiting for more detail.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6623-1] tomcat10 security updatelists.debian.org ·
  • Debian
  • Tomcat
  • DSA
  • HTTP request smuggling
  • patching