
查出 Spring Boot 内嵌 Tomcat 的真实版本(pom 里没有),并对每条 2026 年 CVE 同时给出 ASF 官方评级与 GitHub 评级、触发条件、以及这条会不会进 Dependabot 告警 CVE-2026-41293
Find out the actual Tomcat version you have installed, and for each 2026 CVE provide both rating systems and the trigger conditions at the same time.
Zero-dependency single jar, runs offline, no network access, uploads nothing.
一、Spring Boot 项目的内嵌 Tomcat 版本,你的 pom 里没有。
It is controlled by the tomcat.version property of spring-boot-starter-parent; in your pom you only see
spring-boot-starter-web. So this tool scans build artifacts (jar / fat jar / installation directory), and does not read the pom.
Two, some entries never make it into Dependabot alerts.
As of 2026-10-13, there are 51 CVEs from 2026 on the official Tomcat security page, of which 34 will not appear in alerts for Spring Boot projects due to the following two mechanisms (unreviewed 29 entries, coordinate mismatch 5 entries):
| 机制 | 说明 |
|---|---|
advisory 是 unreviewed | GitHub 只用 reviewed 的 advisory 做 Dependabot 告警。unreviewed 是 NVD 自动导入、尚未人工确认受影响包的正常流程状态 |
| 坐标对不上 | advisory 挂在 org.apache.tomcat:tomcat-coyote 等坐标下,而 Spring Boot 的依赖树里只有 tomcat-embed-core / -el / -websocket |
Actual results (run on 2026-10-13 with the real jar from Central): Spring Boot 3.5.16's bundled
tomcat-embed-core 10.1.55 + tomcat-embed-websocket 10.1.55, this tool reports 25 hits,
of which 22 do not make it into Dependabot alerts; with the default configuration, 1 is exposed, and the rest all come with preconditions, so please check the trigger conditions one by one.
These numbers will change: GitHub may convert
unreviewedentries toreviewedat any time. Regenerate the decision table (see below) to get the status as of that day.
Three, the two rating systems use different criteria, and you can only see one of them.
| ASF / Tomcat official | GitHub / NVD | |
|---|---|---|
| Grading | Low / Moderate / Important / Critical | CVSS numeric score |
| Basis | Actual exploitability under default configuration | Mechanically computed from the vector, regardless of whether you enabled that feature |
| Where to see it | tomcat.apache.org/security-9.html | Pushed directly to you by Dependabot |
Of the 51 entries, 23 have a rating difference of 2 levels or more between the two rating systems (another 9 have not yet been rated by GitHub and are not counted), with the most extreme being CVE-2026-41293: official Low, GitHub critical CVSS 9.8.
This is not a case of someone being wrong. The two systems are measuring different things to begin with. But to decide "should I upgrade right now", you need to see both — and whether you have that feature enabled.
java -jar tomcat-check.jar <jar 或目录> ...
--all 连「不适用」的条目也列出来
--utf8 Windows 控制台中文乱码时加这个
# Spring Boot fat jar
java -jar tomcat-check.jar target/my-app.jar
# 独立安装的 Tomcat
java -jar tomcat-check.jar /opt/tomcat
# 整个依赖目录
java -jar tomcat-check.jar target/lib
Requires Java 17+.
Each hit gives: two sets of ratings, the trigger conditions, the original official description, and whether this entry will show up in your Dependabot alerts. Finally, it gives a single upgrade target that covers all hit entries.
tomcat-embed-websocket is scanned. In the embedded form, the WebSocket implementation
is not in tomcat-embed-core; if your application excludes it, these entries will be listed under "not applicable" with the reason stated.unreviewed is a normal process state.Officially, a batch of 10 was fixed in 9.0.121 / 10.1.58 / 11.0.25, and another batch of 12 was fixed in 9.0.122 / 10.1.60 / 11.0.26. One of them deserves special mention:
CVE-2026-86350 (officially Important) is a regression introduced while fixing CVE-2026-41293. Its affected range is 9.0.118–9.0.121, 10.1.55–10.1.59, 11.0.22–11.0.25 — that is, the very releases that fixed 41293. Those who upgraded to these versions to fix 41293 need to upgrade once more. The trigger condition is that HTTP/2 is enabled.
Of these 22 entries across the two batches, 19 are still unreviewed on GitHub (as read on 2026-10-13).
tools/gen_rules.py generates CveTable.java from two primary sources, with not a single line copied by hand:
https://tomcat.apache.org/security-{9,10,11}.html — official ratings, titles, original descriptions, affected rangestype, affected Maven coordinatesThe generation process carries 7 assertions; if any one is not satisfied, it aborts and writes no file. Three of them deserve special mention:
<strong>Moderate: The fix for <a>CVE-2025-66614</a> was incomplete</strong> <a>CVE-2026-32990</a>.
Searching for "the first CVE" within the whole block picks up the old number embedded in the title; the consequence is not a missing entry but misattribution:
one CVE gets another's title and description, while generation, tests, and real-artifact re-verification all pass as usual.Affects: line sits right next to the title of the next CVE,
making it very easy to pair with the wrong entry — a mistake yields a table that "looks completely normal but is shifted by one row overall".
Cross-checking against GitHub's first_patched_version actually caught such a misalignment once during development.tomcat-embed-*.
The basis for exclusion must be empirical testing, not "I remember".To regenerate:
python tools/gen_rules.py
mvn clean package # → target/tomcat-check.jar
39 tests. Zero runtime dependencies; JUnit is test-only.
MIT
This tool answers "am I affected or not". The following it cannot answer, and you can reach out to me for: