Skip to content
Tools / gerbera / Security

Security Deep Dive

gerbera

Security posture and CVE patch evidence from tracked releases.

Back to Tool

10 high-severity dependency CVEs affects v3.2.1.

Review the dependency vulnerabilities below.

— Signed — SLSA ✓ SBOM ✗ Security policy Weekly cadence · 7d 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 Present
GitHub SBOM API Latest release
Last verified: 28d ago
SECURITY.md Absent
GitHub repository metadata Repository policy
Checked: 23d ago
Release cadence: weekly Present
7d median over recent releases Release history
Latest release: 2mo ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 2mo ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 2mo ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 2mo ago
4.2/10 Security Score
5.5/10 Scorecard
Dependency Exposure 22 transitive dependency CVEs found in the latest SBOM.

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

2.20 / 4.0

Score 5.5/10

cve health

0.25 / 2.5

⚠ No direct scan — 0c/10h 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 20.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

1.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

7.9

10%

supply chain risk: 20.64 transitive cves: 0c/10h

Provenance trust

provenance trust

5.5

40%

scorecard score: 5.5 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

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 20.6/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
68% Dependency freshness

Scorecard

Scorecard 5.5/10

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

Check Score Reason
Maintained 10 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Code-Review 2 Found 3/15 approved changesets -- score normalized to 2
Dangerous-Workflow 10 no 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
Binary-Artifacts 10 no binaries found in the repo
Security-Policy 0 security policy file not detected
License 9 license file detected
Fuzzing 0 project is not fuzzed
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
Signed-Releases -1 no releases found
Packaging 10 packaging workflow detected
SAST 10 SAST tool is run on all commits
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

796 dependencies scanned View full dependency list →

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

Critical

0

High

10

Medium

10

Low

2

Unknown

0

High 10 Medium 10 Low 2
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2026-41324 high basic-ftp 5.2.2
CVE-2026-42033 high axios 1.15.0
CVE-2026-42035 high axios 1.15.0
CVE-2026-42043 high axios 1.15.0
CVE-2026-42264 high axios 1.15.0
CVE-2026-44240 high basic-ftp 5.2.2
CVE-2026-44728 high @babel/plugin-transform-modules-systemjs 7.29.0
CVE-2026-6321 high fast-uri 3.1.0
CVE-2026-6322 high fast-uri 3.1.0
GHSA-5c6j-r48x-rmvq high serialize-javascript 6.0.2
CVE-2026-34043 medium serialize-javascript 6.0.2
CVE-2026-42034 medium axios 1.15.0
CVE-2026-42036 medium axios 1.15.0
CVE-2026-42037 medium axios 1.15.0
CVE-2026-42038 medium axios 1.15.0
CVE-2026-42039 medium axios 1.15.0
CVE-2026-42041 medium axios 1.15.0
CVE-2026-42042 medium axios 1.15.0
CVE-2026-42044 medium axios 1.15.0
CVE-2026-42338 medium ip-address 10.1.0
CVE-2026-24001 low diff 7.0.0
CVE-2026-42040 low axios 1.15.0

Showing 22 of 22

Beta — feedback welcome: [email protected]