Skip to content
QuenchWorks

kfp-frontend

Image · Machine learning & AI · standard · v2.17.2

D 4cosign signedSPDX SBOMSLSA provenanceamd64 · arm64Rebuilt 2026-10-22

The Kubeflow Pipelines UI, the React client and the Node server that serves it and proxies the API server, artifacts and pod logs. Built from source with its npm dependencies pinned to fixed releases.

Signed
cosign keyless
SBOM
SPDX, on digest
Provenance
SLSA build
Architectures
amd64, arm64
Runs as
nonroot (uid 1001)
Root filesystem
read-only
Image size
70.1 MB

Published versions

1 tag

Each tag is a multi-arch index (amd64 + arm64) pinned by digest. Tagged by version, never :latest.

VersionSizePublishedDigest
2.17.2latest70.1 MB2026-10-22sha256:797ddc1237d4…

Security report (Trivy)

D· 57/1003 fixable · rebuild clears them

Vulnerability detail

kfp-frontend 2.17.2 · 4 CVE
CVESeverityPackageInstalledFixed inTitle
CVE-2026-111181HIGHbody-parser2.3.02.4.0, 1.20.9body-parser: body-parser: Denial of Service via unhandled decompression stream error
CVE-2026-85393HIGHnode-forge1.4.0— not fixablenode-forge: node-forge: Signature forgery vulnerability in RSA PKCS#1 v1.5 verification
CVE-2026-110816MEDIUMqs6.16.06.16.1qs: qs: Denial of Service via unhandled exception during array serialization
CVE-2026-111997MEDIUMip-address10.7.210.7.4ip-address: ip-address: Denial of Service via excessive percent characters in IPv6 address input
0
Critical
2
High
2
Medium
0
Low
0
Unknown
fixable per nightly scan · peak 21 of 115 days with any · 2026-06-29 to 2026-10-22

Pull the image

Run it directly with Docker, Podman, or any Kubernetes workload. Nonroot, read-only root filesystem, built for amd64 and arm64.

Pull (tag)

docker pull ghcr.io/quenchworks/images/kfp-frontend:2.17.2

Tags

2.17.22.17.2-amd642.17.2-arm64

Images are tagged by app version (never :latest): a multi-arch index plus per-arch tags.

App version
2.17.2
Architectures
amd64, arm64
Runs as
nonroot (uid 1001)
Root filesystem
read-only
License
Apache-2.0

Verify the supply chain

This image is cosign-signed and carries an SPDX SBOM and a SLSA build-provenance attestation on the same digest. Check all three yourself:

# 1. signature — built and signed by QuenchWorks CI
cosign verify ghcr.io/quenchworks/images/kfp-frontend:2.17.2 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# 2. SLSA build provenance — which workflow built it, from what
cosign verify-attestation --type https://slsa.dev/provenance/v1 ghcr.io/quenchworks/images/kfp-frontend:2.17.2 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# 3. SPDX SBOM — the package inventory
cosign verify-attestation --type https://spdx.dev/Document/v2.3 ghcr.io/quenchworks/images/kfp-frontend:2.17.2 \
  --certificate-identity-regexp 'https://github.com/quenchworks/.+' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

See the SBOM & provenance guide for reading the SBOM and using these checks in CI.

Transparency

Every image carries its SBOM and provenance as attestations on the same digest, publicly verifiable with the commands above (they check the package and the Sigstore transparency log, Rekor).

Upstream project: https://www.kubeflow.org/docs/components/pipelines/