NetRise has released a new report that explores software compositions, vulnerability risks, and non-CVE risks in different asset classes in every organization’s software supply chain. The report analyzes the scope and scale of the components and risks found across 70 of the most commonly downloaded Docker Hub container images.
Key findings from NetRise researchers include:
- After analyzing 70 randomly selected container images from 250 of Docker Hub’s most commonly downloaded images and generating a detailed SBOM, NetRise discovered that each container image had an average of 389 software components.
- NetRise found that one in eight components had no software manifest—they lacked the formal metadata typically found in manifests and details about dependencies, version numbers, or the package’s source.
- The average container had 604 known vulnerabilities in the underlying software components, with over 45% being 2 to 10+ years old; over 4% of the 16,557 identified CVEs with a Critical or High CVSS Severity ranking were weaponized vulnerabilities known by botnets to spread ransomware, used by threat actors, or used in known attacks; 4.8 misconfigurations per container, including 146 “world writable and readable directories outside tmp,” the containers had overly permissive identity controls with an average of 19.5 usernames per container.
You can read the report here.


NetRise Introduces A Significant Platform Enhancement
Posted in Commentary with tags NetRise on August 5, 2025 by itnerdNetRise announced a significant update to its core product platform. This update makes users’ time more efficient and effective in prioritizing, mitigating, and remediating vulnerabilities found in the software they produce and reducing risk in the environments in which that software runs.
Key features introduced into the NetRise platform include:
In its Supply Chain Visibility & Risk Study, published in Q4 2024, NetRise reported that on networking devices whose compiled software NetRise analyzed, an average of 1,120 CVEs were found per device. The report showed how to prioritize those CVEs to focus on those that were network accessible, greatly reducing the work required of a manufacturer’s development team or of an enterprise’s third-party risk management team.
Resources
Leave a comment »