Skip to content
Tools / humhub / Security

Security Deep Dive

humhub

Security posture and CVE patch evidence from tracked releases.

Back to Tool

10 high-severity dependency CVEs affects v1.18.3.

Review the dependency vulnerabilities below.

✗ Signed ✗ SLSA — SBOM ✓ Security policy Monthly cadence · 21d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present
Signed releases Absent
Latest release artifact signature None
Last verified: 6d ago
SLSA provenance Absent
Attestation predicate level Latest release
Last verified: 6d ago
SBOM published Unknown
GitHub SBOM API Latest release
SECURITY.md Present
GitHub repository metadata Repository policy
Checked: 16d ago
Release cadence: monthly Present
21d median over recent releases Release history
Latest release: 16d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 1d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 16d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 16d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 16d ago
4.6/10 Security Score
6.6/10 Scorecard
Dependency Exposure 18 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.64 / 4.0

Score 6.6/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.3/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

8.0

10%

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

Provenance trust

provenance trust

6.6

40%

scorecard score: 6.6 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.3/100
0 Transitive critical CVEs
0 KEV-transitive CVEs
84% Dependency freshness

Scorecard

Scorecard 6.6/10

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

Check Score Reason
Code-Review 8 Found 23/28 approved changesets -- score normalized to 8
Maintained 10 30 commit(s) and 6 issue activity found in the last 90 days -- score normalized to 10
Packaging -1 packaging workflow not detected
Dangerous-Workflow -1 no workflows found
Token-Permissions -1 No tokens found
Security-Policy 10 security policy file detected
CII-Best-Practices 0 no effort to earn an OpenSSF best practices badge detected
License 9 license file detected
Fuzzing 0 project is not fuzzed
Binary-Artifacts 10 no binaries found in the repo
Pinned-Dependencies -1 no dependencies 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
Signed-Releases -1 no releases found
SAST 0 SAST tool is not run on all commits -- score normalized to 0

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

420 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

7

Low

1

Unknown

0

High 10 Medium 7 Low 1
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2018-17567 high jekyll 0 v1.18.3
CVE-2018-3740 high sanitize 4.0.1 v1.18.3
CVE-2020-4054 high sanitize 4.0.1 v1.18.3
CVE-2022-25883 high semver 5.7.1 v1.18.3
CVE-2023-36823 high sanitize 4.0.1 v1.18.3
CVE-2026-26996 high minimatch 3.0.8 v1.18.3
CVE-2026-27903 high minimatch 3.0.8 v1.18.3
CVE-2026-27904 high minimatch 3.0.8 v1.18.3
CVE-2026-33671 high picomatch 2.3.1 v1.18.3
CVE-2026-4800 high lodash 4.17.21 v1.18.3
CVE-2020-26298 medium redcarpet 0 v1.18.3
CVE-2024-4067 medium micromatch 4.0.5 v1.18.3
CVE-2025-13465 medium lodash 4.17.21 v1.18.3
CVE-2025-64718 medium js-yaml 3.14.1 v1.18.3
CVE-2026-2950 medium lodash 4.17.21 v1.18.3
CVE-2026-33672 medium picomatch 2.3.1 v1.18.3
CVE-2026-33750 medium brace-expansion 1.1.11 v1.18.3
CVE-2025-5889 low brace-expansion 1.1.11 v1.18.3

Showing 18 of 18

Beta — feedback welcome: [email protected]