Security Deep Dive
Zentral
Security posture and CVE patch evidence from tracked releases.
8 critical dependency CVEs affects v2026.2.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 3 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
4d stale
scorecard
3.24 / 4.0
Score 8.1/10
cve health
0.00 / 2.5
⚠ No direct scan — 8c/40h 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 100.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
0.0
10%
Provenance trust
provenance trust
8.1
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 100.0/100Scorecard
Scorecard 8.1/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Maintained | 10 | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| Token-Permissions | 9 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Security-Policy | 10 | security policy file detected |
| Code-Review | 10 | all changesets reviewed |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| License | 9 | license file detected |
| Signed-Releases | -1 | no releases found |
| Fuzzing | 0 | project is not fuzzed |
| Branch-Protection | 8 | branch protection is not maximal on development and all release branches |
| SAST | 10 | SAST tool is run on all commits |
| Packaging | 10 | packaging workflow detected |
| 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
8
High
40
Medium
34
Low
16
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2015-7337 | critical | — | ipython | — | — |
| CVE-2015-8557 | critical | — | pygments | — | — |
| CVE-2017-18342 | critical | — | pyyaml | — | — |
| CVE-2019-20477 | critical | — | pyyaml | — | — |
| CVE-2020-14343 | critical | — | pyyaml | — | — |
| CVE-2020-1747 | critical | — | pyyaml | — | — |
| CVE-2021-41945 | critical | — | httpx | — | — |
| CVE-2023-47248 | critical | — | pyarrow | — | — |
| CVE-2013-4314 | high | — | pyopenssl | — | — |
| CVE-2014-1402 | high | — | jinja2 | — | — |
| CVE-2014-3429 | high | — | ipython | — | — |
| CVE-2015-5607 | high | — | ipython | — | — |
| CVE-2016-10075 | high | — | tqdm | — | — |
| CVE-2016-10745 | high | — | jinja2 | — | — |
| CVE-2016-9243 | high | — | cryptography | — | — |
| CVE-2018-1000164 | high | — | gunicorn | — | — |
| CVE-2018-1000807 | high | — | pyopenssl | — | — |
| CVE-2018-1000808 | high | — | pyopenssl | — | — |
| CVE-2018-10903 | high | — | cryptography | — | — |
| CVE-2018-18074 | high | — | requests | — | — |
| CVE-2019-10906 | high | — | jinja2 | — | — |
| CVE-2019-12408 | high | — | pyarrow | — | — |
| CVE-2019-12410 | high | — | pyarrow | — | — |
| CVE-2020-15225 | high | — | django-filter | — | — |
| CVE-2020-25659 | high | — | cryptography | — | — |
| CVE-2020-36242 | high | — | cryptography | — | — |
| CVE-2021-20270 | high | — | pygments | — | — |
| CVE-2021-27291 | high | — | pygments | — | — |
| CVE-2021-32839 | high | — | sqlparse | — | — |
| CVE-2022-21699 | high | — | ipython | — | — |
| CVE-2023-0286 | high | — | cryptography | — | — |
| CVE-2023-34233 | high | — | snowflake-connector-python | — | — |
| CVE-2023-38325 | high | — | cryptography | — | — |
| CVE-2023-50782 | high | — | cryptography | — | — |
| CVE-2024-1135 | high | — | gunicorn | — | — |
| CVE-2024-26130 | high | — | cryptography | — | — |
| CVE-2024-4340 | high | — | sqlparse | — | — |
| CVE-2024-6827 | high | — | gunicorn | — | — |
| CVE-2025-24793 | high | — | snowflake-connector-python | — | — |
| CVE-2026-1207 | high | — | django | 6 | — |
| CVE-2026-1287 | high | — | django | 6 | — |
| CVE-2026-25673 | high | — | django | 6 | — |
| CVE-2026-26007 | high | — | cryptography | — | — |
| CVE-2026-27459 | high | — | pyopenssl | — | — |
| CVE-2026-33034 | high | — | django | 6 | — |
| CVE-2026-3902 | high | — | django | 6 | — |
| CVE-2026-6321 | high | — | fast-uri | 3.0.3 | — |
| CVE-2026-6322 | high | — | fast-uri | 3.0.3 | — |
| CVE-2014-0012 | medium | — | jinja2 | — | — |
| CVE-2014-1829 | medium | — | requests | — | — |
| CVE-2014-1830 | medium | — | requests | — | — |
| CVE-2015-2296 | medium | — | requests | — | — |
| CVE-2015-4706 | medium | — | ipython | — | — |
| CVE-2015-4707 | medium | — | ipython | — | — |
| CVE-2015-6938 | medium | — | ipython | — | — |
| CVE-2020-25626 | medium | — | djangorestframework | — | — |
| CVE-2020-28493 | medium | — | jinja2 | — | — |
| CVE-2022-30187 | medium | — | azure-storage-blob | — | — |
| CVE-2022-40896 | medium | — | pygments | — | — |
| CVE-2022-42965 | medium | — | snowflake-connector-python | — | — |
| CVE-2023-23931 | medium | — | cryptography | — | — |
| CVE-2023-30608 | medium | — | sqlparse | — | — |
| CVE-2023-32681 | medium | — | requests | — | — |
| CVE-2023-49083 | medium | — | cryptography | — | — |
| CVE-2024-0727 | medium | — | cryptography | — | — |
| CVE-2024-22195 | medium | — | jinja2 | — | — |
| CVE-2024-34064 | medium | — | jinja2 | — | — |
| CVE-2024-35195 | medium | — | requests | — | — |
| CVE-2024-47081 | medium | — | requests | — | — |
| CVE-2024-49750 | medium | — | snowflake-connector-python | — | — |
| CVE-2024-56201 | medium | — | jinja2 | — | — |
| CVE-2024-56326 | medium | — | jinja2 | — | — |
| CVE-2025-24794 | medium | — | snowflake-connector-python | — | — |
| CVE-2025-24795 | medium | — | snowflake-connector-python | — | — |
| CVE-2025-27516 | medium | — | jinja2 | — | — |
| CVE-2026-1312 | medium | — | django | 6 | — |
| CVE-2026-25645 | medium | — | requests | — | — |
| CVE-2026-33033 | medium | — | django | 6 | — |
| CVE-2026-39892 | medium | — | cryptography | — | — |
| GHSA-27jp-wm6q-gp25 | medium | — | sqlparse | — | — |
| GHSA-39hc-v87j-747x | medium | — | cryptography | — | — |
| GHSA-h4gh-qq45-vh27 | medium | — | cryptography | — | — |
| CVE-2023-24816 | low | — | ipython | — | — |
| CVE-2024-12797 | low | — | cryptography | — | — |
| CVE-2024-21520 | low | — | djangorestframework | — | — |
| CVE-2024-34062 | low | — | tqdm | — | — |
| CVE-2025-13473 | low | — | django | 6 | — |
| CVE-2025-14550 | low | — | django | 6 | — |
| CVE-2026-1285 | low | — | django | 6 | — |
| CVE-2026-25674 | low | — | django | 6 | — |
| CVE-2026-27448 | low | — | pyopenssl | — | — |
| CVE-2026-34073 | low | — | cryptography | — | — |
| CVE-2026-4277 | low | — | django | 6 | — |
| CVE-2026-4292 | low | — | django | 6 | — |
| CVE-2026-4539 | low | — | pygments | — | — |
| GHSA-5cpq-8wj7-hf2v | low | — | cryptography | — | — |
| GHSA-jm77-qphf-c4w8 | low | — | cryptography | — | — |
| GHSA-v8gr-m533-ghj9 | low | — | cryptography | — | — |
| CVE-2024-52338 | unknown | — | pyarrow | — | — |
Showing 99 of 99