# To tell where a new CVE hits you, run the version, configuration and exposure checks in that order

Guide, 19 Nov 2026, read 19 Nov 2026

**The short answer.** To tell where a new CVE hits you, check three things in order: the version of every copy of the product, the configuration the advisory requires, and whether an attacker can reach the asset. Each has a command. For CVE-2026-123158, five configuration checks cut an example fleet of 120 hosts to nine.

## Read the version where the running software reports it

Compare the reading with the fixed build in the advisory, not with a banner or a package name. Distribution packages carry backports under older version strings, so for OpenSSH and the Linux kernel read the package changelog or the vendor errata table.

| Product and CVE | Command or page | Compare with |
| --- | --- | --- |
| PHP, CVE-2026-109618 | php-fpm -v, php-cgi -v, or php -v from the mod_php build, on every host and image | 8.2.35, 8.3.36, 8.4.27, 8.5.12 |
| Node.js, CVE-2026-111497 | node --version on hosts, CI runners and inside images; libbrotli package version where Node links the system library | 22.23.4, 24.22.1, 26.12.1 |
| fastjson, CVE-2026-16723 | mvn dependency:tree -Dincludes=com.alibaba:fastjson, or search the SBOM | Affected 1.2.68 to 1.2.83; fixed 1.2.84 |
| OpenSSH, CVE-2026-123158 | ssh -V; on Alpine apk info -v openssh-server | 10.6p2 or the Alpine package table |
| Linux kernel, CVE-2026-46300 | uname -r; on RPM systems rpm -q --changelog kernel \| grep CVE-2026-46300 | Distribution errata; the version number alone can mislead |
| Cisco ASA and FTD, CVE-2026-76418 | show version | First fixed release for the train, such as ASA 9.20.4.50 or FTD 7.4.9 |
| F5 BIG-IP, CVE-2026-94127 | tmsh show sys version and tmsh show sys software status, on each device in a failover pair | Hotfix-BIGIP-17.1.3.5.0.41.14-ENG for 17.1.x, Hotfix-BIGIP-17.5.1.9.0.160.12-ENG for 17.5.x, Hotfix-BIGIP-21.1.0.2.0.30.22-ENG for 21.1.0 |
| PAN-OS, CVE-2026-0322 | show system info, sw-version line, on every firewall and on Panorama | 12.2.4; 12.1.4-h12, 12.1.7-h8 or 12.1.10-h2; 11.2.4-h22, 11.2.7-h21, 11.2.10-h15, 11.2.13-h3 or 11.2.16; 11.1.4-h37, 11.1.6-h39, 11.1.7-h11, 11.1.10-h35, 11.1.13-h15 or 11.1.16-h3; 10.2.7-h38, 10.2.10-h41, 10.2.13-h26, 10.2.16-h11 or 10.2.18-h12. Use the entry for your sub-train |
| Artifactory, CVE-2026-82329 | GET /artifactory/api/system/version on every self-hosted instance | 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38, 7.161.20 |
| VMware ESX, CVE-2026-41709 | esxcli system version get | Build 25370933 (9.1), 25595025 (9.0), 25429389 (8.0) |
| WordPress, CVE-2026-119977 | wp core version | 7.1.4, 7.0.8, 6.9.11 and so on down to 4.7.39 for older branches |
| Windows, CVE-2026-68820 | winver, or [System.Environment]::OSVersion.Version | Fixed builds of 11 Aug 2026. Windows 11 24H2 and Server 2025 share the 26100 build number but are serviced by different packages, so their revisions differ (Microsoft CVRF): 11 24H2 10.0.26100.9106 or 9168; Server 2025 10.0.26100.33222 or 33296. Others: Server 2012 6.2.9200.26280; Server 2012 R2 6.3.9600.23338; 10 1607 and Server 2016 10.0.14393.9418; 10 1809 and Server 2019 10.0.17763.9121; 10 21H2 10.0.19044.7663; 10 22H2 10.0.19045.7663; Server 2022 10.0.20348.5440 or 5499; 11 23H2 10.0.22631.7517; 11 25H2 10.0.26200.9106 or 9168; 11 26H1 10.0.28000.2704 |

