Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2020-13943 — tomcat-coyote

MEDIUMFix: apache/tomcat@1bbc650

CVE-2020-13943 is a medium-severity (CVSS 4.3) vulnerability in org.apache.tomcat:tomcat-coyote. EPSS puts its 30-day exploitation probability at 57.3% (99th percentile). A fix is available for org.apache.tomcat:tomcat-coyote — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Also known asBIT-tomcat-2020-13943GHSA-f268-65qc-98vg
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
57.3%probability of exploitation in next 30 days
High Risk0.00%
Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk
56.8%57.1%57.5%57.8%57.3%57.3%Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-13943 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote☕org.apache.tomcat:tomcat-coyote

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.tomcat:tomcat-coyote≥ 10.0.0-M1&&< 10.0.0-M810.0.0-M8org.apache.tomcat:tomcat-coyote:10.0.0-M8
☕Mavenorg.apache.tomcat:tomcat-coyote≥ 9.0.0-M1&&< 9.0.389.0.38org.apache.tomcat:tomcat-coyote:9.0.38
☕Mavenorg.apache.tomcat:tomcat-coyote≥ 8.5.0&&< 8.5.588.5.58org.apache.tomcat:tomcat-coyote:8.5.58

Affected Products

4 products · 131 configurations
Application
tomcatapache
97 versions
8.5.08.5.18.5.28.5.38.5.48.5.58.5.68.5.78.5.88.5.98.5.108.5.11
OS
debian linuxdebian
2 versions
9.010.0
Application
instantis enterprisetrackoracle
3 versions
17.117.217.3
Application
sd-wan edgeoracle
1 version
9.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat-coyote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.apache.tomcat:tomcat-coyote to 10.0.0-M8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13943 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat Enterprise Linux 8's Identity Management is using an affected version of Tomcat bundled within PKI servlet engine, however HTTP/2 protocol is not supported by this component.

ProductFixed inAdvisory
Red Hat Fuse 7.10tomcatRHSA-2021:5134
Red Hat JBoss Web Server 5tomcatRHSA-2021:0495
Red Hat JBoss Web Server 5.4 on RHEL 7jws5-tomcat-0:9.0.36-9.redhat_8.1.el7jwsRHSA-2021:0494
Red Hat Support for Spring Boot 2.4.9tomcatRHSA-2021:4012
UbuntuMEDIUM

Frequently Asked Questions

If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
O3 Security · Impact-Aware SCA

Is CVE-2020-13943 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2020-13943: tomcat-coyote — Fixed in 10.0.0-M8