BlogPartners

NetRise’s New Execution-Aware Reachability

Our latest platform addition moves vulnerability analysis beyond traditional static detection with pseudo-runtime analysis—mapping which CVEs actually execute within your environment.

The Problem: Visibility Without Context

Traditional vulnerability management stops at enumeration. Scanners and SBOM tools can tell you what exists in your environment, but not what actually runs, or the privileges with which it runs. This blind spot means that millions of vulnerabilities appear critical on paper but never execute in practice or their underlying components do not execute with the required privileges to be exploited.

At scale, the result is noise. Visibility alone floods teams with false positives, redundant CVEs, and theoretical risk. Without execution context, defenders spend time triaging issues that can never be exploited.

Execution-Aware Reachability

Execution-Aware Reachability adds a new layer of intelligence. By correlating known vulnerabilities with confirmed execution paths, NetRise distinguishes between code that merely exists and code that actively runs within live systems.

In other words: it transforms theoretical exposure into measurable operational risk.

How It Works

When NetRise analyzes firmware, containers, or binaries, it performs multi-phase analysis:

  1. Autorun Detection – Identify system entry points, and other autorun/persistence mechanisms.
  2. Execution Path Reconstruction – Map execution across files, modules and code within asset filesystems.
  3. Vulnerability Correlation – Cross-reference reachable code with CVE and vulnerability information.
  4. Prioritization and Presentation – Flag reachable vulnerabilities and provide contextual evidence showing how they’re reachable.
NetRise CVE-2023-38408 detail panel showing 9.8 critical severity, OpenSSH component, and reachability evidence call chain

Quantifiable Impact

Since deployment, Execution-Aware Reachability has processed millions of vulnerabilities across production environments. The results speak for themselves:

MetricCountPercent Reduction
Initial CVEs5,100,000-
Post-Auto Remediation3,255,00036.2%
Reachable CVEs36,00099.29%

In one example, 30% of CVEs were confirmed as reachable within a specific asset – highlighting real exposure while eliminating 70% of noise.

Layered Prioritization in Action

Execution-Aware Reachability integrates directly with NetRise’s Kernel Vulnerability Auto-Remediation engine. The workflow looks like this:

  1. Visibility: Collect full software and firmware composition.
  2. Noise Reduction: Auto-remove false positives and redundant kernel CVEs.
  3. Execution Correlation: Confirm which vulnerabilities exist in active code and service paths.
  4. Action: Prioritize the 1% that matters.

In recent uploads of 40 new assets, NetRise identified 125,575 CVEs. Auto-remediation removed 48,445 non-actionable kernel findings. From the remainder, only 1.1% – 833 – were proven reachable.

Screenshot 2025-10-21 at 3.22.34 PM

Why It Matters

Attackers don’t exploit what’s installed — they exploit what runs. Execution-Aware Reachability gives defenders that same clarity, surfacing vulnerabilities in active execution paths and helping teams focus their resources where it counts.

Visibility without prioritization leads to fatigue. Prioritization without visibility creates blind spots. By combining the two, NetRise enables defenders to transition from reactive patching to proactive, evidence-based remediation.

The NetRise Perspective

At NetRise, our mission is to illuminate invisible risk within device software and firmware. Execution-Aware Reachability advances that mission by revealing which components and vulnerabilities actually execute.

Every connected device runs on complex layers of code — but only a fraction of that code ever runs. By focusing on the subset that executes, defenders gain:

  • Evidence-based prioritization of vulnerabilities
  • Quantifiable noise reduction (90%+)
  • Demonstrable due diligence for compliance and audit

Coming Next

Next in our Cybersecurity Awareness Month series, we’ll turn to the 2025 draft of the Software Bill of Materials (SBOM) Minimum Elements, and explore how evolving standards are shaping transparency, automation, and the next generation of software assurance.

Frequently Asked Questions

What is execution-aware reachability in vulnerability management?
Execution-aware reachability is the ability to determine which vulnerabilities are tied to code that actually executes within a live software or firmware environment. Instead of treating every detected CVE as equally urgent, it adds context about whether vulnerable components are part of real execution paths. This helps security teams separate theoretical exposure from operational risk. In practice, it means prioritizing vulnerabilities that are reachable in running systems rather than spending time on code that exists but never executes.
How does execution-aware reachability reduce vulnerability noise?
Execution-aware reachability reduces vulnerability noise by correlating known vulnerabilities with confirmed execution paths inside firmware, containers, and binaries. Traditional tools often generate large volumes of findings because they flag everything present in an environment, regardless of whether it can actually run. By identifying which vulnerable code paths are active and relevant, teams can eliminate large amounts of non-actionable risk. This improves triage efficiency, reduces alert fatigue, and helps defenders focus on the smaller subset of vulnerabilities that matter most.
Why is reachability analysis important for remediation prioritization?
Reachability analysis is important because attackers exploit code that runs, not just code that happens to be installed. Without execution context, security teams may waste time patching low-value findings while more meaningful exposure remains buried in the noise. By showing which vulnerabilities exist in active code and service paths, reachability analysis supports evidence-based remediation decisions. This allows teams to prioritize resources more effectively, improve response speed, and demonstrate a more defensible approach to vulnerability management, compliance, and audit readiness.