Security Deep Dive
profilarr
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v2.0.7.
Audit transitive dependencies; consider upgrading or pinning replacements.
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
3d stale
scorecard
2.00 / 4.0
⚠ Estimated — not yet collected
cve health
0.50 / 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 50.7/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
2.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
4.9
10%
Provenance trust
provenance trust
5.0
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 50.7/100OpenSSF 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
2
High
21
Medium
31
Low
14
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2022-24439 | critical | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2023-40267 | critical | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2023-25577 | high | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2023-30861 | high | — | flask | 2.0.1 | v2.0.0 |
| CVE-2023-40590 | high | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2024-1135 | high | — | gunicorn | 21.2.0 | v2.0.0 |
| CVE-2024-22190 | high | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2024-23334 | high | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-30251 | high | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-34069 | high | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2024-6221 | high | — | flask-cors | 3.0.10 | v2.0.0 |
| CVE-2024-6827 | high | — | gunicorn | 21.2.0 | v2.0.0 |
| CVE-2025-69223 | high | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-26996 | high | — | minimatch | 5.1.6 | v2.0.0 |
| CVE-2026-27903 | high | — | minimatch | 5.1.6 | v2.0.0 |
| CVE-2026-27904 | high | — | minimatch | 5.1.6 | v2.0.0 |
| CVE-2026-32763 | high | — | kysely | 0.27.6 | v2.0.0 |
| CVE-2026-33468 | high | — | kysely | 0.27.6 | v2.0.0 |
| CVE-2026-42284 | high | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2026-44243 | high | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2026-44244 | high | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2026-6321 | high | — | fast-uri | 3.1.0 | v2.0.0 |
| CVE-2026-6322 | high | — | fast-uri | 3.1.0 | v2.0.0 |
| CVE-2023-32681 | medium | — | requests | 2.26.0 | v2.0.0 |
| CVE-2023-41040 | medium | — | gitpython | 3.1.24 | v2.0.0 |
| CVE-2023-46136 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2023-47627 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2023-49081 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2023-49082 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-1681 | medium | — | flask-cors | 3.0.10 | v2.0.0 |
| CVE-2024-23829 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-27306 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-35195 | medium | — | requests | 2.31.0 | v2.0.0 |
| CVE-2024-47081 | medium | — | requests | 2.31.0 | v2.0.0 |
| CVE-2024-49766 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2024-49767 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2024-52304 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2024-6839 | medium | — | flask-cors | 3.0.10 | v2.0.0 |
| CVE-2024-6844 | medium | — | flask-cors | 3.0.10 | v2.0.0 |
| CVE-2024-6866 | medium | — | flask-cors | 3.0.10 | v2.0.0 |
| CVE-2025-64718 | medium | — | js-yaml | 4.1.0 | v2.0.0 |
| CVE-2025-66221 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2025-69227 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69228 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69229 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-21860 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2026-22815 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-25645 | medium | — | requests | 2.31.0 | v2.0.0 |
| CVE-2026-27199 | medium | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2026-33750 | medium | — | brace-expansion | 2.0.2 | v2.0.0 |
| CVE-2026-34515 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34516 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34525 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| GHSA-pjjw-qhg8-p2p9 | medium | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2023-23934 | low | — | werkzeug | 2.0.1 | v2.0.0 |
| CVE-2024-47764 | low | — | cookie | 0.6.0 | v2.0.0 |
| CVE-2025-53643 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69224 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69225 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69226 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2025-69230 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-27205 | low | — | flask | 2.0.1 | v2.0.0 |
| CVE-2026-34513 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34514 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34517 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34518 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34519 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2026-34520 | low | — | aiohttp | 3.8.5 | v2.0.0 |
| CVE-2022-29361 | unknown | — | werkzeug | 2.0.1 | v2.0.0 |
Showing 69 of 69