Tools / Docker Compose / Security

Security Deep Dive

Docker Compose

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v5.1.4.

Audit transitive dependencies; consider upgrading or pinning replacements.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

6 versions tracked

Version	Published	C	H	M	L	KEV	Notes
v5.1.4	2026-05-20	—	—	—	—	—	Latest
v5.1.3	2026-04-15	—	—	—	—	—	—
v5.1.2	2026-04-09	—	—	—	—	—	—
v5.1.1	2026-03-20	—	—	—	—	—	—
v5.1.0	2026-02-24	—	—	—	—	—	Patches GO-2026-4610
v5.0.2	2026-01-21	—	—	—	—	—	—

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 23d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 21d ago

Release cadence: monthly Present

23d median over recent releases Release history

Latest release: 14d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 14d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 14d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 14d ago

4.6/10 Security Score

7.2/10 Scorecard

0d avg CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

Patch speed: 0d

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

1d stale

scorecard

2.88 / 4.0

Score 7.2/10

cve health

0.00 / 2.5

Open CVEs detected

patch speed

0.50 / 0.5

0d avg

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 54.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: 0

Dependency exposure

dependency exposure

4.6

10%

supply chain risk: 54.05 transitive cves: 4c/19h

Provenance trust

provenance trust

7.2

40%

scorecard score: 7.2 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 54.0/100

2 Transitive critical CVEs

0 KEV-transitive CVEs

98% Dependency freshness

Scorecard

Scorecard 7.2/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Code-Review	10	all changesets reviewed
Dependency-Update-Tool	10	update tool detected
Packaging	-1	packaging workflow not detected
Token-Permissions	9	detected GitHub workflow tokens with excessive permissions
Maintained	10	30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
Security-Policy	10	security policy file detected
Binary-Artifacts	10	no binaries found in the repo
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
License	10	license file detected
Vulnerabilities	0	28 existing vulnerabilities detected
Signed-Releases	8	5 out of the last 5 releases have a total of 5 signed artifacts.
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration
Fuzzing	0	project is not fuzzed
SAST	1	SAST tool is not run on all commits -- score normalized to 1
CI-Tests	10	18 out of 18 merged PRs checked by a CI test -- score normalized to 10
Contributors	10	project has 45 contributing companies or organizations
Pinned-Dependencies	2	dependency not pinned by hash detected -- score normalized to 2

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

CVE Patch History

Median patch time: 0 days

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low

2026

CVE	Severity	EPSS	Disclosed	Fixed in	Days to fix	vs Ecosystem Median	KEV
GO-2026-4610	unknown	—	—	v5.1.0	—	—	—

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

229 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (39) All (56)

Critical 2 High 15 Medium 15 Low 4 Unknown 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2022-24439	critical	—	gitpython	3.1.11	v5.1.4
CVE-2023-40267	critical	—	gitpython	3.1.11	v5.1.4
CVE-2023-0286	high	—	cryptography	3.3.2	v5.1.4
CVE-2023-40590	high	—	gitpython	3.1.11	v5.1.4
CVE-2023-43804	high	—	urllib3	1.26.5	v5.1.4
CVE-2023-49797	high	—	pyinstaller	4.1	v5.1.4
CVE-2023-50782	high	—	cryptography	3.3.2	v5.1.4
CVE-2024-22190	high	—	gitpython	3.1.11	v5.1.4
CVE-2025-59042	high	—	pyinstaller	4.1	v5.1.4
CVE-2025-66418	high	—	urllib3	1.26.5	v5.1.4
CVE-2025-66471	high	—	urllib3	1.26.5	v5.1.4
CVE-2026-21441	high	—	urllib3	1.26.5	v5.1.4
CVE-2026-26007	high	—	cryptography	3.3.2	v5.1.4
CVE-2026-39883	high	—	go.opentelemetry.io/otel/sdk	v1.42.0	v5.1.4
CVE-2026-42284	high	—	gitpython	3.1.11	v5.1.4
CVE-2026-44243	high	—	gitpython	3.1.11	v5.1.4
CVE-2026-44244	high	—	gitpython	3.1.11	v5.1.4
CVE-2023-23931	medium	—	cryptography	3.3.2	v5.1.4
CVE-2023-32681	medium	—	requests	2.25.1	v5.1.4
CVE-2023-41040	medium	—	gitpython	3.1.11	v5.1.4
CVE-2023-45803	medium	—	urllib3	1.26.5	v5.1.4
CVE-2023-48795	medium	—	paramiko	2.7.2	v5.1.4
CVE-2023-49083	medium	—	cryptography	3.3.2	v5.1.4
CVE-2024-0727	medium	—	cryptography	3.3.2	v5.1.4
CVE-2024-3651	medium	—	idna	2.10	v5.1.4
CVE-2024-37891	medium	—	urllib3	1.26.5	v5.1.4
CVE-2025-50181	medium	—	urllib3	1.26.5	v5.1.4
CVE-2025-68146	medium	—	filelock	3.0.12	v5.1.4
CVE-2025-69277	medium	—	pynacl	1.4.0	v5.1.4
CVE-2026-22701	medium	—	filelock	3.0.12	v5.1.4
CVE-2026-39882	medium	—	go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp	v1.42.0	v5.1.4
CVE-2026-39882	medium	—	go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp	v1.42.0	v5.1.4
CVE-2026-34073	low	—	cryptography	3.3.2	v5.1.4
GHSA-5cpq-8wj7-hf2v	low	—	cryptography	3.3.2	v5.1.4
GHSA-jm77-qphf-c4w8	low	—	cryptography	3.3.2	v5.1.4
GHSA-v8gr-m533-ghj9	low	—	cryptography	3.3.2	v5.1.4
CVE-2022-24302	unknown	—	paramiko	2.7.2	v5.1.4
CVE-2022-42969	unknown	—	py	1.10.0	v5.1.4
CVE-2026-33814	unknown	—	golang.org/x/net	v0.51.0	v5.1.4

Showing 39 of 56