Code Not Present means the vulnerable code is not included in the product or component being assessed. In VEX usage, it indicates that a reported vulnerability cannot apply to that specific package, image or build because the code path is absent, which helps separate real exposure from inherited or irrelevant findings.
What Code Not Present Means in VEX
Code Not Present is a VEX status used to say the vulnerable code path is absent from the assessed product, image, or build. That matters because it separates inherited or theoretical findings from exposure that actually exists in the artefact being shipped or deployed.
In practice, this status is a claim about applicability, not about whether a vulnerability exists in the wider ecosystem. It helps security teams avoid treating every reported issue as actionable on every component, especially where shared dependencies, optional features, or multi-variant builds create false positives.
Why “Not Present” Changes Exposure Assessment
The main security value of Code Not Present is precision. If the vulnerable function, library, or code path is not included, the package cannot be exploited through that route, even if the upstream project or a related component has a known issue. That makes applicability triage faster and more defensible.
This also changes how teams interpret SBOM and scanner output. A finding should be tied to the exact artefact and build context, not assumed to apply because a vulnerable component name appears somewhere in the supply chain. For that reason, teams should verify the assessed package or image against build contents, dependency manifests, and vendor guidance before escalating.
How Teams Verify Applicability
Verification is usually an evidence exercise. Teams compare the vulnerability report with the exact package version, image digest, feature set, and build composition to determine whether the affected code path is actually included. When the answer is “not present”, the key question becomes whether the artefact is truly equivalent to the one described by the advisory.
Authoritative sources matter here. Vendor advisories explain the affected code path, while the CISA Known Exploited Vulnerabilities catalogue helps confirm whether the issue is being actively exploited and should therefore receive higher priority if applicability is uncertain. For control expectations around inventory, configuration, and validation of software exposure, see NIST SP 800-53 Rev 5 Security and Privacy Controls and SLSA.
What It Means for Remediation and Monitoring
When code is not present, remediation usually shifts away from emergency patching and toward maintaining proof of applicability. That may include preserving build evidence, documenting the exact variant assessed, and ensuring future rebuilds do not reintroduce the vulnerable path through a dependency change or feature toggle.
Even when patching is not required for the current artefact, teams should keep watching for new builds, repackaging, or transitive dependency drift that could change the applicability conclusion. The safest assumption is that “not present” is version- and build-specific, not permanent.
For broader vulnerability management and exposure reduction workflows, the NIST Cybersecurity Framework 2.0 and OWASP API Security Top 10 are useful companions when the finding involves software supply paths or exposed application interfaces.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and SLSA set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | RA-5 — Vulnerability Monitoring and Scanning | Applies to validating whether a reported weakness is truly present in the assessed artefact. |
| Recommendation — Verify exposure against the exact build and record why the vulnerability does or does not apply. | ||
| CIS Controls v8 | CIS-7 — Continuous Vulnerability Management | Applies because applicability judgments depend on ongoing identification and tracking of software exposure. |
| Recommendation — Track findings against the exact package or image and maintain evidence for applicability decisions. | ||
| SLSA | Supply-chain Levels for Software Artifacts | Applies because build provenance helps prove which code was actually included in the artefact. |
| Recommendation — Preserve build provenance so you can confirm whether vulnerable code entered the shipped artefact. | ||
Related resources from NHI Mgmt Group
- What breaks when a Linux host allows local code execution and an exploitable kernel privilege bug is present?
- What happens when a revoked code signing certificate is still present on installed software?
- Why is hardcoding credentials into source code so dangerous?
- What is the difference between code scanning and runtime identity monitoring?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org