Security Deep Dive
zigbee2mqtt
Security posture and CVE patch evidence from tracked releases.
8 high-severity dependency CVEs affects 2.11.0.
Review the dependency vulnerabilities below.
Trust Signals — 2 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
1d stale
scorecard
1.52 / 4.0
Score 3.8/10
cve health
0.25 / 2.5
⚠ No direct scan — 0c/8h transitive 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 16.9/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
1.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
8.3
10%
Provenance trust
provenance trust
3.8
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 16.9/100Scorecard
Scorecard 3.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 1 | Found 3/23 approved changesets -- score normalized to 1 |
| Maintained | 10 | 30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10 |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Dangerous-Workflow | 0 | 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 |
| Security-Policy | 0 | security policy file not detected |
| License | 10 | license file detected |
| Fuzzing | 0 | project is not fuzzed |
| Signed-Releases | -1 | no releases found |
| Branch-Protection | 2 | branch protection is not maximal on development and all release branches |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| Packaging | 10 | packaging workflow detected |
| SAST | 9 | SAST tool is not run on all commits -- score normalized to 9 |
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
8
Medium
6
Low
2
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-26996 | high | — | minimatch | 9.0.5 | 2.10.1 |
| CVE-2026-27606 | high | — | rollup | 4.44.0 | 2.10.1 |
| CVE-2026-27903 | high | — | minimatch | 9.0.5 | 2.10.1 |
| CVE-2026-27904 | high | — | minimatch | 9.0.5 | 2.10.1 |
| CVE-2026-33671 | high | — | picomatch | 4.0.2 | 2.10.1 |
| CVE-2026-39363 | high | — | vite | 6.3.5 | 2.10.1 |
| CVE-2026-6321 | high | — | fast-uri | 3.1.0 | 2.10.1 |
| CVE-2026-6322 | high | — | fast-uri | 3.1.0 | 2.10.1 |
| CVE-2025-62522 | medium | — | vite | 6.3.5 | 2.10.1 |
| CVE-2026-33672 | medium | — | picomatch | 4.0.2 | 2.10.1 |
| CVE-2026-33750 | medium | — | brace-expansion | 5.0.2 | 2.10.1 |
| CVE-2026-39365 | medium | — | vite | 6.3.5 | 2.10.1 |
| CVE-2026-41305 | medium | — | postcss | 8.5.6 | 2.10.1 |
| CVE-2026-42338 | medium | — | ip-address | 10.1.0 | 2.10.1 |
| CVE-2025-58751 | low | — | vite | 6.3.5 | 2.10.1 |
| CVE-2025-58752 | low | — | vite | 6.3.5 | 2.10.1 |
Showing 16 of 16