Tools / Consul / Security

Security Deep Dive

Consul

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 critical dependency CVEs affects v2.0.0.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 27d 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: 22d ago

Release cadence: monthly Present

27d median over recent releases Release history

Latest release: 10d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 10d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 10d ago

Signing assets Not active yet

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

Latest release: 10d ago

4.8/10 Security Score

7.5/10 Scorecard

Pending CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

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

Up to date

scorecard

3.00 / 4.0

Score 7.5/10

cve health

0.00 / 2.5

Open CVEs detected

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 26.6/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: no_history

Dependency exposure

dependency exposure

7.3

10%

supply chain risk: 26.59 transitive cves: 2c/9h

Provenance trust

provenance trust

7.5

40%

scorecard score: 7.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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 26.6/100

2 Transitive critical CVEs

0 KEV-transitive CVEs

70% Dependency freshness

Scorecard

Scorecard 7.5/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
Maintained	10	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
License	9	license file detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Signed-Releases	-1	no releases found
Branch-Protection	8	branch protection is not maximal on development and all release branches
Security-Policy	10	security policy file detected
Binary-Artifacts	9	binaries present in source code
Packaging	10	packaging workflow detected
Fuzzing	10	project is fuzzed
Pinned-Dependencies	6	dependency not pinned by hash detected -- score normalized to 6
SAST	0	SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

2572 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 (12) All (26)

Critical 2 High 9 Medium 10 Low 3 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2023-28154	critical	—	webpack	5.74.0	v2.0.0
CVE-2024-41110	critical	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
CVE-2024-21626	high	—	github.com/opencontainers/runc	v1.1.8	v2.0.0
CVE-2024-25621	high	—	github.com/containerd/containerd	v1.7.3	v2.0.0
CVE-2025-31133	high	—	github.com/opencontainers/runc	v1.1.8	v2.0.0
CVE-2025-52565	high	—	github.com/opencontainers/runc	v1.1.8	v2.0.0
CVE-2025-52881	high	—	github.com/opencontainers/runc	v1.1.8	v2.0.0
CVE-2026-34040	high	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
CVE-2026-44728	high	—	@babel/plugin-transform-modules-systemjs	7.24.7	v2.0.0
CVE-2026-6321	high	—	fast-uri	3.1.0	v2.0.0
CVE-2026-6322	high	—	fast-uri	3.1.0	v2.0.0
CVE-2022-29526	medium	—	golang.org/x/sys	0.0.0-20200124204421-9fbb57f87de9	v2.0.0
CVE-2024-24557	medium	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
CVE-2024-40635	medium	—	github.com/containerd/containerd	v1.7.3	v2.0.0
CVE-2024-43788	medium	—	webpack	5.74.0	v2.0.0
CVE-2024-45310	medium	—	github.com/opencontainers/runc	v1.1.8	v2.0.0
CVE-2025-13466	medium	—	body-parser	2.2.0	v2.0.0
CVE-2025-64329	medium	—	github.com/containerd/containerd	v1.7.3	v2.0.0
CVE-2026-33997	medium	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
GHSA-7ww5-4wqc-m92c	medium	—	github.com/containerd/containerd	v1.7.3	v2.0.0
GHSA-jq35-85cj-fj4p	medium	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
CVE-2025-54410	low	—	github.com/docker/docker	v24.0.5+incompatible	v2.0.0
CVE-2025-68157	low	—	webpack	5.74.0	v2.0.0
CVE-2025-68458	low	—	webpack	5.74.0	v2.0.0
CVE-2026-33814	unknown	—	golang.org/x/net	v0.51.0	v2.0.0
GO-2023-2412	unknown	—	github.com/containerd/containerd	v1.7.3	v2.0.0

Showing 26 of 26