## Find the copies you did not install

Search for the component, not only the product. The Node.js upgrade for CVE-2026-111497 fixes only the copy Node.js bundles. Every other copy of Brotli needs its own: Google Brotli 1.0.10, 1.1.1 or 1.2.1, the distribution package, Bun 1.4.4, PyPI Brotli 1.2.1. The PHP advisory covers PHP embedded in appliances and container base images as much as PHP you installed.

To sweep images for a runtime, loop over them: for i in $(docker images --format '{{.Repository}}:{{.Tag}}'); do echo "$i $(docker run --rm --entrypoint node $i --version 2>/dev/null)"; done. Swap node for php-fpm or php. For libraries, search the dependency tree or the SBOM, and on hosts run ldconfig -p | grep -i brotli and pip list | grep -i brotli. For Java, the fastjson advisory's trigger is a Spring Boot executable fat-jar run with java -jar. Plain jar, uber-jar and WAR deployments do not meet it, so list how each service is packaged.

ScreenConnect is the reverse case: servers are not affected, clients are. ConnectWise says not to rely on the console version alone, because updating the console does not update technician clients.

## Check the configuration the advisory requires

A condition removes hosts from the list only if you test it on each host and keep the output. These are the commands for conditions in the 2026 records.

| Condition | Command or page | In scope when |
| --- | --- | --- |
| OpenSSH CVE-2026-123158: musl without PAM | ldd $(command -v sshd) \| grep -iE 'musl\|pam'; sshd -T \| grep -i usepam | libc.musl appears, no PAM library, or UsePAM is no |
| Password login on | sshd -T \| grep -iE 'passwordauthentication\|permitrootlogin'; also read Match blocks in /etc/ssh/sshd_config.d/ | passwordauthentication yes |
| An account with no password, and one with a hash | awk -F: '$2=="*"{print $1}' /etc/shadow, then awk -F: '$2 ~ /^\$[56]\$/{print $1}' /etc/shadow | Both commands print at least one name. Accounts locked with ! do not count |
| Cisco CVE-2026-76418: SSL VPN on | show running-config webvpn | A line enable <interface_name> |
| Secondary authentication in scope | show running-config tunnel-group | secondary-authentication-server-group in any group, including DefaultWEBVPNGroup, even when tunnel-group-list is disabled |
| F5 CVE-2026-94127: APM provisioned | tmsh list sys provision apm | A level other than none |
| APM is an OAuth authorization server on a virtual server | tmsh list ltm virtual all-properties; GUI Access > Federation > OAuth Authorization Server | A virtual server with an access profile and an OAuth profile; an empty page means not in scope |
| SonicWall CVE-2026-19868: SAML and an alternate server | SonicOS SSLVPN user authentication settings; Device > Users > Settings > Authentication > Configure RADIUS, LDAP or TACACS+ > Settings | SAML is the SSLVPN login method and any listed server is not disabled |
| Artifactory CVE-2026-82329: default join key | Look under shared, security in system.yaml for additionalJoinKeys; in containers read JF_SHARED_SECURITY_ADDITIONALJOINKEYS | No additional join key set |
| Tomcat CVE-2026-34486: clustering with EncryptInterceptor | version.sh; grep -nE 'Cluster\|EncryptInterceptor' conf/server.xml | Version exactly 11.0.20, 10.1.53 or 9.0.116, plus both strings in server.xml |
| WordPress CVE-2026-119977: upgrade runs | wp config get WP_AUTO_UPDATE_CORE; Dashboard > Updates | Updates run automatically, or an admin or WP-CLI upgrade is planned |
| Staging folder is public | curl -sI https://example.test/wp-content/upgrade/ from outside; ls -la wp-content/upgrade/ on the host | 200 or a listing means reachable; 403 or 404 means blocked. A folder named after the package with no random suffix is the unfixed behavior |

