RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics (CVE-2026-66069) | HOL Guard CVE

Low · CVSS 2.3CVE-2026-66069

RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics

Answer in brief

CVE-2026-66069 records a Low severity (CVSS 2.3) vulnerability in RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics. The current sources do not mark it as known exploited. The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 23, 2026Updated Sep 23, 2026Source checked Sep 23, 2026First seen by HOL Sep 23, 2026Material review Sep 23, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
rabbitmq/rabbitmq-servergeneric	>=4.1.0 <4.1.13 \|\| >=4.2.0 <4.2.7	4.1.13, 4.2.7

Recommended response

Check inventory. Check lockfiles and deployed manifests for rabbitmq/rabbitmq-server.
Review the reported fix. Update rabbitmq/rabbitmq-server to 4.1.13 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 23, 2026

Sources and claim methodology

Upstream source description

RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.13, 4.2.7, and 4.3.0, is_authorized/2 uses is_authorized_monitor for all methods. DELETE resets rabbit_core_metrics:reset_auth_attempt_metrics(). Impact is cosmetic (counters only, no log erasure), but inconsistent with rabbit_mgmt_wm_reset.erl which requires admin for the analogous operation. A monitoring-tagged user can reset the per-node authentication-attempt counters via DELETE /api/auth/attempts/:node, erasing evidence of brute-force activity. The sibling endpoint wm_reset requires administrator. Preconditions include Management plugin enabled monitoring tag. This issue is fixed in versions 4.1.13, 4.2.7, and 4.3.0.

Quoted source text, attributed separately from HOL analysis.