Offline NetScaler ADC / Gateway evidence checker for CVE-2026-88772. Reported firmware and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads.
Assess reported NetScaler builds and DTLS configuration for CVE-2026-88772
CVE-2026-88772 · offline, single-file, dependency-free
An offline, single-file checker that assesses reported NetScaler ADC and Gateway builds and supplied DTLS configuration exports for CVE-2026-88772, using a verified embedded advisory snapshot.
It needs Python 3.10+ and nothing else: no packages, no network access and no companion runtime files. Copy netscaler_check.py and run it. JSON, CSV and offline HTML reports are produced from the same validated evidence records.
[!IMPORTANT] This is an evidence assessment, not a scan. Supplied builds and exports do not prove what is deployed. A reported fixed build is not a verified patch, and potential exposure is not confirmed exploitability. Exploitability is always
not_tested: reachability, local exploitation and prior compromise are not tested. Missing, incomplete or unsupported evidence staysunknown. This repository covers one CVE; adjacent NetScaler vulnerabilities need their own checkers.
Check only assets you are authorized to assess, and keep real inventories, exports and reports out of version control.
Requirements: Python 3.10+ (standard library only). Nothing is installed and nothing contacts the network.
# One device, by reported build
python netscaler_check.py --product netscaler-adc --edition standard --version 14.1-73.36
python netscaler_check.py --product netscaler-adc --edition fips --version "13.1.37.279 FIPS"
# One device, with a complete exported configuration
python netscaler_check.py --product netscaler-gateway --edition standard --version 14.1-73.36 --config examples/dtls-disabled.conf --config-complete
# Inventory CSV, as JSON or as an offline HTML report
python netscaler_check.py --inventory examples/inventory.csv --format json
python netscaler_check.py --inventory examples/inventory.csv --format html --output report.html --brand "Example organization" --logo assets/logo.png
examples/ contains synthetic data only. Output files are created without overwriting an existing file; use --force for deliberate report replacement. Inputs and supplied logos remain protected even with --force.
Run python netscaler_check.py --help for the complete CLI. Exactly one of --version or --inventory is required.
| Option | Purpose |
|---|---|
--version BUILD | Exact reported build for a single device. Requires --product. |
--product | netscaler-adc or netscaler-gateway. |
--edition | unknown (default), standard, fips or ndcpp. An explicit supported edition is required for classification. |
--deployment | self-hosted (default), vendor-managed or unknown. Managed or unknown deployments remain unknown. |
--build-source | unknown (default), upstream, vendor or custom. Vendor/custom builds cannot be cleared by an upstream number. |
--asset-id | Opaque report identifier (default device-0001). Do not supply a hostname or secret. |
--config FILE, --config-complete | Local exported configuration for the device, and your assertion that it is complete for that device. |
--inventory CSV | CSV inventory of devices instead of a single --version; see examples/inventory.csv. Per-device options cannot be combined with it. |
--format json|csv|html | Report format (default json). |
--output FILE | Write the report atomically instead of to stdout. Existing files are protected unless --force is given. |
--brand TEXT, --logo FILE | HTML only: escaped organization label and optional PNG/JPEG/GIF/WebP logo up to 1 MiB. |
--fail-on-finding, --fail-on-unknown | Exit 1 when a finding or unresolved evidence matches; see exit codes. |
An upstream build has the exact numeric shape 14.1-73.36. FIPS and NDcPP builds accept a matching FIPS or NDcPP suffix with the explicit edition. Prereleases, build metadata, multiple versions, mismatched suffixes and leading zeroes remain unknown. Comparison never crosses a release branch or edition. The full grammar is in the reference.
Supply an authentic export with --config-complete (or CSV config_complete=true) only when it covers the intended device. The flag is an operator assertion that the tool cannot verify, and no file is executed. Supported VPN add commands default DTLS to ON, and ordered set commands override only that server. Missing, incomplete, malformed or unsupported configuration remains unknown, and only a complete, unambiguous supported export can establish that the DTLS prerequisite is absent. The grammar is deliberately narrow, so a valid full appliance export may still produce unknown; retain the complete export rather than removing lines to obtain a negative result. Grammar, limits and exact behavior are in the reference.
Inventory input is UTF-8 CSV with one header and one device per row (columns asset_id, product, version, edition, deployment, build_source, config_file, config_complete). config_file is a relative path beneath the CSV directory. Limits are 4 MiB, 1,000 devices and 1,024 characters per field. Report asset labels and exact valid build numbers are operator-supplied facts; review them before sharing a report. See the reference for column rules.
| Status | Meaning in this checker |
|---|---|
unknown | The supplied product/version/provenance cannot be classified. |
potentially_affected | The reported version is below the verified fix; effective DTLS is unresolved. |
precondition_present | An affected version and complete supported export indicate DTLS enabled. |
mitigated_configuration | An affected version remains recorded, while the supplied complete export indicates the DTLS prerequisite absent. |
fixed_version_reported | The reported build meets the verified fix within its exact branch/edition. Not a guarantee of patch installation. |