Vulnerability Reportbrunoazuma/datasp:v1.10.0

brunoazuma/datasp:latestbrunoazuma/datasp:v1.10.0

digestsha256:f1f17b4cdeb9aee66ff38f1eafc3c644d564e0c17f582175172b8aa2b495f4e1

Executive Summary

Last scanned: Oct 23, 2026

Threat ScoreSAFE• Pre-calculated threat score is 5, which falls in the SAFE band (0-24).• Vulnerability stats show exposed_total 3 and post_total 2, but exposed_max_severity is 0.0 and post_max_severity is 2.51.• Both exposed_count_ge6 and post_count_ge6 are 0, so no severity 6.0+ findings drive risk in the provided data.• No CVE IDs appear in the exposed-surface or post-exploit-only finding lists, so there are no specific CVE mitigations to apply from this report.• Trust signal is WARNING/COMMUNITY: unverified, not official, 0 stars, 556 pulls; the image is pinned by digest, so use standard provenance checks.

5/100SAFE

ReputationCOMMUNITY• Community Image with low/unknown reputation• Very few downloads (<1k) - Use caution• Pinned by digest (Immutable)

UNVERIFIED

This image is safe for production use. The provided scan lists 3 exposed-surface entries and 2 post-exploit-only entries, but the exposed maximum severity is 0.0 and the post-exploit maximum severity is 2.51, with no counts at severity 6.0 or above. The main practical caveat is provenance rather than exploitability: it is an unverified community image with 556 pulls and a WARNING reputation, so standard supply-chain checks still apply. Because it is pinned by digest, the deployment is immutable, and no CVE IDs are available in the provided findings to require specific remediation.

Vulnerabilities

Vulnerability Log

10 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
CVE-2026-77214	LOW2.51	libexpat 2.8.5-r0 fixed in 2.9.0-r0	0.5% Theoretical Threat	Post-Exploit
CVE-2026-102633	LOW1.81	libexpat 2.8.5-r0 fixed in 2.9.0-r0	0.3% Theoretical Threat	Post-Exploit
CVE-2026-88806	NONE0	libx11 1.8.13-r0 fixed in 1.8.14-r0	0.2% Theoretical Threat	Not Applicable
CVE-2026-94283	NONE0	libx11 1.8.13-r0 fixed in 1.8.14-r0	0.2% Theoretical Threat	Not Applicable
CVE-2026-94284	NONE0	libx11 1.8.13-r0 fixed in 1.8.14-r0	0.1% Theoretical Threat	Not Applicable
CVE-2026-94287	NONE0	libxpm 3.5.19-r0 fixed in 3.5.20-r0	0.1% Theoretical Threat	Not Applicable
CVE-2026-94285	NONE0	libx11 1.8.13-r0 fixed in 1.8.14-r0	0.1% Theoretical Threat	Not Applicable
CVE-2026-107891	NONE0	musl 1.2.6-r2 fixed in 1.2.6-r3	—	Not Applicable
CVE-2026-107891	NONE0	musl-utils 1.2.6-r2 fixed in 1.2.6-r3	—	Not Applicable
CVE-2026-85091	NONE0	zlib 1.3.2-r0 fixed in 1.3.2-r1	0.4% Theoretical Threat	Not Applicable

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.