A widely reported CVE is not automatically applicable to your environment. Start with the product and version, then combine severity, known exploitation, exposure and business impact to prepare a verifiable remediation decision.
Record product, version, component, owner and business role. Check the vendor advisory and exploitation prerequisites. An old public banner does not establish the currently installed version.
2
Read severity with its vector
Retain CVSS version, vector, score source and prerequisites such as privileges or user interaction. A context-free number is insufficient for comparing cases.
3
Review exploitation signals
Consult KEV for known exploitation and EPSS for a thirty-day estimate. Record their dates. An EPSS percentile is a rank, distinct from probability.
4
Assess exposure and consequences
Work with the authorised team to establish component accessibility, prerequisites and affected data or operations. Defensive assessment does not require trying an exploit against a public target.
5
Select and verify the measure
Apply the patch or vendor-recommended temporary mitigation through the change process. Retain validation, functional tests, owner and the review date for temporary measures.
CVSS, KEV and EPSS answer different questions
CVSS describes technical severity. KEV lists vulnerabilities with known real-world exploitation. EPSS estimates exploitation probability over the next thirty days. None alone describes the consequences for your asset.
A low EPSS score does not cancel known exploitation. A CVE missing from KEV may still be exploited. CISA catalog deadlines belong to a US federal framework; define organisational deadlines using your context and obligations.
Document affected and unaffected assets
Preserve the inventory used, actually installed version and advisory passage supporting applicability. An assumption based only on a search result remains unconfirmed.
If the version or prerequisite cannot be checked, retain a pending-verification status. To close as not applicable, record the technical reason and source instead of silently dismissing the alert.
Explain the decision rather than combining scores
Review exploitation, component accessibility, existing controls and business consequences separately. An exposed application handling sensitive data may warrant different action from an isolated component with the same severity score.
Document planned remediation, temporary containment, incident investigation or demonstrated non-applicability. A compensating control needs an owner, effectiveness limits and a review deadline.
Verify after the change
Check the corrected version, actually loaded component and service availability. A closed ticket or downloaded package does not prove every affected asset has been updated.
If compromise indicators exist, patching alone does not close the incident. Preserve available logs and initiate response with the responsible team.
Identify the actually patched branch
Some vendors backport fixes into maintained branches. An upstream version alone may therefore mislead: compare installed build, branch and vendor advisory. Confirm component, configuration and exploitation conditions; bundled dependencies may need their own check.
Do not add incompatible signals
Severity, estimated probability, known exploitation and asset exposure answer different questions. Agree remediation evidence and functional checks before intervention. Afterwards verify the running state, not merely a downloaded patch; mitigation retains an owner and review condition.
Four questions before closing a vulnerability alert
Editorial reading framework; no statistical measurements are represented.
Severity: what technical impact?
Exploitation: observed or estimated?
Asset: present and exposed?
Remediation: verified on the system?
These signals answer different questions and do not form a universal additive score.
Reading technical evidence
Keep the CVSS vector alongside the score
A score alone hides its assumptions. CVSS v4 separates Base, Threat and Environmental metrics.
Field or situation and its interpretation
Observed item
What it means
CVSS-B
Intrinsic severity based on Base metrics.
CVSS-BT
Also accounts for Threat metrics.
CVSS-BTE
Also incorporates the specified Environmental context.
Retain version, vector, source and date. Then check product, installed version and exposure conditions before prioritising action.
Prioritise a CVE with exploitation and asset evidence
CISA’s KEV catalogue identifies vulnerabilities known to be exploited. Combine that signal with the installed product and version, reachable service and asset criticality. A proof of concept is distinct from observed exploitation; absence from KEV does not establish safety.
Assign an owner, action and verification date. Agree the expected version, any required restart and a functional check before intervention. Retain the vendor advisory. Temporary mitigation does not close the case automatically. Resolve contradictory inventory and scan results rather than choosing the more reassuring result; reassess when exposure or exploitation evidence changes.
Signal
Read the KEV entry and vendor advisory.
Exposure
Confirm product, installed version and reachable surface.
Action
Assign an owner, deadline and remediation evidence.
Can an old CVE remain a priority?
Yes, when an affected version remains present and exposed. Publication age does not establish that the patch is installed.
Try the reasoning
A severe CVE concerns a component missing from the inventory. What needs checking?
Reasoning: Actual presence, version, exposure and exploitation evidence. A severity score does not describe your environment.
A severe vulnerability does not match the installed product
Fictional teaching case, not a client investigation.
Which priority follows from actual applicability beyond the displayed score?
Observation, interpretation and limit
Observation
What it establishes
What remains unproven
An advisory describes a high-severity product vulnerability.
A documented weakness concerns that advisory’s scope.
The score does not confirm an affected version is used by the organisation.
Authorised inventory shows a related product with a different component.
A trading name alone does not establish applicability.
Inventory may be incomplete; component and version need confirmation.
The owner confirms another asset with an affected version and exposed function.
A relevant asset and its context are identified.
This does not prove exploitation occurred on that asset.
Conclusion to record
Prioritise verification and remediation of the actually applicable asset using the vendor advisory and context. Keep the first asset pending verification instead of declaring it affected without evidence.
What would change the conclusion?
Review after validating product, version, exposure, available measures and remediation outcome.
Check your reasoning
Do severity, exploitation likelihood and consequences for your asset answer the same question?
For each point, record what the material actually supports. “Supported” applies to the specific observation, not to the entire case. A contradiction needs explanation; missing material remains an open question.
Define the question
Record the source
Test the observation
State the limits
Entries stay in this page until you leave or reload it. Nothing is saved or submitted by this tool. Use neutral references instead of personal data or credentials.
How to write a useful conclusion
Editorial examples, not findings about your case
Material
Useful wording
Next check
One dated source
The consulted source stated X on the recorded date.
Check its origin and whether it still applies.
Multiple copies of one claim
Several pages repeat X; independent corroboration is missing.
Find the original and a source with independent evidence.
Conflicting sources
A states X while B states Y; the difference is unresolved.
Compare dates, scope, identifiers and definitions.
No matching result
No result was found in the recorded scope.
Describe queries, coverage and access limitations.
Common pitfalls
Four shortcuts that weaken the result.
Sorting only by CVSS
Technical severity is not complete business risk.
Confusing percentile and probability
Keep the EPSS fields separate.
Assuming a version
Confirm the installed product before concluding.
Closing without validation
Check every asset and temporary control.
Practical questions
Frequently asked questions.
Does a CVSS score of 9 determine priority?
It indicates high severity within the vector conditions. Applicability, exploitation, exposure and consequences also need assessment.
Is absence from KEV reassuring?
It means the CVE was not in the consulted catalog. It does not establish absence of exploitation.
Must exploitation be tested before deciding?
Not necessarily. Vendor advisories and an authorised inventory often support a decision; technical testing requires an appropriate scope and permission.
Public references
These primary references support the checks described here. The sequence and working sheet are an IIS editorial method; a cited organisation does not endorse this guide. Read each reference within its stated date, jurisdiction and scope.
CISA — KEV. Vulnérabilités exploitées / Known exploited vulnerabilities.
FIRST — EPSS. Probabilité sur trente jours et percentile / Thirty-day probability and percentile.
Red Hat — Backporting. Reference for the technical fields and interpretation boundaries described in this guide.
Editorial scope
Published by Internet Intelligence Service on 6 October 2026. Last content update: 29 October 2026. This educational guide describes a lawful, defensive method. It is not legal advice, an emergency service or authority instruction.