Skip to content
Tools / shellhub / Security

Security Deep Dive

shellhub

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 actively-exploited dependency CVE affects v0.26.0.

KEV-listed CVEs are confirmed exploited in the wild — patch urgently.

Versions by Severity

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

12 versions tracked
Version Published C H M L KEV Notes
v0.26.0 2026-07-06
Latest
v0.25.1 2026-06-10
v0.25.0 2026-06-06
Patches CVE-2023-44487
v0.24.2 2026-04-29 1 KEV 1
v0.21.7 2026-04-23 1 KEV 1
v0.21.6 2026-04-23 1 KEV 1
v0.24.1 2026-04-08 1 KEV 1
v0.24.0 2026-04-01 1 KEV 1
v0.23.0 2026-04-01 1 KEV 1
v0.22.0 2026-03-10 1 KEV 1
v0.21.5 2026-01-07 1 KEV 1
v0.21.4 2026-01-02 1 KEV 1
— Signed — SLSA — SBOM ✓ Security policy Weekly cadence · 6d 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: 14d ago
Release cadence: weekly Present
6d median over recent releases Release history
Latest release: 20d ago
Maintainer active Present
Recent commit activity Repository
Last commit: 8d ago
Checksums (SHA256SUMS) Not active yet
SHA256SUMS or equivalent Release asset
Latest release: 20d ago
GitHub Actions attestation Not active yet
actions/attest-build-provenance Workflow file
Latest release: 20d ago
Signing assets Not active yet
.sig, .crt, cosign.pub, or similar Release asset
Latest release: 20d ago
0.8/10 Security Score
5.7/10 Scorecard
Dependency Exposure 32 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 1.000

freshness

1.00 / 1.0

1d stale

scorecard

2.28 / 4.0

Score 5.7/10

cve health

0.00 / 2.5

⚠ No direct scan — 3c/32h 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 91.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

5%

patch speed days: no_history

Dependency exposure

dependency exposure

0.8

10%

supply chain risk: 91.59 transitive cves: 3c/32h

Provenance trust

provenance trust

5.7

40%

scorecard score: 5.7 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

0.0

10%

kev exposure: detected epss max: 1.0
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 91.6/100
1 Transitive critical CVEs
1 KEV-transitive CVEs
70% Dependency freshness

Scorecard

Scorecard 5.7/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 28 issue activity found in the last 90 days -- score normalized to 10
Code-Review 6 Found 5/8 approved changesets -- score normalized to 6
Security-Policy 10 security policy file detected
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
License 10 license file detected
Fuzzing 10 project is fuzzed
Branch-Protection 1 branch protection is not maximal on development and all release branches
Signed-Releases 0 Project has not signed or included provenance with any releases.
SAST 0 SAST tool is not run on all commits -- score normalized to 0
Packaging 10 packaging workflow detected
Pinned-Dependencies 1 dependency not pinned by hash detected -- score normalized to 1

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
1
CVE Severity EPSS Disclosed Fixed in Days to fix vs Ecosystem Median KEV
CVE-2023-44487 HIGH 99%ile v0.25.0 KEV

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

Dependency Vulnerabilities

2373 dependencies scanned View full dependency list →

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

Critical

1

High

8

Medium

17

Low

0

Unknown

6

1 dependency vulnerabilities are in KEV.

CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.

Critical 1 High 8 Medium 17 Unknown 6
CVE Severity KEV Dependency Affected version Cleared in release
CVE-2024-45337 critical golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2021-23409 high github.com/pires/go-proxyproto 0.6.0 v0.25.0
CVE-2021-33194 high golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2021-43565 high golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2022-27191 high golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2022-27664 high golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2022-41723 high golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2023-39325 high golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2025-22869 high golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2021-31525 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2022-29526 medium golang.org/x/sys 0.0.0-20210616094352-59db8d763f22 v0.25.0
CVE-2022-41717 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2023-3978 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2023-44487 medium KEV golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.1
CVE-2023-45288 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2023-48795 medium golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2025-22870 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2025-22872 medium golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2025-47914 medium golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2025-58058 medium github.com/ulikunitz/xz v0.5.14 v0.25.0
CVE-2025-58181 medium golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2026-44423 medium github.com/shellhub-io/shellhub 0.7.1 v0.25.0
CVE-2026-44424 medium github.com/shellhub-io/shellhub 0.7.1 v0.25.0
CVE-2026-44425 medium github.com/shellhub-io/shellhub 0.7.1 v0.25.0
CVE-2026-44426 medium github.com/shellhub-io/shellhub 0.7.1 v0.25.0
GHSA-67mh-4wv8-2f99 medium esbuild 0.21.5 v0.25.0
CVE-2021-44716 unknown golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2022-30636 unknown golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2024-45338 unknown golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2025-47911 unknown golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0
CVE-2025-47913 unknown golang.org/x/crypto 0.0.0-20210616213533-5ff15b29337e v0.25.0
CVE-2025-58190 unknown golang.org/x/net 0.0.0-20210226172049-e18ecbb05110 v0.25.0

Showing 32 of 106

Beta — feedback welcome: [email protected]