Tools / wazuh / Security

Security Deep Dive

wazuh

Security posture and CVE patch evidence from tracked releases.

Back to Tool

5 high-severity dependency CVEs affects v4.14.6.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✓ Security policy Monthly cadence · 35d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/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 Present

GitHub repository metadata Repository policy

Checked: 14d ago

Release cadence: monthly Present

35d median over recent releases Release history

Latest release: 24d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 8d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 24d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 24d ago

Signing assets Not active yet

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

Latest release: 24d ago

3.7/10 Security Score

4.8/10 Scorecard

Dependency Exposure 28 transitive dependency CVEs found in the latest SBOM.

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

1.92 / 4.0

Score 4.8/10

cve health

0.00 / 2.5

No open CVEs

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

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

4.5

10%

supply chain risk: 54.61 transitive cves: 6c/15h

Provenance trust

provenance trust

4.8

40%

scorecard score: 4.8 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.6/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

70% Dependency freshness

Scorecard

Scorecard 4.8/10

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

Check	Score	Reason
Security-Policy	10	security policy file detected
Code-Review	5	Found 7/13 approved changesets -- score normalized to 5
Maintained	10	30 commit(s) and 25 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
License	9	license file detected
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Dangerous-Workflow	0	dangerous workflow patterns detected
Signed-Releases	-1	no releases found
Binary-Artifacts	7	binaries present in source code
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Fuzzing	10	project is fuzzed
Packaging	10	packaging workflow detected
SAST	0	SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

283 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 (28) All (54)

High 5 Medium 12 Low 10 Unknown 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2023-52323	high	—	pycryptodome	3.19.0	v4.14.6
CVE-2025-69223	high	—	aiohttp	3.13.2	v4.14.6
CVE-2026-30922	high	—	pyasn1	0.4.8	v4.14.6
CVE-2026-32597	high	—	pyjwt	2.10.1	v4.14.6
CVE-2026-42561	high	—	python-multipart	0.0.22	v4.14.6
CVE-2024-35195	medium	—	requests	2.31.0	v4.14.6
CVE-2024-47081	medium	—	requests	2.32.3	v4.14.6
CVE-2025-69227	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2025-69228	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2025-69229	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2026-22815	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2026-25645	medium	—	requests	2.32.4	v4.14.6
CVE-2026-27199	medium	—	werkzeug	3.1.5	v4.14.6
CVE-2026-34515	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34516	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34525	medium	—	aiohttp	3.13.2	v4.14.6
CVE-2026-40347	medium	—	python-multipart	0.0.22	v4.14.6
CVE-2025-69224	low	—	aiohttp	3.13.2	v4.14.6
CVE-2025-69225	low	—	aiohttp	3.13.2	v4.14.6
CVE-2025-69226	low	—	aiohttp	3.13.2	v4.14.6
CVE-2025-69230	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34513	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34514	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34517	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34518	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34519	low	—	aiohttp	3.13.2	v4.14.6
CVE-2026-34520	low	—	aiohttp	3.13.2	v4.14.6
CVE-2022-42969	unknown	—	py	1.11.0	v4.14.6

Showing 28 of 54