
CVE-2026-24880: does Apache's upgrade advice actually apply to your Tomcat? Detects the fix by class presence, not version comparison. Covers 7.0/8.0/8.5/9.0/10.0/10.1/11.0 lines.
CVE-2026-24880 · GHSA-563x-q5rq-57qp —— Does Apache's
upgrade to version 11.0.20, 10.1.52 or 9.0.116 actually apply to you?
For most people it doesn't, and there are four different ways it doesn't apply. This tool scans your artifacts and tells you which one it is.
java -jar tomcat-line-check.jar /path/to/tomcat # 解压部署的 Tomcat
java -jar tomcat-line-check.jar app.war # war
java -jar tomcat-line-check.jar app.jar # Spring Boot fat jar
java -jar tomcat-line-check.jar --table # 只看七条线的判定表
java -jar tomcat-line-check.jar --utf8 ... # Windows 控制台中文乱码时加
unzip -l tomcat-coyote-<ver>.jar | grep ChunkExtension
Has org/apache/tomcat/util/http/parser/ChunkExtension.class = fix included; absent = fix missing.
🔴 This tool does not compare version numbers to decide whether a fix is present — because the version-number claim itself is exactly where things go wrong on this CVE.
The verdict table is generated by tools/gen_table.py from first-hand sources; if any of the seven assertion groups fails, it refuses to produce the table.
| Line | Final version | EOL | Fix present | Exit |
|---|---|---|---|---|
| 7.0 | 7.0.109 | 2021-03-31 | None | ❌ 7.0.110 = 404 |
| 8.0 | 8.0.53 | 2018-06-30 | None | ❌ 8.0.54 = 404 |
| 8.5 | 8.5.100 | 2024-03-31 | None | ❌ 8.5.101 = 404 |
| 10.0 | 10.0.27 | 2022-10-31 | None | ❌ 10.0.28 = 404 |
| 9.0 | 9.0.121 | 2027-03-31 | 9.0.115 no | ✅ 9.0.116 |
| 10.1 | 10.1.59 | Not EOL | 10.1.52 no | ✅ 10.1.53 |
| 11.0 | 11.0.25 | Not EOL | 11.0.18 no | ✅ 11.0.20 |
① You are on the 8.5 / 7.0 / 8.0 line — none of the three versions the official advisory gives is on your line,
and your line has stopped shipping (8.5.101 / 7.0.110 / 8.0.54 are all 404 on Maven Central).
8.0 is even more special: the official advisory marks it as unknown, so it doesn't even answer "are you affected or not".
② You are on the 10.1 line — the official advisory tells you to upgrade to 10.1.52, and 10.1.52 itself lacks the fix.
The previous paragraph of the same advisory lists 10.1.0-M1 through 10.1.52 as affected.
Apache's own security-10.html
files this CVE under the 10.1.53 section; and compare 10.1.52...10.1.53 does contain the fix commit f07df938.
→ Upgrading as that sentence says is as good as not upgrading.
③ You are on the 10.0 line — 10.0. appears 0 times in the official advisory.
It is neither in the affected list nor in the two unknown entries; the two ranges in the GitHub advisory
(>= 7.0.0, < 9.0.116 and >= 10.1.0-M1, < 10.1.52) don't cover it either.
And the ChunkedInputFilter members of 10.0.27 are word-for-word identical to those of 7.0.109 / 8.5.100, while 10.0.28 is a 404.
→ No source has ever answered whether 10.0 is affected or not.
④ You use Dependabot / OSV — the GitHub advisory compresses 7.0/8.5/9.0 into a single range,
with first_patched_version = 9.0.116, so the machine will tell 8.5 users to upgrade to 9.0.116.
That is a different major-version line, not a patch.
low (the GitHub advisory marks it high / CVSS 7.5).
Both numbers are listed here; we don't pick whichever one suits us.1b586d6(9.0)· f07df938(10.1)· fde1a82(11.0)python tools/gen_table.py --dry # 只跑断言,不写文件
python tools/gen_table.py # 断言全过才写 LineTable.java
Assertions cover: positive (9.0.116 / 10.1.53 / 11.0.20 must have the fix class), negative (9.0.115 / 10.1.52 must not have it), core claim (the official recommend entry states exactly 10.1.52), EOL line, no exit (the version after the final release must 404), sentinel (a nonexistent version must 404, proving the 404 criterion itself is not broken), 10.0 absence.
mvn package # 需要 JDK 17;运行时零依赖
Apache-2.0
| Code | Meaning |
|---|---|
0 | Scan completed, and every file was actually read, with no findings requiring your action |
4 | A file could not be read — not a zip, truncated content, or read failure |
🔴 4 was added on 2026-09-09, and the reason for adding it is worth stating clearly.
Before that, unreadable files only left a line of notice in the output, while the exit code remained 0 —
leaving a trace is for humans to see, but CI and scripts look at the exit code, so "I couldn't read it" equals "passed" in automation.
A corrupted, encrypted, or incompletely downloaded jar would quietly turn into a "no issues found" message.
"I can't read it" and "you are safe" must be two different statements.
⚠️ A legitimate empty jar does not count as unreadable (a 22-byte EOCD record is a real empty zip), and will not trigger 4 —
when there are too many false alarms, nobody pays attention to the real ones.
For the meaning of the remaining exit codes, see the various verdict tiers and usage notes above.