chore: suppress 2026-08-26 OpenSSL Alpine CVE batch pending digest bump

[Wikid82]

Summary

• Trivy's PR security gate started blocking PRs (including renovate PR chore(deps): update node.js to v24.20.0 - autoclosed #1287, node.js to v24.20.0) on 9 new CVEs against libcrypto3/libssl3 3.5.7-r0 in the Alpine base image: CVE-2026-63072, -63073, -63074, -63075, -63076, -18798, -14457, -54874, -75803 (OpenSSL advisories disclosed 2026-08-25/26).
• These are unrelated to the Node.js bump — the final runtime image doesn't even contain Node; it's a separate FROM ${ALPINE_IMAGE} stage pinned by digest (alpine:3.24.1@sha256:28bd5fe8...943f8b).
• Alpine's v3.24 tag branch already published libssl3/libcrypto3 3.5.8-r0 on 2026-08-25 which likely fixes this batch, but because the Dockerfile pins the base image by digest rather than tag, it won't pick up the fix until Renovate opens a digest-bump PR for ALPINE_IMAGE.
• None of the affected code paths (OpenSSL QUIC/CMP/CMS/DTLS/RPK servers) run in this deployment — Caddy's HTTP/3 stack uses quic-go (pure Go), and the Go backend uses native crypto/tls.
• Suppresses the batch in both .trivyignore and .grype.yaml with a short 14-day review window (2026-09-09) rather than the usual 30–90 day window, since a fix is likely one digest bump away.

Test plan

• Confirm CI's security-scan jobs pass on this PR
• Once merged, rebase/re-run renovate PR chore(deps): update node.js to v24.20.0 - autoclosed #1287's checks and confirm the Trivy gate passes
• When Renovate bumps ALPINE_IMAGE's digest, rebuild and remove this entire suppression batch

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

✅ Supply Chain Verification Results

✅ PASSED

📦 SBOM Summary

• Components: 1754

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	5
🟢 Low	2
Total	11

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.