Vulnerability Reportlitellm/litellm-database:v1.106.4

litellm/litellm-database:latestlitellm/litellm-database:main-stablelitellm/litellm-database:v1.106.4litellm/litellm-database:1.106.4

digestsha256:db36453d25e76c9eb689d7d51b8e5fa48843243d7a86ed1284cf574ce0107b3f

Executive Summary

Last scanned: Oct 27, 2026

Threat ScoreSAFE• Threat score is 3, which falls in the SAFE band (0 to 24).• Three exposed-surface findings exist, but the highest severity is 4.26, which is low and does not reach the threshold that would change the verdict.• No post-exploit-only findings were reported, and none of the exposed findings are listed as known exploited.• Trust status is WARNING with an UNVERIFIED verdict because this is a community image from the litellm publisher, so provenance should be reviewed as a routine check.• The container runs as root, which is a hardening gap to address over time even though it does not change this verdict.

3/100SAFE

ReputationCOMMUNITY• Community Image with low/unknown reputation• Pinned by digest (Immutable)

UNVERIFIED

This image is safe for production use. It has three low-severity exposed-surface findings, with the highest at 4.26, and none are known to be actively exploited, so they do not change the verdict. The image is a community build from an unverified publisher, so confirm its provenance as part of your normal review process. Running as root is worth tightening over time, but it does not block production use at this risk level.

Vulnerabilities

Vulnerability Log

3 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
CVE-2026-112940	MEDIUM4.26	filelock 3.32.7 fixed in 4.2.1	0.2% Theoretical Threat	Directly Exposed
CVE-2026-112913	LOW1.98	filelock 3.32.7 fixed in 4.2.1	—	Directly Exposed
CVE-2026-112907	LOW1.5	filelock 3.32.7 fixed in 4.2.1	—	Directly Exposed

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.