Point hosts at Progress LoadMaster and flag CVE-2026-8037 (command injection) from a version compare, then echo a short token on /accessv2. Non-destructive.
Fingerprints LoadMaster and flags CVE-2026-8037 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 Progress LoadMaster and sorts each host by whether its version falls in the CVE-2026-8037 range. LoadMaster is the ADC some estates never replaced. CVE-2026-8037 is command injection that CISA listed on KEV. The check reads /access/login and flags the two trains the graph encodes. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on LoadMaster), reads the version from /access/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-8037 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only echoes a short unique token on /accessv2. It does not open a shell 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 Progress LoadMaster from the public page title, then GET /access/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 echoing a short unique token on /accessv2.
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 token echo on /accessv2, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether Progress LoadMaster was detected, the version read, the affected flag, and whether the token-echo confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root and /access/login. Confirm is a token echo on /accessv2, only on flagged hosts.
Sample output
The records below are illustrative and do not come from a real run. They show one Progress LoadMaster host inside the CVE-2026-8037 range, one patched host, and one host that is not the product.
Which Progress LoadMaster versions does this flag?
every build before 7.2.54.18, and 7.2.55.0 through 7.2.63.1. 7.2.54.18 on the 7.2.54 line, and 7.2.63.2 and later on the 7.2.55+ line 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-8037 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only echoes a short unique token on /accessv2. Treat a confirmed row as evidence the injection still answers, not as proof someone already used it.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is a token echo on /accessv2, only on hosts already in range. It does not open a shell or write files.
Does the check need credentials?
No. It fingerprints the public page and reads /access/login the way an external scanner would.
What is CVE-2026-8037?
Command injection in Progress LoadMaster. CISA listed it on KEV. This workflow flags by version, then confirms with a token echo on /accessv2.