Tools / cloudflared / Security

Security Deep Dive

cloudflared

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects 2026.5.2.

Audit transitive dependencies; consider upgrading or pinning replacements.

— Signed — SLSA — SBOM ✗ Security policy Weekly cadence · 10d 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: 21d ago

Release cadence: weekly Present

10d median over recent releases Release history

Latest release: 7d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 2d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 7d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 7d ago

Signing assets Not active yet

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

Latest release: 7d ago

5.6/10 Security Score

5.2/10 Scorecard

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

6d stale

scorecard

2.08 / 4.0

Score 5.2/10

cve health

1.25 / 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.01 / 10.0

Risk 10.1/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

5.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.0

10%

supply chain risk: 10.1 transitive cves: 1c/3h

Provenance trust

provenance trust

5.2

40%

scorecard score: 5.2 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 6d

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

1 Transitive critical CVEs

0 KEV-transitive CVEs

95% Dependency freshness

Scorecard

Scorecard 5.2/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 0 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow	10	no dangerous workflow patterns detected
Packaging	-1	packaging workflow not detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Code-Review	0	Found 0/30 approved changesets -- score normalized to 0
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
SAST	0	no SAST tool detected
Binary-Artifacts	10	no binaries found in the repo
Fuzzing	10	project is fuzzed
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
Security-Policy	10	security policy file detected
Signed-Releases	0	Project has not signed or included provenance with any releases.
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.

Dependency Vulnerabilities

101 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 (16) All (16)

Critical 1 High 3 Medium 7 Unknown 5

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-33186	critical	—	google.golang.org/grpc	v1.72.2	2026.5.0
CVE-2026-29181	high	—	go.opentelemetry.io/otel	v1.40.0	2026.5.0
CVE-2026-34986	high	—	github.com/go-jose/go-jose/v4	v4.1.3	2026.5.0
CVE-2026-39883	high	—	go.opentelemetry.io/otel/sdk	v1.40.0	2026.5.0
CVE-2023-32681	medium	—	requests	2.28.2	2026.5.0
CVE-2024-35195	medium	—	requests	2.28.2	2026.5.0
CVE-2024-47081	medium	—	requests	2.28.2	2026.5.0
CVE-2025-47914	medium	—	golang.org/x/crypto	v0.38.0	2026.5.0
CVE-2025-58181	medium	—	golang.org/x/crypto	v0.38.0	2026.5.0
CVE-2025-71176	medium	—	pytest	7.3.1	2026.5.0
CVE-2026-25645	medium	—	requests	2.28.2	2026.5.0
CVE-2025-47911	unknown	—	golang.org/x/net	v0.40.0	2026.5.0
CVE-2025-47913	unknown	—	golang.org/x/crypto	v0.38.0	2026.5.0
CVE-2025-58190	unknown	—	golang.org/x/net	v0.40.0	2026.5.0
CVE-2025-69725	unknown	—	github.com/go-chi/chi/v5	v5.2.2	2026.5.0
CVE-2026-33814	unknown	—	golang.org/x/net	v0.40.0	2026.5.0

Showing 16 of 16