Unauthenticated OPTIONS probe of the host root. This proves PUT is advertised, not that a file was written. CVE-2025-24813 details
Detection
Detect fingerprints Apache Tomcat and flags CVE-2025-24813 by version. No probe.
Report
mention the confirmed count as well as checked / product / affected.
Targets
Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Overview
This workflow finds Apache Tomcat and sorts each host by whether its version falls in the CVE-2025-24813 range. CVE-2025-24813 is partial PUT path-equivalence that can lead to session deserialization. CISA listed it on KEV after confirmed use. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the Server header or a public error page, reads the version, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. Version flag is first. Hosts in range get a second node that sends OPTIONS and looks for PUT in Allow. It does not PUT a file.
Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fingerprint each host as Tomcat from the Server banner or error page, then compare the version to the CVE-2025-24813 floors in the graph.
Confirm only those flagged hosts with an unauthenticated OPTIONS request. It does not PUT a file.
Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.
Inputs
Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test.
Outputs
results.jsonl. One row per host: URL, whether Tomcat was detected, the version read, the affected flag, and whether OPTIONS advertised PUT.
summary.json. Counts across the list: targets, product hits, affected, confirmed, and errors.
Integrations
HTTP. Unauthenticated GET to the product surface and, on flagged hosts only, OPTIONS. No PUT.
Sample output
The records below are illustrative and do not come from a real run. They show one Tomcat host inside the CVE-2025-24813 range, one patched host, and one host that is not the product.
Tomcat 11.0 before 11.0.3, 10.1 before 10.1.35, and 9.0 before 9.0.99. The compare uses the version the product itself served.
Does a confirmed row mean a file was written?
No. Confirm only sends OPTIONS and looks for PUT in Allow. It does not PUT a file. A confirmed row means the server advertises PUT.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is OPTIONS, only on hosts already in range. It does not log in or write a file.
Does the check need credentials?
No. It fingerprints the public page the way an external scanner would.
What is CVE-2025-24813?
Partial PUT path-equivalence on Tomcat that can lead to session deserialization. CISA listed it on KEV after confirmed use. This workflow flags by version, then confirms PUT is advertised, without writing a file.