Vulnerability Reportnats:2

nats:latestnats:2.15.1nats:2.15nats:2
digestsha256:023a08c46caa5aff878fb86841187bebfdad9a6e3c552ba5c1a1e18938bbf88a

Executive Summary

Last scanned:

Threat Score
0/100SAFE
Reputation
TRUSTED

This image is safe for production use. INPUT 3 reports 1 exposed finding and 1 post-exploit-only finding, but none reach the severity thresholds that would raise concern: exposed max severity is 0.0 and post-exploit max severity is 2.45, with no findings at 6.0 or above. The image is an official Docker Hub image pinned by digest, and the pre-calculated threat score is 0, placing it in the SAFE band. No CVE IDs were provided in INPUT 4 or INPUT 5, so there is no specific CVE-based risk to cite from these inputs.

Already in good shape · 2 hardening steps left

Included in Pro

Scanning procedure

  1. Vulnerability scan
    Full CVE sweep across OS packages and app dependencies
  2. Exploitability check
    CVEs ranked by exploit probability (EPSS) and matched against CISA KEV
  3. Reachability analysis
    Symbol-level proof: is the vulnerable code even linked and callable in your binaries?
  4. Runtime verification
    Live-container probes: exposed endpoints, feature flags, real defaults
  5. Supply chain analysis
    Base-image lineage, package provenance and signatures — nothing slipped in unnoticed
  6. Hardening recommendations
    A hardened build plan — patch, remove unused packages, lock down the runtime — with parity tests proving nothing broke

Vulnerabilities

Vulnerability Log

2 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-111943LOW2.45
stdlib
v1.27.2
fixed in 1.26.10, 1.27.3
—
Post-Exploit
GO-2026-5932NONE0
golang.org/x/crypto
v0.57.0
No fix yet
—
Not Applicable

Want to check another image? Run a full scan with the Docker Security Scanner.