Tools / tailscale / Security

Security Deep Dive

tailscale

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v1.98.5.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✓ Security policy Monthly cadence · 15d 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: 18d ago

Release cadence: monthly Present

15d median over recent releases Release history

Latest release: 2d ago

Maintainer active Present

Recent commit activity Repository

Last commit: today

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 2d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 2d ago

Signing assets Not active yet

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

Latest release: 2d ago

4.8/10 Security Score

7.7/10 Scorecard

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

1d stale

scorecard

3.08 / 4.0

Score 7.7/10

cve health

0.00 / 2.5

⚠ No direct scan — 1c/14h 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 32.9/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

6.7

10%

supply chain risk: 32.94 transitive cves: 1c/14h

Provenance trust

provenance trust

7.7

40%

scorecard score: 7.7 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 32.9/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

53% Dependency freshness

Scorecard

Scorecard 7.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 9 issue activity found in the last 90 days -- score normalized to 10
Code-Review	10	all changesets reviewed
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Packaging	-1	packaging workflow not detected
License	10	license file detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Fuzzing	10	project is fuzzed
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
Binary-Artifacts	6	binaries present in source code
Signed-Releases	-1	no releases found
Pinned-Dependencies	7	dependency not pinned by hash detected -- score normalized to 7
SAST	9	SAST tool detected but not run on all commits

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

1367 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 (37)

Critical 1 High 6 Medium 8 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33186	critical	—	google.golang.org/grpc	v1.78.0	v1.98.2
CVE-2026-29181	high	—	go.opentelemetry.io/otel	v1.39.0	v1.98.2
CVE-2026-33747	high	—	github.com/moby/buildkit	v0.20.2	v1.98.2
CVE-2026-33748	high	—	github.com/moby/buildkit	v0.20.2	v1.98.2
CVE-2026-35469	high	—	github.com/moby/spdystream	v0.5.0	v1.98.2
CVE-2026-42151	high	—	github.com/prometheus/prometheus	v0.49.2-0.20240125131847-c3b8ef1694ff	v1.98.2
CVE-2026-42154	high	—	github.com/prometheus/prometheus	v0.49.2-0.20240125131847-c3b8ef1694ff	v1.98.2
CVE-2025-47909	medium	—	github.com/gorilla/csrf	v1.7.3	v1.98.2
CVE-2026-33532	medium	—	yaml	1.10.2	v1.98.2
CVE-2026-33809	medium	—	golang.org/x/image	v0.27.0	v1.98.2
CVE-2026-40179	medium	—	github.com/prometheus/prometheus	v0.49.2-0.20240125131847-c3b8ef1694ff	v1.98.2
GHSA-67mh-4wv8-2f99	medium	—	esbuild	0.21.5	v1.98.2
GHSA-fw8g-cg8f-9j28	medium	—	github.com/prometheus/prometheus	v0.49.2-0.20240125131847-c3b8ef1694ff	v1.98.2
GHSA-xmrv-pmrh-hhx2	medium	—	github.com/aws/aws-sdk-go-v2/service/s3	v1.75.3	v1.98.2
GHSA-xmrv-pmrh-hhx2	medium	—	github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream	v1.6.8	v1.98.2
CVE-2026-33812	unknown	—	golang.org/x/image	v0.27.0	v1.98.2
CVE-2026-33813	unknown	—	golang.org/x/image	v0.27.0	v1.98.2

Showing 17 of 37