Security Deep Dive
Mailu
Security posture and CVE patch evidence from tracked releases.
10 critical dependency CVEs affects 2024.06.52.
Audit transitive dependencies; consider upgrading or pinning replacements.
— Signed
— SLSA
— SBOM
✓ Security policy
Monthly cadence · 19d 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: 22d ago
Release cadence: monthly
Present
19d median over recent releases
Release history
Latest release: 6d ago
Maintainer active
Present
Recent commit activity
Repository
Last commit: 3d 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.0/10
Security Score
5.5/10
Scorecard
Dependency Exposure
123 transitive dependency
CVEs found in the latest SBOM.
10 critical.
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
3d stale
scorecard
2.20 / 4.0
Score 5.5/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 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
direct cves: clear
cve scan: available
Release responsiveness
release responsiveness
10.0
5%
patch speed days: no_history
Dependency exposure
dependency exposure
0.0
10%
supply chain risk: 100.0
transitive cves: 10c/35h
Provenance trust
provenance trust
5.5
40%
scorecard score: 5.5
openssf badge: none
Maintainer health
maintainer health
10.0
10%
activity freshness: 3d
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 100.0/100
10
Transitive critical CVEs
0
KEV-transitive CVEs
64%
Dependency freshness
Scorecard
Scorecard 5.5/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 23 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 10 | all changesets reviewed |
| Security-Policy | 3 | security policy file detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| License | 9 | license file detected |
| Packaging | -1 | packaging workflow not 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 | 10 | no dangerous workflow patterns detected |
| Signed-Releases | -1 | no releases found |
| Fuzzing | 0 | project is not fuzzed |
| Binary-Artifacts | 9 | binaries present in source code |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| 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
158 dependencies scanned
View full dependency list →
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
10
High
35
Medium
55
Low
22
Unknown
1
Critical
10
High
35
Medium
55
Low
22
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2012-0805 | critical | — | sqlalchemy | — | 2024.06.51 |
| CVE-2015-8557 | critical | — | pygments | — | 2024.06.51 |
| CVE-2015-8747 | critical | — | radicale | — | 2024.06.51 |
| CVE-2016-1505 | critical | — | radicale | — | 2024.06.51 |
| CVE-2017-18342 | critical | — | pyyaml | — | 2024.06.51 |
| CVE-2019-20477 | critical | — | pyyaml | — | 2024.06.51 |
| CVE-2019-7164 | critical | — | sqlalchemy | — | 2024.06.51 |
| CVE-2019-7548 | critical | — | sqlalchemy | — | 2024.06.51 |
| CVE-2020-14343 | critical | — | pyyaml | — | 2024.06.51 |
| CVE-2020-1747 | critical | — | pyyaml | — | 2024.06.51 |
| CVE-2014-1402 | high | — | jinja2 | — | 2024.06.51 |
| CVE-2016-10745 | high | — | jinja2 | — | 2024.06.51 |
| CVE-2017-8342 | high | — | radicale | — | 2024.06.51 |
| CVE-2018-1000164 | high | — | gunicorn | — | 2024.06.51 |
| CVE-2018-1000656 | high | — | flask | — | 2024.06.51 |
| CVE-2018-18074 | high | — | requests | — | 2024.06.51 |
| CVE-2019-1010083 | high | — | flask | — | 2024.06.51 |
| CVE-2019-10906 | high | — | jinja2 | — | 2024.06.51 |
| CVE-2019-14322 | high | — | werkzeug | — | 2024.06.51 |
| CVE-2019-14806 | high | — | werkzeug | — | 2024.06.51 |
| CVE-2019-16791 | high | — | postfix-mta-sts-resolver | — | 2024.06.51 |
| CVE-2019-19588 | high | — | validators | — | 2024.06.51 |
| CVE-2019-2435 | high | — | mysql-connector-python | — | 2024.06.51 |
| CVE-2021-20270 | high | — | pygments | — | 2024.06.51 |
| CVE-2021-27291 | high | — | pygments | — | 2024.06.51 |
| CVE-2021-32838 | high | — | flask-restx | — | 2024.06.51 |
| CVE-2021-42771 | high | — | babel | — | 2024.06.51 |
| CVE-2023-25577 | high | — | werkzeug | — | 2024.06.51 |
| CVE-2023-28859 | high | — | redis | — | 2024.06.51 |
| CVE-2023-30861 | high | — | flask | — | 2024.06.51 |
| CVE-2024-1135 | high | — | gunicorn | — | 2024.06.51 |
| CVE-2024-21272 | high | — | mysql-connector-python | 8.4.0 | 2024.06.51 |
| CVE-2024-23334 | high | — | aiohttp | — | 2024.06.51 |
| CVE-2024-30251 | high | — | aiohttp | — | 2024.06.51 |
| CVE-2024-34069 | high | — | werkzeug | — | 2024.06.51 |
| CVE-2024-6345 | high | — | setuptools | 69.5.1 | 2024.06.51 |
| CVE-2024-6827 | high | — | gunicorn | — | 2024.06.51 |
| CVE-2025-47273 | high | — | setuptools | 69.5.1 | 2024.06.51 |
| CVE-2025-66418 | high | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2025-66471 | high | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2025-69223 | high | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-21441 | high | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2026-24049 | high | — | wheel | 0.43.0 | 2024.06.51 |
| CVE-2026-26007 | high | — | cryptography | 42.0.6 | 2024.06.51 |
| CVE-2026-44307 | high | — | mako | 1.3.3 | 2024.06.51 |
| CVE-2014-0012 | medium | — | jinja2 | — | 2024.06.51 |
| CVE-2014-1829 | medium | — | requests | — | 2024.06.51 |
| CVE-2014-1830 | medium | — | requests | — | 2024.06.51 |
| CVE-2015-2296 | medium | — | requests | — | 2024.06.51 |
| CVE-2015-8748 | medium | — | radicale | — | 2024.06.51 |
| CVE-2016-10516 | medium | — | werkzeug | — | 2024.06.51 |
| CVE-2018-17175 | medium | — | marshmallow | — | 2024.06.51 |
| CVE-2020-28493 | medium | — | jinja2 | — | 2024.06.51 |
| CVE-2020-28724 | medium | — | werkzeug | — | 2024.06.51 |
| CVE-2022-40896 | medium | — | pygments | — | 2024.06.51 |
| CVE-2023-28858 | medium | — | redis | — | 2024.06.51 |
| CVE-2023-29483 | medium | — | dnspython | — | 2024.06.51 |
| CVE-2023-32681 | medium | — | requests | — | 2024.06.51 |
| CVE-2023-37276 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2023-46136 | medium | — | werkzeug | — | 2024.06.51 |
| CVE-2023-47627 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2023-49081 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2023-49082 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2024-22195 | medium | — | jinja2 | — | 2024.06.51 |
| CVE-2024-23829 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2024-27306 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2024-34064 | medium | — | jinja2 | — | 2024.06.51 |
| CVE-2024-35195 | medium | — | requests | 2.31.0 | 2024.06.51 |
| CVE-2024-3651 | medium | — | idna | — | 2024.06.51 |
| CVE-2024-37891 | medium | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2024-42367 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2024-47081 | medium | — | requests | 2.31.0 | 2024.06.51 |
| CVE-2024-49766 | medium | — | werkzeug | 3.0.3 | 2024.06.51 |
| CVE-2024-49767 | medium | — | werkzeug | 3.0.3 | 2024.06.51 |
| CVE-2024-52303 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2024-52304 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2024-56201 | medium | — | jinja2 | 3.1.4 | 2024.06.51 |
| CVE-2024-56326 | medium | — | jinja2 | 3.1.4 | 2024.06.51 |
| CVE-2025-27516 | medium | — | jinja2 | 3.1.4 | 2024.06.51 |
| CVE-2025-48945 | medium | — | pycares | 4.4.0 | 2024.06.51 |
| CVE-2025-50181 | medium | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2025-50182 | medium | — | urllib3 | 2.2.1 | 2024.06.51 |
| CVE-2025-66221 | medium | — | werkzeug | 3.0.3 | 2024.06.51 |
| CVE-2025-68480 | medium | — | marshmallow | 3.21.2 | 2024.06.51 |
| CVE-2025-69227 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69228 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69229 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-8869 | medium | — | pip | 24.0 | 2024.06.51 |
| CVE-2026-21860 | medium | — | werkzeug | 3.0.3 | 2024.06.51 |
| CVE-2026-22815 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-25645 | medium | — | requests | 2.31.0 | 2024.06.51 |
| CVE-2026-27199 | medium | — | werkzeug | 3.0.3 | 2024.06.51 |
| CVE-2026-3219 | medium | — | pip | 24.0 | 2024.06.51 |
| CVE-2026-34515 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34516 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34525 | medium | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-41205 | medium | — | mako | 1.3.3 | 2024.06.51 |
| CVE-2026-6357 | medium | — | pip | 24.0 | 2024.06.51 |
| GHSA-h4gh-qq45-vh27 | medium | — | cryptography | 42.0.6 | 2024.06.51 |
| GHSA-pjjw-qhg8-p2p9 | medium | — | aiohttp | — | 2024.06.51 |
| CVE-2017-3590 | low | — | mysql-connector-python | — | 2024.06.51 |
| CVE-2021-21330 | low | — | aiohttp | — | 2024.06.51 |
| CVE-2023-23934 | low | — | werkzeug | — | 2024.06.51 |
| CVE-2023-47641 | low | — | aiohttp | — | 2024.06.51 |
| CVE-2024-12797 | low | — | cryptography | 42.0.6 | 2024.06.51 |
| CVE-2024-39689 | low | — | certifi | 2024.2.2 | 2024.06.51 |
| CVE-2025-47278 | low | — | flask | — | 2024.06.51 |
| CVE-2025-53643 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69224 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69225 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69226 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2025-69230 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-1703 | low | — | pip | 24.0 | 2024.06.51 |
| CVE-2026-27205 | low | — | flask | 3.0.3 | 2024.06.51 |
| CVE-2026-34073 | low | — | cryptography | 42.0.6 | 2024.06.51 |
| CVE-2026-34513 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34514 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34517 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34518 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34519 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-34520 | low | — | aiohttp | 3.9.5 | 2024.06.51 |
| CVE-2026-4539 | low | — | pygments | 2.18.0 | 2024.06.51 |
| CVE-2022-29361 | unknown | — | werkzeug | — | 2024.06.51 |
Showing 123 of 123