hermes - 💡(How to fix) Fix Rebuild Docker image to pick up 41 patched Debian 13 packages (5 CRITICAL, 36 HIGH)

Summary

Trivy scan of nousresearch/hermes-agent:main@sha256:23c691a7cefd74785df3c95ffd9d0f71c0891a3497aa19aaa8e3b1a79bad4ce5 (current :main digest as of 2026-05-21) reports 172 CRITICAL/HIGH CVEs, of which 41 are already fixed in Debian 13 — they would disappear with a simple image rebuild against fresh apt mirrors. No code or Dockerfile changes needed.

Why filing

The Hermes Agent image is the foundation for self-hosted deployments. CI vulnerability gates (Trivy, Grype, Docker Scout) block deployment of images with known CRITICAL CVEs. A scheduled rebuild — e.g. weekly via GitHub Actions — would keep the published image fresh as Debian ships patches.

Concrete data

Scanner: Trivy 0.70.0
Image scanned: nousresearch/hermes-agent:main@sha256:23c691a7…
OS detected: debian 13.4, 784 packages
Vulnerability counts:

Specifically affected packages (fixed in Debian, need rebuild)

(Full triage available on request.)

Suggested fixes

Option A — One-time rebuild (minimum) Rebuild the published :main tag against today's debian:13.4 apt cache. The 41 fixed CVEs disappear immediately. Existing Dockerfile is unchanged; only apt-get update && apt-get install … resolves to newer package versions during build.

Option B — Scheduled rebuilds (preferred) Add a GitHub Actions workflow that triggers docker build --pull weekly on a cron schedule and publishes a fresh :main digest. Keeps the image fresh as Debian ships patches.

Option C — Bump to debian:13-slim or pin a fresher base digest If the full debian:13.4 base ships too many extras, a -slim variant or a digest-pinned more-recent 13.x tag would similarly close the gap and shrink the image.

Context

This isn't blocking us from running Hermes locally — but it does block PRs through any CI Trivy/Grype gate downstream. We've added a documented .trivyignore for the 40 CVEs that are demonstrably unreachable in our deployment (kernel headers package, headless Chromium so no Mesa, docker-cli without a socket mount, openssh-client we don'''t initiate from). The remaining 93 are in genuinely-reachable code paths — those are the ones a rebuild would meaningfully help with.

Happy to help test a rebuilt image against the same Trivy scan if useful.

Reference

• Trivy SARIF / JSON / table report can be shared on request.
• Scan reproducer:

  trivy image --severity CRITICAL,HIGH --no-progress \
    nousresearch/hermes-agent:main@sha256:23c691a7cefd74785df3c95ffd9d0f71c0891a3497aa19aaa8e3b1a79bad4ce5