Tools / Bareos / Security

Security Deep Dive

Bareos

Security posture and CVE patch evidence from tracked releases.

Back to Tool

7 critical dependency CVEs affects Release/25.0.4.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 0d 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: 14d ago

Release cadence: weekly Present

0d median over recent releases Release history

Latest release: 24d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 10d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 24d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 24d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 24d ago

4.3/10 Security Score

6.5/10 Scorecard

Dependency Exposure 25 transitive dependency CVEs found in the latest SBOM. 7 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

2d stale

scorecard

2.60 / 4.0

Score 6.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 54.7/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

4.5

10%

supply chain risk: 54.69 transitive cves: 7c/13h

Provenance trust

provenance trust

6.5

40%

scorecard score: 6.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 2d

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 54.7/100

7 Transitive critical CVEs

0 KEV-transitive CVEs

66% Dependency freshness

Scorecard

Scorecard 6.5/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Code-Review	10	all changesets reviewed
Maintained	10	30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Security-Policy	10	security policy file detected
License	9	license file 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
Binary-Artifacts	10	no binaries found in the repo
Packaging	10	packaging workflow detected
SAST	0	SAST tool is not run on all commits -- score normalized to 0
Pinned-Dependencies	1	dependency not pinned by hash detected -- score normalized to 1
Fuzzing	0	project is not fuzzed

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

66 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (0) All (25)

Critical 7 High 13 Medium 5

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2016-7036	critical	—	python-jose	—	Release/25.0.4
CVE-2017-18342	critical	—	pyyaml	—	Release/25.0.4
CVE-2019-20477	critical	—	pyyaml	—	Release/25.0.4
CVE-2020-14343	critical	—	pyyaml	—	Release/25.0.4
CVE-2020-1747	critical	—	pyyaml	—	Release/25.0.4
CVE-2021-3007	critical	—	laminas/laminas-http	2.8.4	Release/25.0.4
CVE-2024-33663	critical	—	python-jose	—	Release/25.0.4
CVE-2020-7694	high	—	uvicorn	—	Release/25.0.4
CVE-2020-7695	high	—	uvicorn	—	Release/25.0.4
CVE-2021-32677	high	—	fastapi	—	Release/25.0.4
CVE-2024-24762	high	—	fastapi	—	Release/25.0.4
CVE-2024-24762	high	—	python-multipart	—	Release/25.0.4
CVE-2024-53981	high	—	python-multipart	—	Release/25.0.4
CVE-2026-24486	high	—	python-multipart	—	Release/25.0.4
CVE-2026-32274	high	—	black	24.8.0	Release/25.0.4
CVE-2026-42215	high	—	gitpython	3.1.43	Release/25.0.4
CVE-2026-42284	high	—	gitpython	3.1.43	Release/25.0.4
CVE-2026-42561	high	—	python-multipart	—	Release/25.0.4
CVE-2026-44243	high	—	gitpython	3.1.43	Release/25.0.4
CVE-2026-44244	high	—	gitpython	3.1.43	Release/25.0.4
CVE-2021-29510	medium	—	pydantic	—	Release/25.0.4
CVE-2022-23598	medium	—	laminas/laminas-form	2.6.0	Release/25.0.4
CVE-2024-33664	medium	—	python-jose	—	Release/25.0.4
CVE-2024-3772	medium	—	pydantic	—	Release/25.0.4
CVE-2026-40347	medium	—	python-multipart	—	Release/25.0.4

Showing 25 of 25