n8n-runners

Image · Workflow · standard · v2.32.7

C 12cosign signedSPDX SBOMSLSA provenanceamd64 · arm64Rebuilt 2026-09-01

n8n external task-runner sidecar — isolates and executes workflow code (JS/Python) out of the main n8n process for security and scale. Built from source on Wolfi. Image only, no chart.

Image

ghcr.io/quenchworks/images/n8n-runners:2.32.7

Signed

cosign keyless

SBOM

SPDX, on digest

Provenance

SLSA build

Architectures

amd64, arm64

Runs as

nonroot (uid 1001)

Root filesystem

read-only

Image size

184.5 MB

Published versions

1 tag

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

Version	Size	Published	Digest
2.32.7latest	184.5 MB	2026-09-01	sha256:b1ed3220b80a…

Security report (Trivy)

C· 0/10012 fixable · rebuild clears them

Vulnerability detail

n8n-runners 2.32.7 · 12 CVE

CVE	Severity	Package	Installed	Fixed in	Title
CVE-2026-15806	MEDIUM	python-3.13	3.13.15-r4	3.13.15-r5	python: Python: Information disclosure due to incorrect URL scheme matching
CVE-2026-15806	MEDIUM	python-3.13-base	3.13.15-r4	3.13.15-r5	python: Python: Information disclosure due to incorrect URL scheme matching
CVE-2026-17084	MEDIUM	python-3.13	3.13.15-r4	3.13.15-r6	python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability
CVE-2026-17084	MEDIUM	python-3.13-base	3.13.15-r4	3.13.15-r6	python: Python stringprep module: Incorrect domain name processing breaks IDNA interoperability
CVE-2026-18374	MEDIUM	glibc-2.44	2.44-r4	2.44-r6	glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374	MEDIUM	glibc-2.44-locale-posix	2.44-r4	2.44-r6	glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374	MEDIUM	ld-linux-2.44	2.44-r4	2.44-r6	glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-18374	MEDIUM	libcrypt1-2.44	2.44-r4	2.44-r6	glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string
CVE-2026-71429	MEDIUM	stream-json	1.9.1	3.5.0	stream-json: stream-json: Denial of Service due to inefficient processing of deeply nested JSON
CVE-2026-82417	MEDIUM	qs	6.15.2	6.16.0	qs: qs: Denial of Service via improper validation in stringify function
CVE-2026-82562	MEDIUM	qs	6.15.2	6.16.0	qs: qs: Denial of Service via array limit bypass in query string parsing
CVE-2026-85091	MEDIUM	zlib	1.3.2-r5	1.3.3-r0	zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vul ...

Critical

High

Medium

Low

Unknown

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/n8n-runners:2.32.7

Tags

2.32.72.32.7-amd642.32.7-arm64

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

App version: 2.32.7
Architectures: amd64, arm64
Runs as: nonroot (uid 1001)
Root filesystem: read-only
License: LicenseRef-n8n-Sustainable-Use-License-1.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/n8n-runners:2.32.7 \
  --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/n8n-runners:2.32.7 \
  --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/n8n-runners:2.32.7 \
  --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).

View package

Upstream project: https://n8n.io