Tools / krakend-ce / Security

Security Deep Dive

krakend-ce

Security posture and CVE patch evidence from tracked releases.

Back to Tool

2 high-severity dependency CVEs affects v2.13.7.

Review the dependency vulnerabilities below.

— 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: 20d ago

Release cadence: monthly Present

15d median over recent releases Release history

Latest release: today

Maintainer active Present

Recent commit activity Repository

Last commit: 12d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: today

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: today

Signing assets Not active yet

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

Latest release: today

5.6/10 Security Score

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

2.00 / 4.0

⚠ Estimated — not yet collected

cve health

0.75 / 2.5

⚠ No direct scan — 0c/2h 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

-0.40 / 10.0

Risk 4.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

3.0

25%

direct cves: clear cve scan: estimated

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

9.6

10%

supply chain risk: 4.0 transitive cves: 0c/2h

Provenance trust

provenance trust

5.0

40%

scorecard score: estimated 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 4.0/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

OpenSSF Badge

OpenSSF none

Badge indicates adherence to open-source best practices.

Dependency Vulnerabilities

297 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 (7) All (7)

High 2 Medium 2 Unknown 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-42151	high	—	github.com/prometheus/prometheus	v0.54.0	v2.13.5
CVE-2026-42154	high	—	github.com/prometheus/prometheus	v0.54.0	v2.13.5
CVE-2026-40179	medium	—	github.com/prometheus/prometheus	v0.54.0	v2.13.5
GHSA-fw8g-cg8f-9j28	medium	—	github.com/prometheus/prometheus	v0.54.0	v2.13.5
CVE-2020-8911	unknown	—	github.com/aws/aws-sdk-go	v1.55.8	v2.13.5
CVE-2020-8912	unknown	—	github.com/aws/aws-sdk-go	v1.55.8	v2.13.5
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	v2.13.5

Showing 7 of 7