Offline Ivanti Connect Secure evidence checker for CVE-2026-104935. Connect Secure build and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.
Ivanti Connect Secure: Authentication bypass by spoofing
CVE-2026-104935 · branch-aware offline version triage · CISA KEV-listed
ivanti_connect_secure_cve_2026_104935_check.py is a standalone Python checker for CVE-2026-104935. It compares operator-reported Ivanti Connect Secure release numbers with the vendor's branch-specific affected and fixed ranges, and writes CSV, JSON or HTML reports.
[!IMPORTANT] CISA lists this CVE in its Known Exploited Vulnerabilities (KEV) catalog. A
fixed_version_reportedresult is a version observation, not evidence that an appliance was not already compromised, andpotentially_affectedis not confirmed exploitability. This tool does not detect compromise.
exploitability: not_tested.python ivanti_connect_secure_cve_2026_104935_check.py --version 25.1.1.1 --version 22.8R2.5 --format json
python ivanti_connect_secure_cve_2026_104935_check.py --inventory examples/inventory.example.json --format html --output report.html
python ivanti_connect_secure_cve_2026_104935_check.py --csv examples/versions.example.csv --fail-on-finding
On systems where Python is called python3, substitute it. The examples in examples/ use synthetic placeholder data. Run --help for all options.
At least one of --version, --inventory or --csv is required. Inputs can be combined, and each entry is a separate observation (up to 10,000 per run).
| Option | Default | Purpose |
|---|---|---|
--version RELEASE | none | Assess one reported release number; repeatable. |
--inventory FILE | none | Assess a JSON inventory (schema_version 1); repeatable. |
--csv FILE | none | Assess a CSV list with a version column; repeatable. |
--format csv|json|html | csv | Report format. |
--output PATH | stdout | Write a new file. Existing files are refused unless --force; the directory must exist and no input file may be the output. |
--force | off | Replace an existing output file. |
--brand NAME | CompleteTech LLC | Organization name in the HTML report (at most 128 characters, no control characters). |
--fail-on-finding | off | Exit 1 when any result is potentially_affected. |
--tool-version | Print the checker version. |
Release numbers must be plain stable releases: dotted (25.1.3.0) or R-style (22.8R2.5, where 22.8R2 means build 0). Partial values (25.1), build suffixes, hotfix labels, prereleases and non-ASCII digits are reported as unknown. Inventory fields (label, product, version_candidates, build_source, reachable_from_untrusted_network), CSV columns, size limits and parsing rules are in docs/REFERENCE.md.
| Code | Meaning |
|---|---|
0 | Completed. Findings do not change this unless --fail-on-finding is set. |
1 | --fail-on-finding was set and at least one result is potentially_affected. |
2 | Argument, input or output error. Takes precedence over 1; nothing is reported for invalid input. |
130 | Interrupted. See Interruption and partial results for what is preserved. |
unknown results are assessment outcomes, not errors. Operational failures (exit 2) are never reported as assessment results.
Do not treat every release below 25.1.3.0 as affected. The fix differs per branch:
| Release line | Potentially affected | Fixed version reported | Evidence |
|---|---|---|---|
| 25.1.0.0 through 25.1.1.x | 25.1.0.0 up to 25.1.1.1 | 25.1.1.2 or later in 25.1.1.x (backport) | NVD and Ivanti blog (medium) |
| 25.1.2.x | 25.1.2.0 and later in 25.1.2.x | 25.1.3.0 or later in 25.1 (25.1.3.1 also listed unaffected) | CNA and NVD (high) |
| 22.8R2.x | 22.8R2 through 22.8R2.4 | 22.8R2.5 or later in 22.8R2.x | CNA and NVD (high) |
| 22.7R2.14 and prior (22.x releases from 22.1R1) | not affected by this CVE per the CNA record | reported as unknown with vendor_reported_unaffected_release | CNA and NVD (high) |
Everything else (25.0.x, 25.2 and later, 22.8R1, 22.8R3, 22.7R2.15+, and so on) is unknown (release_line_not_in_rules): it is not covered by the dated rule snapshot and is never assumed fixed or affected. 22.7R2.14 and prior is unaffected by this CVE only; it does not attest security against other vulnerabilities, and the checker does not call it fixed.
The rules are a dated snapshot (reviewed 2026-10-24). Per-rule affected and fixed bounds, evidence and confidence are in docs/REFERENCE.md.