## Check the exposure from the attacker's side

Sort matches into four groups: reachable from the internet, reachable from partner networks, reachable from the internal network, and isolated. Record the source of each answer: an external scan, a firewall rule export or an architecture note. Exposure from memory is the usual source of a missed host.

Run the checks that need a vantage point from outside: curl -sI against the URL, the VPN login page of the ASA or SonicWall tested from an untrusted network, ss -ltnp | grep sshd on the host with the security-group rules beside it, and for Tomcat clusters ss -ltnp for ports 4000 to 4100. On PAN-OS, Permitted IP Addresses and every Network > Network Profiles > Interface Mgmt profile that allows HTTPS or SSH show what the management interface admits. On BIG-IP, the flaw is on the data plane, so the virtual server address and the self IPs that expose it decide exposure, not the management port.

Do not drop the internal group. Some bugs need an attacker who already runs code, and CISA's KEV entry for the Linux flaw CVE-2026-46300 says it was chained with the two PHP2Shell CVEs to implant web shells and run commands as root. Windows CVE-2026-68820 needs a local user. Artifactory CVE-2026-42018 hands out a low-privilege token that CVE-2026-42016 turns into an admin token. For these, the exposure question is whether untrusted code or an untrusted token can reach the host.

## Who runs each check and what to keep as evidence

The owner and the record turn a check into evidence a reviewer can use. Failures are listed once, by check.

| Check | Run by | Output kept as evidence | How it fails |
| --- | --- | --- | --- |
| Version | Platform team, through configuration management or the product's own page | The command output per host, with host name and UTC time | A backport: the version string is below the fixed one but the package is patched. Keep the changelog line or errata entry beside the reading |
| Copies you did not install | Application owners, with the build team | Image digests and the SBOM query result | Images not scanned: the sweep covers running containers but not stopped ones, base images in the registry or CI runners. Name what the sweep covered |
| Configuration | Platform team | The configuration command output per host, including Match blocks and drop-in files | One member of a failover pair, or one drop-in file, is read and the other is not |
| Exposure | Network owner, from outside the network | The external scan or request output and the firewall rule export, each dated | Stale exposure data: the scan or export is older than the last firewall or security-group change. Rerun it, and print its date in the record |

## Worked scoping: five checks narrow 120 hosts to nine for CVE-2026-123158, and a sixth sorts them by exposure

The counts below are an invented fleet of 120 Linux hosts to show the arithmetic; the conditions and commands come from the record. Each row runs on the survivors of the row before, and each excluded host gets a one-line reason in the record.

| Check | Hosts left |
| --- | --- |
| Start: Linux hosts running sshd | 120 |
| sshd links musl | 31 |
| No PAM, or UsePAM no | 26 |
| PasswordAuthentication yes | 19 |
| At least one account with * as its password field | 12 |
| At least one other account with a $5$ or $6$ hash | 9 |
| Port 22 reachable from an untrusted network | 4 internet, 5 internal |

## When the usual answer is wrong

A version number below the fixed one does not always mean exposed. Alpine's fixed OpenSSH package for 3.22 is 10.0_p1-r11 and for 3.21 is 9.9_p2-r1. Both report a version far below 10.6p2 and are patched for CVE-2026-123158, so compare the package release with the vendor table, not with the upstream number.

A version at or above a fixed-looking number does not always mean safe. OpenSSH 10.6 and 10.6p1 are affected; only 10.6p2 carries the fix. The same holds in the other direction for configuration: a Cisco ASA on a vulnerable release without secondary authentication on any tunnel group, including DefaultWEBVPNGroup, is outside CVE-2026-76418, and a ScreenConnect server at any version tells you nothing about the clients.

## Repeat the match when the advisory changes

