Cyber Resilience

CVE-2026-57211

SSRF in Broadcom Rabbitmq Server 4.1.0 – 4.2.6

Public PoCSSRFPath Traversal
Published
10 July 2026
Modified
13 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0043 36th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2026-57211 is a medium-severity Absolute Path Traversal (CWE-36) vulnerability in Broadcom Rabbitmq Server. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

RabbitMQ is a messaging and streaming broker. Prior to 4.1.11 and 4.2.6 on Windows, the RabbitMQ management plugin static file handler rabbit_mgmt_wm_static can pass URL-encoded backslashes to erl_prim_loader:read_file_info before path validation when multiple management extension plugins are enabled, causing outbound…

more

DNS and SMB requests to attacker-controlled UNC paths. This issue is fixed in versions 4.1.11 and 4.2.6.

CWE(s)
CWE-36CWE-918

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-30679Same product: Microsoft Windows
CVE-2025-0539Same product: Microsoft Windows
CVE-2024-40898Same product: Microsoft Windows
CVE-2025-30680Same product: Microsoft Windows
CVE-2025-30678Same product: Microsoft Windows
CVE-2024-33864Same product: Microsoft Windows
CVE-2023-3765Same product: Microsoft Windows
CVE-2024-43394Same product: Microsoft Windows
CVE-2025-69274Same product: Microsoft Windows
CVE-2025-69267Same product: Microsoft Windows

Affected Assets

broadcom
rabbitmq server
4.1.0 — 4.2.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

AC-4 Information Flow Enforcement good match

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

SI-10 Information Input Validation good match

Input validation directly stops construction of absolute paths from untrusted data before they reach file operations.

AC-3 Access Enforcement partial match

Enforced access authorizations can limit which resources are reachable even if a traversal succeeds.

SC-7 Boundary Protection partial match

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and path sanitization that prevent absolute path traversal.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect absolute path traversal via static analysis and fuzzing.

A.5.7 Threat intelligence partial match
prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes input validation and path-handling requirements that reduce absolute path traversal risk.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate controls against path traversal in file-access functions.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles call for canonicalization and sandboxing that limit absolute path traversal.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require neutralization of absolute path sequences in pathname construction.

References