Features

Vulnerability scanning Vulnerabilities, in order of importance

scancontainer matches every component in a container image against public vulnerability sources and then answers the question that matters: which of these do I need to fix, and how.

What it finds

  • Whether the vulnerability affects the version you have, using the status published by each distribution
  • Whether it really applies: vulnerable function absent, never called, or disabled by configuration
  • Whether it can be reached from an entry point or from the network
  • Whether it is being exploited: CISA KEV, EPSS and public exploits
  • Backported patches, checked in the binary itself even when the version number says otherwise

What you get

  • A short, prioritised list with the reason for each position
  • A plan by package: what to update to remove the most risk with the fewest changes
  • The version that fixes each issue, or the base image change that removes it
  • CVSS 2.0, 3.0, 3.1 and 4.0 scores, plus CWE classification

What makes it different

A long list of CVEs is not a plan. Each vulnerability in the report says whether it applies and why, with the evidence, so you can leave out what does not affect you and defend that decision.

Which plan includes it

Simple report on free plans, full report on Skipper and above. Compare plans.

FAQ

Questions about this feature

Which vulnerability databases do you use?

More than 70 public sources, including OSV, NVD, the CVE List, GitHub Security Advisories, CISA and the security trackers of each Linux distribution.

What is the difference between CVSS, EPSS and KEV?

CVSS measures how severe a vulnerability is. EPSS estimates how likely it is to be exploited. KEV is the CISA list of vulnerabilities that are being exploited already.

More features

Scan yours before the next deploy.