Tools / Beats / Security

Security Deep Dive

Beats

Security posture and CVE patch evidence from tracked releases.

Back to Tool

14 high-severity dependency CVEs affects v9.4.2.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 0d 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: weekly Present

0d median over recent releases Release history

Latest release: 6d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 6d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 6d ago

Signing assets Not active yet

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

Latest release: 6d ago

4.6/10 Security Score

7.1/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

2.84 / 4.0

Score 7.1/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 34.1/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

6.6

10%

supply chain risk: 34.06 transitive cves: 0c/17h

Provenance trust

provenance trust

7.1

40%

scorecard score: 7.1 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 34.1/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

97% Dependency freshness

Scorecard

Scorecard 7.1/10

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

Check	Score	Reason
Maintained	10	30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Packaging	-1	packaging workflow not detected
Code-Review	10	all changesets reviewed
Dangerous-Workflow	10	no dangerous workflow patterns detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
License	9	license file detected
Fuzzing	10	project is fuzzed
Branch-Protection	5	branch protection is not maximal on development and all release branches
Signed-Releases	-1	no releases found
Security-Policy	10	security policy file detected
Binary-Artifacts	9	binaries present in source code
Pinned-Dependencies	-1	internal error: internal error: invalid Dockerfile: Syntax error - can't find = in "$beatHome". Must be of the form: name=value
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

693 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 (25) All (36)

High 14 Medium 9 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2021-38561	high	—	golang.org/x/text	v0.3.1-0.20180807135948-17ff2d5776d2	v9.4.1
CVE-2022-32149	high	—	golang.org/x/text	v0.3.1-0.20180807135948-17ff2d5776d2	v9.4.1
CVE-2024-25621	high	—	github.com/containerd/containerd/v2	v2.1.0	v9.4.1
CVE-2025-4565	high	—	protobuf	3.19.5	v9.4.1
CVE-2025-47290	high	—	github.com/containerd/containerd/v2	v2.1.0	v9.4.1
CVE-2025-66418	high	—	urllib3	1.26.19	v9.4.1
CVE-2025-66471	high	—	urllib3	1.26.19	v9.4.1
CVE-2026-0994	high	—	protobuf	3.19.5	v9.4.1
CVE-2026-21441	high	—	urllib3	2.6.0	v9.4.1
CVE-2026-30922	high	—	pyasn1	0.4.8	v9.4.1
CVE-2026-35469	high	—	github.com/moby/spdystream	v0.5.0	v9.4.1
CVE-2026-41602	high	—	github.com/apache/thrift	v0.22.0	v9.4.1
CVE-2026-42151	high	—	github.com/prometheus/prometheus	v0.311.2-0.20260410083055-07c6232d159b	v9.4.1
CVE-2026-42154	high	—	github.com/prometheus/prometheus	v0.311.2-0.20260410083055-07c6232d159b	v9.4.1
CVE-2020-14040	medium	—	golang.org/x/text	v0.3.1-0.20180807135948-17ff2d5776d2	v9.4.1
CVE-2025-50181	medium	—	urllib3	1.26.19	v9.4.1
CVE-2025-64329	medium	—	github.com/containerd/containerd/v2	v2.1.0	v9.4.1
CVE-2025-69277	medium	—	pynacl	1.5.0	v9.4.1
CVE-2025-71176	medium	—	pytest	7.3.2	v9.4.1
CVE-2026-25645	medium	—	requests	2.32.4	v9.4.1
CVE-2026-28684	medium	—	python-dotenv	0.21.1	v9.4.1
GHSA-747p-wmpv-9c78	medium	—	awscli	1.18.48	v9.4.1
GHSA-fw8g-cg8f-9j28	medium	—	github.com/prometheus/prometheus	v0.311.2-0.20260410083055-07c6232d159b	v9.4.1
CVE-2022-42969	unknown	—	py	1.11.0	v9.4.1
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	v9.4.1

Showing 25 of 36