Prove a finding is not exploitable by naming the failed precondition and keeping dated evidence for it
A closure is a failed precondition, not a feeling of safety
A finding is not exploitable on a system when one condition the advisory requires is false there. The advisory must name the condition, and your evidence must show it is false on this system, on a date. The first condition that fails ends the test. The record holds that one condition, the proof the advisory still lists it, and nothing else.
A CVSS score cannot stand in for that proof. The FIRST CVSS v4.0 user guide says Base scores "are designed to measure the severity of a vulnerability and should not be used alone to assess risk".
Five kinds of evidence can fail a precondition
Version and build evidence is mechanical and the strongest. Configuration and deployment evidence changes with the system, so each needs a date and a re-check trigger. The examples are preconditions from the ledger records.
| Evidence | Ledger precondition | What makes the claim stale |
|---|---|---|
| Version outside the affected range | CVE-2026-88779 Citrix NetScaler ADC and Gateway: builds before 14.1-73.41 and 13.1-64.28 are affected, and those builds and later are fixed | Restoring an older build from backup or downgrading |
| Deployment form excludes the trigger | CVE-2026-16723 fastjson: the advisory says plain jar, uber-jar and Tomcat or Jetty WAR deployments do not meet the trigger | Repackaging as a Spring Boot executable fat-jar |
| Feature or role not enabled | CVE-2026-94127 BIG-IP APM: affected only as an OAuth Authorization Server | A profile change |
| Platform excludes it | CVE-2026-75604 Next.js: Linux and macOS hosts are not described as affected | Moving the workload to a Windows host |
| Interface not reachable | CVE-2026-0322: needs network access to the management interface | A firewall or routing change |
Worked case: fastjson 1.2.76 in a Tomcat WAR, closed against CVE-2026-16723
The finding. On 19 Nov 2026 a scanner flags invoice-api, a service used here as an illustration, for fastjson 1.2.76. CVE-2026-16723 is a remote code execution flaw in fastjson 1.2.68 to 1.2.83. The advisory, dated 21 Jul 2026 and updated 29 Jul 2026, rates it Critical and lists the conditions: the version range, AutoType and SafeMode off (the defaults), and "Spring Boot executable fat-jar (i.e., launched via java -jar xxx.jar)". Its not-affected table lists "Non-fat-jar deployments", including "Tomcat/Jetty WAR". The ledger records no KEV entry for it.
The test starts with the cheapest condition to falsify, which is the deployment form. Version 1.2.76 is inside the range, so the version cannot close the finding, and the other two conditions are properties of defaults. The steps below are what the engineer runs. The output shown is the illustration's output.
- E1, version. In the build checkout, run
mvn dependency:tree -Dincludes=com.alibaba:fastjson. Output:com.alibaba:fastjson:jar:1.2.76:compile. This confirms the finding is real and in range. - E2, artifact shape. Run
unzip -l invoice-api-4.8.2.war | grep -c BOOT-INFand read the manifest withunzip -p invoice-api-4.8.2.war META-INF/MANIFEST.MF. Output: 0 BOOT-INF entries, and a manifest with no Main-Class line. A Spring Boot executable archive carries a launcher entry point, and this one has none. - E3, how it runs. On host web-12 run
ps -o args= -C javaandls /opt/tomcat/webapps. Output: one process whose arguments startorg.apache.catalina.startup.Bootstrap, andinvoice-api.warunpacked under webapps. No process runsjava -jaron any invoice-api archive. - E4, pipeline. Read the deploy job definition in the CI system. It copies the WAR into /opt/tomcat/webapps and restarts Tomcat. It has no step that starts a jar. The owner of the pipeline confirms in the ticket.
The record that closes the finding
The record cites E1 to E4 by label and holds no copy of their output, which is attached to the ticket. A second person, not the engineer who ran the checks, signs it after reading the attachments and the advisory page.
| Field | Entry |
|---|---|
| Claim | Not exploitable on invoice-api, host web-12, as of 19 Nov 2026 |
| Advisory and revision | CVE-2026-16723, fastjson2 wiki advisory dated 21 Jul 2026, updated 29 Jul 2026 |
| Precondition tested | Deployed as a Spring Boot executable fat-jar launched with java -jar |
| Result | False: the artifact is a WAR with no Spring Boot launcher, run by Tomcat (E2, E3, E4) |
| Finding still real | Yes: fastjson 1.2.76 is present (E1), so the dependency stays on the upgrade list |
| Run by | Service engineer, 19 Nov 2026, build 4.8.2 |
| Signed off by | Security reviewer, 19 Nov 2026, after repeating E2 |
| Stale if | The artifact is rebuilt as an executable jar or executable WAR run with java -jar, the advisory is revised, or CVE-2026-16723 is added to KEV |
| Review date | 19 Feb 2027, or at the first trigger |
A closure holds only while the stale conditions stay false
Wire each stale condition to an event. A change to the build packaging should reopen the record. So should an advisory revision, or a KEV listing of the CVE. A calendar date alone misses all three. The claim also stays narrow: 'not exploitable on host web-12 as of 19 Nov 2026' ages better than 'not exploitable'.
The closure leaves fixing the dependency a separate decision. The advisory's fixes are fastjson 1.2.84, SafeMode, a noneautotype build or a move to fastjson2, and they remove the dependence on the deployment form.
Some advisories leave no precondition to fail
The ledger records Cisco's position for CVE-2026-76460: ISE and ISE-PIC on a release without the patch are affected with no configuration dependency, so a configuration argument has nothing to test. Atlassian says instances with user authentication should still be treated as exposed for CVE-2026-21589, so only the fixed version or restricted network access changes the answer.
Two more cases need care. GitLab says CVE-2026-97229 is exploitable "under certain conditions" and does not publish them, so the honest record reads 'not provable'. The fastjson advisory itself leaves one gap: it does not say how a Spring Boot executable WAR run with java -jar is treated. Evidence for that packaging must show the manifest and the launch command, as E2 and E3 do above.
Timing can also flip a result. WordPress CVE-2026-119977 is reachable only during a full-package core upgrade, and sites with automatic background updates open that window without an administrator acting. A check run on a quiet day proves nothing about the upgrade window.
Related pages
Sources
- fastjson advisory for CVE-2026-16723, dated 21 Jul 2026, updated 29 Jul 2026, read 19 Nov 2026
- FIRST CVSS v4.0 user guide, read 19 Nov 2026
Last reviewed 19 Nov 2026.