Advisories
This weekExploitable · Confirmed

org.apache.tomcat:tomcat-coyote, org.apache.tomcat.embed:tomcat-embed-core: Apache Tomcat Denial of Service via invalid HTTP priority header

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

Does it affect what I run?

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • org.apache.tomcat:tomcat-coyote (Maven): from 9.0.76, before 9.0.104
  • org.apache.tomcat:tomcat-coyote (Maven): from 10.1.10, before 10.1.40
  • org.apache.tomcat:tomcat-coyote (Maven): from 11.0.0-M2, before 11.0.6
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): from 9.0.76, before 9.0.104
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): from 10.1.10, before 10.1.40
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): from 11.0.0-M2, before 11.0.6
  • org.apache.tomcat:tomcat-coyote (Maven): from 8.5.0, up to and including 8.5.100
  • org.apache.tomcat.embed:tomcat-embed-core (Maven): from 8.5.0, up to and including 8.5.100

The fix

  • org.apache.tomcat:tomcat-coyote (Maven) fixed in 9.0.104

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=9.0.104 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat:tomcat-coyote
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat:tomcat-coyote to 9.0.104 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.apache.tomcat:tomcat-coyote (Maven) fixed in 10.1.40

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=10.1.40 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat:tomcat-coyote
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat:tomcat-coyote to 10.1.40 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.apache.tomcat:tomcat-coyote (Maven) fixed in 11.0.6

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat:tomcat-coyote -DdepVersion=11.0.6 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat:tomcat-coyote
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat:tomcat-coyote to 11.0.6 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.apache.tomcat.embed:tomcat-embed-core (Maven) fixed in 9.0.104

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=9.0.104 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat.embed:tomcat-embed-core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat.embed:tomcat-embed-core to 9.0.104 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.apache.tomcat.embed:tomcat-embed-core (Maven) fixed in 10.1.40

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=10.1.40 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat.embed:tomcat-embed-core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat.embed:tomcat-embed-core to 10.1.40 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
  • org.apache.tomcat.embed:tomcat-embed-core (Maven) fixed in 11.0.6

    maven
    mvn versions:use-dep-version -Dincludes=org.apache.tomcat.embed:tomcat-embed-core -DdepVersion=11.0.6 -DforceVersion=true
    Check what is installed
    mvn dependency:tree -Dincludes=org.apache.tomcat.embed:tomcat-embed-core
    Paste into Cursor, Lovable or Claude Code
    Upgrade the Maven dependency org.apache.tomcat.embed:tomcat-embed-core to 11.0.6 or the nearest later release, to fix CVE-2025-31650. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

  • Exploitable · Confirmed

    EPSS puts the chance of exploitation in the next 30 days at 61%.

    FIRST EPSSStated

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)