Opens a protected REST path without credentials. Advisory
Detect
Fingerprints FortiAnalyzer and flags CVE-2026-24858 by version.
Report
Counts checked, product, affected, and confirmed.
Targets
Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Overview
This workflow finds Fortinet FortiAnalyzer and FortiManager and sorts each host by whether its version falls in the CVE-2026-24858 range. FortiAnalyzer and FortiManager see every log and every policy push. CVE-2026-24858 is authentication bypass. CISA listed it on KEV. A below-fix 7.x login is the patch-lag you can schedule weekly as new KEV rows land. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on Forti), reads the version from /login with a fallback to the root body, 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. CVE-2026-24858 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only opens a protected REST path without credentials. It does not log in or write files.
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 Fortinet FortiAnalyzer and FortiManager from the public page title, then GET /login and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
Confirm only those flagged hosts by opening a protected REST path without credentials.
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. Fingerprint is read-only GET. Confirm is a GET of a protected REST path, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether Fortinet FortiAnalyzer and FortiManager was detected, the version read, the affected flag, and whether the REST confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root, /login, and (on flagged hosts only) a protected REST path.
Sample output
The records below are illustrative and do not come from a real run. They show one Fortinet FortiAnalyzer and FortiManager host inside the CVE-2026-24858 range, one patched host, and one host that is not the product.
Which Fortinet FortiAnalyzer and FortiManager versions does this flag?
7.0.0 through 7.0.14, 7.2.0 through 7.2.10, 7.4.0 through 7.4.9, and 7.6.0 through 7.6.5. 7.0.15, 7.2.11, 7.4.10, and 7.6.6 and later on those lines is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2026-24858 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only opens a protected REST path without credentials. Treat a confirmed row as evidence the bypass still answers, not as proof someone already used it.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is a GET of a protected REST path without credentials, only on hosts already in range. It does not log in or write files.
Does the check need credentials?
No. It fingerprints the public page and reads /login the way an external scanner would.
What is CVE-2026-24858?
Authentication bypass in FortiAnalyzer and FortiManager. CISA listed it on KEV. This workflow flags by version, then confirms by opening a protected REST path without credentials.