TL;DR: High-CVSS findings can still be non-reachable in a given environment, according to Nullify, because scanners score severity without deployment and exposure context. Triage needs evidence from the code path and runtime setup before teams spend effort on a finding.
Editorial analysis by NHI Mgmt Group, based on content published by Nullify: “Stop Paying to Triage Vulnerabilities That Were Never Reachable”.
Key questions
Q: Why do high-severity scanner findings often turn out to be low priority?
A: Because scanners usually score the worst possible outcome, not the outcome in your environment.
Q: What are the signs that OT vulnerability triage is failing?
A: Common signs include long lists of critical findings with no remediation order, repeated arguments between security and operations, and tickets that omit asset role or production impact.
Q: How should teams decide which security findings to fix first?
A: Prioritise findings that are both reachable and tied to active code paths.
Practitioner guidance
- Require deployment evidence before escalating critical findings Do not let CVSS alone determine remediation priority.
- Map repositories to live cloud workloads Build and maintain an artifact-to-infrastructure graph that links images, buckets, and packages to the compute resources that really use them, including replicas and shared services.
- Suppress weak matches before they reach triage Drop speculative links below a clear confidence floor so name similarity does not become false evidence.
Bottom line: The article argues that vulnerability management breaks down when teams treat theoretical severity as if it were equivalent to environmental risk.
Glossary terms: Reachability-Informed Triage, Artifact-to-Infrastructure Graph, Confidence threshold
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Reachability, not score, is the real vulnerability governance problem: CVSS creates urgency, but it does not create context. When a scanner treats every Critical finding as equally actionable, teams spend scarce human and AI effort on weaknesses that cannot be reached in their environment. The practical implication is simple: security operations should treat deployability and exposure as the deciding variables, not as after-the-fact enrichments.
A question worth separating out:
Q: When should organisations rely on automation versus human review in vulnerability triage?
A: Automation should do the first-pass sorting, scoring, and enrichment, while humans handle the hardest cases and validate exceptions. That balance matters because AI can miss environment-specific context or overstate confidence. Human review is still the control that keeps prioritisation honest and auditable.
👉 Read our full editorial: Reachability-first triage cuts wasted effort on non-exploitable CVEs