Vulnerability Reporthashicorp/vault:2.2.1

hashicorp/vault:latesthashicorp/vault:2.2hashicorp/vault:2.2.1

digestsha256:962a92876e168d68eaaa24b0b8b49bbce1cb63024060a67bba95cd158a366fc2

Executive Summary

Last scanned: Oct 26, 2026

Threat ScoreSAFE• Threat score is 0, which falls in the SAFE band (0-24).• Vulnerability stats show exposed_total 0, post_total 0, and max severity 0.0.• No CVE IDs appear in the exposed-surface or post-exploit findings, so no CVE-specific risk is cited.• Trust checks show a VERIFIED/TRUSTED publisher with score 100 and digest pinning.• No exposed or post-exploit findings were provided for this image.

0/100SAFE

ReputationVERIFIED• Verified Publisher (Trusted Vendor)• Pinned by digest (Immutable)

TRUSTED

This image is safe for production use. The provided vulnerability stats show zero exposed and zero post-exploit findings, with maximum severity 0.0. The image is published by hashicorp, marked VERIFIED/TRUSTED with score 100, and pinned by digest. No CVE IDs are present in the supplied findings, so there are no vulnerability-specific mitigations to apply from these inputs.

Relevant for hashicorp/vault:2.2.1

Most CVEs in Go images aren't exploitable

This image is a Go binary — most findings can be ruled out with three commands. How to prove which ones are real.

Read the article

Vulnerabilities

Vulnerability Log

0 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
No vulnerabilities found matching filters.

Reachability analysis

Which CVEs are actually reachable — is the vulnerable code even linked and callable.

Locked

Runtime verification

Live-container probes: default user, writable paths, capabilities, exposed ports.

Locked

Supply chain analysis

Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.

Locked

Hardening recommendations

A step-by-step hardened build plan, with parity tests proving nothing breaks.

Locked

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