httpd:2.4.70-trixie
Rebuilt 3d ago9 critical CVEs7 archs
$
docker pull httpd:2.4.70-trixie Image metadata
PULL COUNT
4.8B
repository-level (not per-tag)
SIZE (COMPRESSED)
45 MB
ARCHITECTURES
7
RUNS AS
root
image config.User
LAST PUSHED
3d ago
2026-11-11 01:52:53
MANIFEST DIGEST
sha256:f243c844139c…
from registry manifest
Latest scan
2026-11-12 01:57:13 UTC · 2d agoOPEN CVES BY SEVERITY
9
CRITICAL
123
HIGH
91
MEDIUM
104
LOW/NEG
Grype DB
2026-11-11T06:21:32.000Z
· rubric cerodeo-v2 RUBRIC BREAKDOWN (6 signals that moved the score)
-72 · Critical CVEs (no fix) -369 · High CVEs (no fix) -91 · medium_unfixable +10 · Rebuilt in last 90 days +3 · Multi-arch +2 · readme_has_example
Consider instead
same role, higher gradeRebuilt 9d ago0 critical CVEs3 archsNon-root
shared: role:reverse-proxy · role:web-server
Rebuilt 23d ago0 critical CVEs7 archs
shared: role:reverse-proxy · role:web-server
Rebuilt 3d ago0 critical CVEs3 archsNon-root
shared: role:reverse-proxy
Raw data
Every signal above decomposes to arithmetic from inputs you can verify. Nothing in these downloads is derived or massaged — they're the raw grype matches and the raw snapshot history exactly as our scanner wrote them.
Reproduce this score yourself
We don't use judgement to score — every signal is deterministic from the image, the manifest, and a pinned CVE DB.
Run the script below on any host with skopeo, syft,
grype, cosign, and jq installed — it fetches the versioned rubric spec, computes the same breakdown, and prints the same grade. Pin the Grype DB with --grype-db to reproduce bit-for-bit identical results.
curl -fsSLO https://ce.rodeo/verify-score.sh && chmod +x verify-score.sh
./verify-score.sh httpd:2.4.70-trixie \
--rubric cerodeo-v2 \
--grype-db 2026-11-11T06:21:32.000Z
All open CVEs (366)
sorted by severity, then CVSS score CVE ID SEV CVSS PACKAGE FIX
+ 166 more in the raw JSON
Scan history
8 total · first 3d ago SCANNED AT GRADE SCORE CRIT HIGH MED GRYPE DB
2d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
2d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
2d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
3d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
3d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
3d ago F 0 9 123 91 2026-11-11T06:21:32.000Z · (same SBOM)
3d ago F 0 9 123 91 2026-11-11T06:21:32.000Z
3d ago F 0 9 115 71 2026-11-10T06:21:20.000Z
Discussion
No comments yet. Be the first.