Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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
tomcat-check — 查出 Spring Boot 内嵌 Tomcat 的真实版本(pom 里没有),并对每条 2026 年 CVE 同时给出 ASF 官方评级与 GitHub 评级、触发条件、以及这条会不会进 Dependabot 告警 CVE-2026-41293 | Kitploit
Tools/GitHubGitHub/xiaoqimikko/tomcat-check
Vulnerability ScannersVulnerability AnalysisConfiguration AuditingWeb SecurityDevSecOpsSupply Chain Security
GitHubxiaoqimikko/tomcat-check

tomcat-check

查出 Spring Boot 内嵌 Tomcat 的真实版本(pom 里没有),并对每条 2026 年 CVE 同时给出 ASF 官方评级与 GitHub 评级、触发条件、以及这条会不会进 Dependabot 告警 CVE-2026-41293

View Repository
151 month agoNot yet reviewed
Share

tomcat-check

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.


What it solves

一、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 是 unreviewedGitHub 只用 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 unreviewed entries to reviewed at 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 officialGitHub / NVD
GradingLow / Moderate / Important / CriticalCVSS numeric score
BasisActual exploitability under default configurationMechanically computed from the vector, regardless of whether you enabled that feature
Where to see ittomcat.apache.org/security-9.htmlPushed 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.


Usage

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

What's in the output

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.

🔴 Read its output like this

  • "Hit" = your version falls within the official Affects range, which does not mean "already exploited", nor "necessarily exploitable". Of the 51 entries, only a few are exposed under the default configuration; the rest require you to explicitly enable some feature (HTTP/2, WebSocket, RewriteValve, DIGEST authentication, AJP, WebDAV, cluster communication...). Check each one against its trigger conditions.
  • WebSocket-type entries only count as hits when 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.
  • "Dependabot won't alert" does not mean GitHub is failing at its job. unreviewed is a normal process state.
  • The verdict table only covers CVEs published in 2026. No hits does not mean your version is fine.
  • The tool will not decide for you whether to upgrade — it gives you the three things you need to make that decision: which version you have installed, how the official source rates it, and what the trigger conditions are.

The 2026-08 and 2026-09 batches (added in v0.2.0)

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

How the verdict table is produced

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 ranges
  • GitHub Advisory API — GitHub ratings, CVSS, type, affected Maven coordinates

The generation process carries 7 assertions; if any one is not satisfied, it aborts and writes no file. Three of them deserve special mention:

  • ASSERT7 (parse completeness): recount the entries using a second, independent regex approach; the two sets must be exactly identical. This came from a very subtle class of mismatch — on the official page, some titles embed a link to another CVE: <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.
  • ASSERT3 (pairing direction): on the official page, the 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.
  • ASSERT6 (basis for exclusion): download the real jars for the 9.0 / 10.1 / 11.0 lines, and confirm one by one that the code for the excluded entries (cluster components, FFM connector, sample applications) is genuinely not in tomcat-embed-*. The basis for exclusion must be empirical testing, not "I remember".

To regenerate:

python tools/gen_rules.py

Build

mvn clean package     # → target/tomcat-check.jar

39 tests. Zero runtime dependencies; JUnit is test-only.

License

MIT


Need a deeper investigation?

This tool answers "am I affected or not". The following it cannot answer, and you can reach out to me for:

  • Dependencies have been shaded / relocated, or the build artifacts simply cannot be obtained
  • What needs to be determined is "whether this CVE will actually trigger on our call chain", not just a version match
  • Customization is needed for your own build process or intranet environment, or integration into an existing pipeline
  • You are dealing with a similar issue in another component, and there is no ready-made tool yet
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 →