Tools / BentoML / Security

Security Deep Dive

BentoML

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v1.4.39.

Audit transitive dependencies; consider upgrading or pinning replacements.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

8 versions tracked

Version	Published	C	H	M	L	KEV	Notes
v1.4.39	2026-05-07	—	—	—	—	—	Latest Patches CVE-2023-4863
v1.4.38	2026-04-02	—	1	—	—	KEV 1	—
v1.4.37	2026-03-25	—	1	—	—	KEV 1	—
v1.4.36	2026-03-06	—	1	—	—	KEV 1	—
v1.4.35	2026-02-03	—	1	—	—	KEV 1	—
v1.4.34	2026-01-26	—	1	—	—	KEV 1	—
v1.4.33	2026-01-12	—	1	—	—	KEV 1	—
v1.4.32	2026-01-09	—	1	—	—	KEV 1	—

— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 13d 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

13d median over recent releases Release history

Latest release: 27d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 27d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 27d ago

Signing assets Not active yet

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

Latest release: 27d ago

1.1/10 Security Score

6.5/10 Scorecard

Dependency Exposure 6 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.00 / 0.5

Max EPSS 0.933

freshness

1.00 / 1.0

2d stale

scorecard

2.60 / 4.0

Score 6.5/10

cve health

0.00 / 2.5

⚠ No direct scan — 41c/107h transitive CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

-1.50 / 1.5

KEV exposure detected

supply chain risk

-1.50 / 10.0

Risk 100.0/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

0.0

10%

supply chain risk: 100.0 transitive cves: 41c/107h

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

0.0

10%

kev exposure: detected epss max: 0.933

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

88% 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	5	Found 11/22 approved changesets -- score normalized to 5
Maintained	10	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Security-Policy	10	security policy file detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
License	10	license file detected
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
Binary-Artifacts	10	no binaries found in the repo
Fuzzing	0	project is not fuzzed
Packaging	10	packaging workflow detected
SAST	9	SAST tool detected but not 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.

CVE Patch History

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low

2026

CVE	Severity	EPSS	Disclosed	Fixed in	Days to fix	vs Ecosystem Median	KEV
CVE-2023-4863	HIGH	99%ile	—	v1.4.39	—	—	KEV

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

76 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 (6) All (231)

Critical 1 Medium 4 Unknown 1

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2020-13092	critical	—	scikit-learn	0.20.3	v1.4.39
CVE-2024-5206	medium	—	scikit-learn	0.20.3	v1.4.39
CVE-2025-3047	medium	—	aws-sam-cli	0.33.1	v1.4.39
CVE-2025-3048	medium	—	aws-sam-cli	0.33.1	v1.4.39
GHSA-rjc6-vm4h-85cg	medium	—	aws-sam-cli	0.33.1	v1.4.39
CVE-2020-28975	unknown	—	scikit-learn	0.20.3	v1.4.39

Showing 6 of 231