Tools / openbao / Security

Security Deep Dive

openbao

Security posture and CVE patch evidence from tracked releases.

Back to Tool

12 high-severity dependency CVEs affects v2.5.4.

Review the dependency vulnerabilities below.

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

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/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 Absent

GitHub repository metadata Repository policy

Checked: 22d ago

Release cadence: monthly Present

27d median over recent releases Release history

Latest release: 14d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 14d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 14d ago

Signing assets Not active yet

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

Latest release: 14d ago

4.9/10 Security Score

7.9/10 Scorecard

Dependency Exposure 17 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

Up to date

scorecard

3.16 / 4.0

Score 7.9/10

cve health

0.00 / 2.5

⚠ No direct scan — 4c/22h 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 60.7/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

3.9

10%

supply chain risk: 60.66 transitive cves: 4c/22h

Provenance trust

provenance trust

7.9

40%

scorecard score: 7.9 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 0d

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

0 Transitive critical CVEs

0 KEV-transitive CVEs

67% Dependency freshness

Scorecard

Scorecard 7.9/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 22 issue activity found in the last 90 days -- score normalized to 10
Dependency-Update-Tool	10	update tool detected
Code-Review	10	all changesets reviewed
Dangerous-Workflow	10	no dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Binary-Artifacts	10	no binaries found in the repo
CII-Best-Practices	2	badge detected: InProgress
SAST	10	SAST tool is run on all commits
Fuzzing	10	project is fuzzed
Packaging	10	packaging workflow detected
Pinned-Dependencies	7	dependency not pinned by hash detected -- score normalized to 7
License	10	license file detected
Security-Policy	10	security policy file detected
Signed-Releases	8	5 out of the last 5 releases have a total of 5 signed artifacts.
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
Vulnerabilities	0	77 existing vulnerabilities detected
CI-Tests	10	30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Contributors	10	project has 20 contributing companies or organizations

Dependency Vulnerabilities

4505 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 (17) All (60)

High 12 Medium 2 Low 1 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2020-7753	high	—	trim	0.0.1	v2.5.4
CVE-2021-23424	high	—	ansi-html	0.0.7	v2.5.4
CVE-2021-3803	high	—	nth-check	1.0.2	v2.5.4
CVE-2022-46175	high	—	json5	0.5.1	v2.5.4
CVE-2024-4068	high	—	braces	2.3.2	v2.5.4
CVE-2024-47068	high	—	rollup	1.32.1	v2.5.4
CVE-2026-27606	high	—	rollup	1.32.1	v2.5.4
CVE-2026-41672	high	—	@xmldom/xmldom	0.8.12	v2.5.4
CVE-2026-41673	high	—	@xmldom/xmldom	0.8.12	v2.5.4
CVE-2026-41674	high	—	@xmldom/xmldom	0.8.12	v2.5.4
CVE-2026-41675	high	—	@xmldom/xmldom	0.8.12	v2.5.4
GHSA-36jr-mh4h-2g58	high	—	d3-color	1.4.1	v2.5.4
CVE-2025-9910	medium	—	jsondiffpatch	0.4.1	v2.5.4
GHSA-r4q5-vmmm-2653	medium	—	follow-redirects	1.15.11	v2.5.4
CVE-2025-54798	low	—	tmp	0.1.0	v2.5.4
CVE-2020-8911	unknown	—	github.com/aws/aws-sdk-go	v1.55.6	v2.5.4
CVE-2020-8912	unknown	—	github.com/aws/aws-sdk-go	v1.55.6	v2.5.4

Showing 17 of 60