Skip to content

Security: render-examples/sandbox-images

Security

docs/security.md

Image security checks

Every image must pass its offline workload checks and security scan before the publisher can push it to GHCR. A source change or a successful build is not a security result.

What blocks publication

The image gate uses Trivy 0.76.2 and a vulnerability database updated within the last 24 hours. It blocks high and critical findings with an available fix, and all detected secrets in the image filesystem or configuration. Scanner errors, missing package inventory and stale evidence also block publication.

Findings without an available fix and lower-severity findings remain in the report. Passing the gate does not mean the image has no known vulnerabilities.

Gitleaks 8.30.1 scans Git history and the checked-out source. Its only allowlist covers two exact output checksums in the November 4 validation report. Detected credential values are redacted from logs and uploaded reports.

The scanner reads the immutable image ID from the acceptance-test receipt. The publisher verifies that ID, the configuration digest, scan age and artifact hashes immediately before pushing. Each publication artifact includes a CycloneDX SBOM, the scan report, source revision and OCI digest.

Findings that need interpretation

Debian's linux-libc-dev package contains kernel headers. Matches against the Linux kernel remain in the report but do not block these images: the guest image does not supply Render's running host kernel. This exception applies only to that Debian package, not to user-space C libraries.

Pip 26.3's embedded SBOM lists setuptools@70.3.0 for its vendored pkg_resources. CVE-2025-47273 affects setuptools.package_index, which is absent from these images. The gate excludes only that CVE/version when Trivy identifies the component from an SBOM. Before accepting the exception, it starts the tested image offline and verifies that pip and all installed Python packages contain no package_index.py or compiled copy. Patched setuptools is allowed when that module is absent; an installed vulnerable setuptools package still fails the scan. The check covers both the system Python and LangChain virtual environment. See the upstream advisory.

Trivy's GCP rule also matches the credential-free singleton {"type": "service_account"} in Anthropic SDK docstrings. The secret-scanner configuration excludes only that complete singleton. A JSON object with any additional field is still scanned, including in the same file. CI tests those boundaries with the actual scanner.

Dependency-metadata patches

The Browser Use and OpenHands dependency trees exclude patched dependencies:

  • Browser Use 1.0.5 requires Pillow 12.3.0. The image uses browser-use==1.0.5+render.1 and its helper browser-harness==0.1.13+render.1 with Pillow 13.0.0.
  • OpenHands SDK 1.62.0 requires LiteLLM below 1.106. That LiteLLM release excludes filelock 4. The image uses litellm==1.105.7+render.1 with filelock 4.2.10.

security/python-wheel-patches.json records the official wheel URLs, SHA-256 hashes and exact requirement changes. The build verifies the original hash and metadata, changes the one requirement and distribution version, regenerates wheel records and retains upstream runtime files and licenses. Each installed wheel includes render-dependency-patch.json with its provenance.

The matching security-overrides.in files let uv resolve those requirements. The Docker build substitutes the patched, hash-verified wheel into the lock; plain pip installation of the unmodified lock is not supported for these two images. Builds still run pip's dependency-consistency check. Remove the patches when upstream requirements allow the fixed versions and workload checks pass.

Security-update candidates

The candidates refresh the Node, Python 3.13, PostgreSQL and pgvector base images, including the APT security fix. All 46 images use the shared security updates and pass through the same scan gate. Node images use npm 11.21.2; Python images use pip 26.3. Additional Debian fixes pin the patched libpq and zlib packages where needed.

Image fixtures that used TypeScript 7 now use the JavaScript compiler in TypeScript 6.0.3 while the published TypeScript 7.0.2 native compiler still bundles an affected Go runtime. The dependency locks remove that native compiler. Restore TypeScript 7 after an upstream update passes the same workloads and security checks. The repository type-policy checker keeps TypeScript 7 for its compiler API; it is not shipped in the images.

The Office image pins image-size 2.1.0 and uuid 11.1.1 through dependency overrides. Its build includes a regression test for a malformed ICNS input that previously caused an infinite loop. Database fixtures use Debian's runuser; the unused upstream gosu binary is removed.

New image and recipe versions start unverified. Publishing a patched image does not change existing snapshots. Recreate snapshots from the new digest and run fresh Render import, workload, capture and restore tests before recording live verification.

GitHub's built-in secret scanning and push protection are currently disabled by enterprise policy. The repository API rejected enabling them on November 16, 2026. The CI scans above run independently of those settings.

There aren't any published security advisories