Security Deep Dive
wazuh
Security posture and CVE patch evidence from tracked releases.
6 high-severity dependency CVEs affects v4.14.5.
Review the dependency vulnerabilities below.
Trust Signals — 4 of 9 Present
Evidence already collected from releases and repository metadata.
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
6d stale
scorecard
2.68 / 4.0
Score 6.7/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 v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
4.5
10%
Provenance trust
provenance trust
6.7
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
10%
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/100Scorecard
Scorecard 6.7/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 9 | Found 11/12 approved changesets -- score normalized to 9 |
| Maintained | 10 | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Security-Policy | 10 | security policy file detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| License | 9 | license file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Signed-Releases | -1 | no releases found |
| 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 |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 7 | binaries present in source code |
| 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
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
0
High
6
Medium
15
Low
11
Unknown
2
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2023-52323 | high | — | pycryptodome | 3.19.0 | — |
| CVE-2025-69223 | high | — | aiohttp | 3.13.2 | — |
| CVE-2026-26007 | high | — | cryptography | 44.0.1 | — |
| CVE-2026-30922 | high | — | pyasn1 | 0.4.8 | — |
| CVE-2026-32597 | high | — | pyjwt | 2.10.1 | — |
| CVE-2026-42561 | high | — | python-multipart | 0.0.22 | — |
| CVE-2024-35195 | medium | — | requests | 2.31.0 | — |
| CVE-2024-47081 | medium | — | requests | 2.32.3 | — |
| CVE-2025-69227 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2025-69228 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2025-69229 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2025-71176 | medium | — | pytest | 7.3.1 | — |
| CVE-2026-22815 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2026-25645 | medium | — | requests | 2.32.4 | — |
| CVE-2026-27199 | medium | — | werkzeug | 3.1.5 | — |
| CVE-2026-3219 | medium | — | pip | 26.0 | — |
| CVE-2026-34515 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2026-34516 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2026-34525 | medium | — | aiohttp | 3.13.2 | — |
| CVE-2026-40347 | medium | — | python-multipart | 0.0.22 | — |
| CVE-2026-6357 | medium | — | pip | 26.0 | — |
| CVE-2025-69224 | low | — | aiohttp | 3.13.2 | — |
| CVE-2025-69225 | low | — | aiohttp | 3.13.2 | — |
| CVE-2025-69226 | low | — | aiohttp | 3.13.2 | — |
| CVE-2025-69230 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34073 | low | — | cryptography | 44.0.1 | — |
| CVE-2026-34513 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34514 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34517 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34518 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34519 | low | — | aiohttp | 3.13.2 | — |
| CVE-2026-34520 | low | — | aiohttp | 3.13.2 | — |
| CVE-2022-42969 | unknown | — | py | 1.11.0 | — |
| CVE-2024-52338 | unknown | — | pyarrow | 14.0.1 | — |
Showing 34 of 54