Vulnerability Reportrabbitmq:4.3.6-alpine

rabbitmq:4.3.6-alpinerabbitmq:4.3-alpine

digestsha256:6931816af1a943f471c038b278835d36692d55dec769232739296bb91b7de0f5

Executive Summary

Last scanned: Oct 21, 2026

Threat ScoreSAFE• Threat score is 0, placing the image in the SAFE band (0–24).• Trust status is OFFICIAL from Docker Official with score 100, and the image is pinned by digest for immutability.• Vulnerability stats show exposed_total=1 with exposed_max_severity=0.0, exposed_count_ge6=0, exposed_count_ge7=0, and post_total=0.• INPUT 4 and INPUT 5 provide no listed CVE findings, so no CVE IDs from those inputs can be cited.• The RabbitMQ container uses the standard docker-entrypoint.sh rabbitmq-server startup, and no input-provided finding indicates an exploitable exposed-surface risk.

0/100SAFE

ReputationOFFICIAL• Official Docker Hub Image• Pinned by digest (Immutable)

TRUSTED

This image is safe for production use. It is the official RabbitMQ image from Docker Official, pinned by digest, with a trust score of 100. The provided vulnerability stats show 1 exposed_total item, but its max severity is 0.0 and there are 0 findings with severity >=6.0, while post_total is 0, so the pre-calculated threat score remains 0. INPUT 4 and INPUT 5 contain no CVE IDs to cite, and no configuration caveats or mitigations are provided for this verdict.

Vulnerabilities

Vulnerability Log

1 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
CVE-2026-85091	NONE0	zlib 1.3.2-r0 fixed in 1.3.2-r1	0.4% Theoretical Threat	Not Applicable

Reachability analysis

Which CVEs are actually reachable — is the vulnerable code even linked and callable.

Locked

Runtime verification

Live-container probes: default user, writable paths, capabilities, exposed ports.

Locked

Supply chain analysis

Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.

Locked

Hardening recommendations

A step-by-step hardened build plan, with parity tests proving nothing breaks.

Locked

Want to check another image? Run a full scan with the Docker Security Scanner.