Advisories grow. Fortinet revised FG-IR-26-175 on 5 Oct 2026 and again on 7 Oct, when it named FortiMail 7.2.10 as an upcoming fix. SonicWall's version 1.1 of 9 Nov updated its workaround. WordPress published 7.1.5 on 18 Nov, after the 7.1.4 release of 28 Oct. Keep the advisory URL and its read time in the record so the second read is a diff against the first, and rerun the match at 24 hours and after the patch.

Log each gap the inventory missed. A recurring one, such as components bundled in vendor appliances, belongs in the supplier questionnaire as a request for a component list. The tools page shows where 14 vendors say a new CVE lands.

## Related pages

- [The 72-hour post-incident review: template and a worked review of the BeyondTrust zero-day](/guides/72-hour-post-incident-review/)
- [Mitigations that buy time before the patch](/guides/mitigations-that-buy-time/)
- [Compromise assessment after patching a critical flaw](/guides/compromise-assessment-after-patching/)

## Sources

- PHP security advisory GHSA-w8hw-w9fx-j79w: https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (read 19 Nov 2026)
- Node.js security releases, 21 Oct 2026: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (read 19 Nov 2026)
- fastjson2 wiki, security advisory for fastjson 1.2.68 to 1.2.83: https://github.com/alibaba/fastjson2/wiki/Security-Advisory:-Remote-Code-Execution-in-fastjson-1.2.68%E2%80%931.2.83 (read 19 Nov 2026)
- Alpine Linux advisory, OpenSSH password authentication bypass, 5 Nov 2026: https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/ (read 19 Nov 2026)
- OpenSSH 10.6p2 release notes: https://www.openssh.org/releasenotes.html#10.6p2 (read 19 Nov 2026)
- Red Hat CVE page for CVE-2026-46300: https://access.redhat.com/security/cve/CVE-2026-46300 (read 19 Nov 2026)
- Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75 (read 19 Nov 2026)
- F5 advisory K000162605: https://my.f5.com/manage/s/article/K000162605 (read 19 Nov 2026)
- SonicWall PSIRT advisory SNWLID-2026-0014: https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014 (read 19 Nov 2026)
- Palo Alto Networks advisory CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- JFrog security advisories, CVE-2026-82329 section and workaround: https://docs.jfrog.com/releases/docs/jfrog-security-advisories (read 19 Nov 2026)
- JFrog documentation, Get Artifactory Version API: https://docs.jfrog.com/administration/reference/getartifactoryversion (read 19 Nov 2026)
- Broadcom security advisory VMSA-2026-0006: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 (read 19 Nov 2026)
- WordPress 7.1.4 security release note: https://wordpress.org/news/2026/10/wordpress-7-1-4 (read 19 Nov 2026)
- WordPress core source, 7.1.4 tag, class-wp-upgrader.php: https://raw.githubusercontent.com/WordPress/wordpress-develop/7.1.4/src/wp-admin/includes/class-wp-upgrader.php (read 19 Nov 2026)
- Microsoft MSRC CVRF, August 2026 release: https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug (read 19 Nov 2026)
- Microsoft MSRC record for CVE-2026-68820: https://api.msrc.microsoft.com/sug/v2.0/en-US/vulnerability/CVE-2026-68820 (read 19 Nov 2026)
- Apache Tomcat 11 clustering guide: https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html (read 19 Nov 2026)
- Apache Tomcat 11 security page: https://tomcat.apache.org/security-11.html (read 19 Nov 2026)
- Fortinet PSIRT advisory FG-IR-26-175: https://fortiguard.fortinet.com/psirt/FG-IR-26-175 (read 19 Nov 2026)
- ConnectWise ScreenConnect security bulletin, 8 Sep 2026: https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin (read 19 Nov 2026)
- GreyNoise event page and timeline for CVE-2026-123158: https://sshole.events.greynoise.io/ (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-46300: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-46300 (read 19 Nov 2026)
- NVD record for CVE-2026-123158: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-123158 (read 19 Nov 2026)
- NVD record for CVE-2026-42016: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-42016 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/guides/where-a-new-cve-hits-you/
