Skip to content
KitploitKITPLOIT
ToolsBlog
Log in
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/xiaoqimikko/tomcat-line-check
Vulnerability ScannersConfiguration AuditingWeb SecuritySupply Chain Security
GitHubxiaoqimikko/tomcat-line-check

tomcat-line-check

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.

View Repository
512 months agoNot yet reviewed
Share

tomcat-line-check

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 控制台中文乱码时加

There is only one criterion, and you can reproduce it yourself

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.

Measured results for the seven lines

LineFinal versionEOLFix presentExit
7.07.0.1092021-03-31None❌ 7.0.110 = 404
8.08.0.532018-06-30None❌ 8.0.54 = 404
8.58.5.1002024-03-31None❌ 8.5.101 = 404
10.010.0.272022-10-31None❌ 10.0.28 = 404
9.09.0.1212027-03-319.0.115 no✅ 9.0.116
10.110.1.59Not EOL10.1.52 no✅ 10.1.53
11.011.0.25Not EOL11.0.18 no✅ 11.0.20

Four cases where "that official sentence doesn't hold for you"

① 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.

The boundaries of what this says (this tool does not cross them, and neither should you)

  • "The fix code is missing" is a fact about the artifact; "you are affected" is another matter, which requires upstream confirmation — and on the 10.0 line, precisely no one has confirmed it. This tool's wording is always the former.
  • Request smuggling is only harmful when there is a front-end proxy and the two ends interpret things differently. You can't tell an attack story about a bare-running Tomcat.
  • The original Apache advisory rates this as low (the GitHub advisory marks it high / CVSS 7.5). Both numbers are listed here; we don't pick whichever one suits us.

First-hand sources

  • Apache 原始公告(oss-security,Mark Thomas,2026-04-09): http://www.openwall.com/lists/oss-security/2026/04/09/20
  • GitHub advisory:https://github.com/advisories/GHSA-563x-q5rq-57qp
  • 修复 commit:1b586d6(9.0)· f07df938(10.1)· fde1a82(11.0)
  • 版本线与 EOL:https://endoflife.date/tomcat

Regenerating the verdict table

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.

Build

mvn package      # 需要 JDK 17;运行时零依赖

License

Apache-2.0

Exit codes

CodeMeaning
0Scan completed, and every file was actually read, with no findings requiring your action
4A 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.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    851
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    538
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    420
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    297
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    280

Explore all tools

Browse our collection of tools

View all tools →