Tools / bigbluebutton / Security

Security Deep Dive

bigbluebutton

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v3.0.28.

Audit transitive dependencies; consider upgrading or pinning replacements.

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

Release cadence: weekly Present

14d median over recent releases Release history

Latest release: 5d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 5d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 5d ago

Signing assets Not active yet

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

Latest release: 5d ago

5.0/10 Security Score

5.6/10 Scorecard

Dependency Exposure 36 transitive dependency CVEs found in the latest SBOM. 1 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.24 / 4.0

Score 5.6/10

cve health

1.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 53.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

4.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

4.7

10%

supply chain risk: 53.03 transitive cves: 1c/24h

Provenance trust

provenance trust

5.6

40%

scorecard score: 5.6 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 53.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

48% Dependency freshness

Scorecard

Scorecard 5.6/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 13 issue activity found in the last 90 days -- score normalized to 10
Code-Review	7	Found 14/18 approved changesets -- score normalized to 7
Dangerous-Workflow	10	no dangerous workflow patterns detected
Packaging	-1	packaging workflow not detected
Security-Policy	10	security policy file detected
CII-Best-Practices	2	badge detected: InProgress
License	10	license file detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	4	binaries present in source code
Signed-Releases	-1	no releases found
Branch-Protection	1	branch protection is not maximal on development and all release branches
SAST	10	SAST tool is run on all commits
Pinned-Dependencies	2	dependency not pinned by hash detected -- score normalized to 2
Fuzzing	0	project is not fuzzed

Dependency Vulnerabilities

6582 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 (36) All (57)

Critical 1 High 18 Medium 14 Low 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
GHSA-353f-x4gh-cqq8	critical	—	nokogiri	1.16.5	v3.0.27
CVE-2021-3803	high	—	nth-check	1.0.2	v3.0.27
CVE-2025-27610	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-46727	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-59830	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-61770	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-61771	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-61772	high	—	rack	2.2.8.1	v3.0.27
CVE-2025-61919	high	—	rack	2.2.8.1	v3.0.27
CVE-2026-22860	high	—	rack	2.2.8.1	v3.0.27
CVE-2026-27601	high	—	underscore	1.13.6	v3.0.27
CVE-2026-29074	high	—	svgo	2.8.0	v3.0.27
CVE-2026-34230	high	—	rack	2.2.8.1	v3.0.27
CVE-2026-34785	high	—	rack	2.2.8.1	v3.0.27
CVE-2026-34829	high	—	rack	2.2.8.1	v3.0.27
CVE-2026-6321	high	—	fast-uri	3.0.1	v3.0.27
CVE-2026-6322	high	—	fast-uri	3.0.1	v3.0.27
GHSA-c4rq-3m3g-8wgx	high	—	nokogiri	1.16.5	v3.0.27
GHSA-mrxw-mxhj-p664	high	—	nokogiri	1.16.5	v3.0.27
CVE-2025-25184	medium	—	rack	2.2.8.1	v3.0.27
CVE-2025-27111	medium	—	rack	2.2.8.1	v3.0.27
CVE-2025-32441	medium	—	rack	2.2.8.1	v3.0.27
CVE-2025-61780	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-25500	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-26961	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-33750	medium	—	brace-expansion	2.0.2	v3.0.27
CVE-2026-34763	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-34786	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-34826	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-34830	medium	—	rack	2.2.8.1	v3.0.27
CVE-2026-34831	medium	—	rack	2.2.8.1	v3.0.27
GHSA-v2fc-qm4h-8hqv	medium	—	nokogiri	1.16.5	v3.0.27
GHSA-wx95-c6cv-8532	medium	—	nokogiri	1.16.5	v3.0.27
CVE-2026-3449	low	—	@tootallnate/once	1.1.2	v3.0.27
GHSA-5w6v-399v-w3cc	low	—	nokogiri	1.16.5	v3.0.27
GHSA-vvfq-8hwr-qm4m	low	—	nokogiri	1.16.5	v3.0.27

Showing 36 of 57