CVE-2026-18655 AWS CVE debrief

Who should care

Defenders responsible for Amazon MQ MCP Server deployments should assess exposure and prioritize upgrading to version 2.0.24. This includes operators, platform administrators, vulnerability management teams, and security teams who manage or interact with Amazon MQ MCP Server. They should verify exposure, review compensating controls, and plan for remediation through normal change control processes. Security teams should also track exceptions and retest rem

Why it matters

CVE-2026-18655 requires verification of exposure and prompt upgrading to version 2.0.24 to prevent potential unauthorized access to broker credentials or OAuth access tokens in Amazon MQ MCP Server deployments.

• Verify exposure by checking current Amazon MQ MCP Server version
• Potential unauthorized access to broker credentials or OAuth access tokens
• Upgrade to version 2.0.24 to remediate vulnerability
• Restrict access to RabbitMQ broker connection tools

Technical summary

Improper restriction of intended endpoints in RabbitMQ broker connection tools of Amazon MQ MCP Server before 2.0.24 may allow remote unauthenticated actors to obtain broker credentials or OAuth access tokens. This issue has a CVSS score of 7.1 and is considered high severity. The affected product is Amazon MQ MCP Server, and the recommended remediation is to upgrade to version 2.0.24. The CVE record was published on 2026-08-03T20:17:17.557Z and has not been modified since then. The vulnerability impacts Amazon MQ for RabbitMQ broker deployments.

Defensive priority

Defenders should prioritize verifying exposure and upgrading to version 2.0.24.

Recommended defensive actions

• Verify exposure by checking current Amazon MQ MCP Server version
• Upgrade to version 2.0.24
• Review and restrict access to RabbitMQ broker connection tools
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

Evidence from Amazon and GitHub indicates improper restriction of intended endpoints in RabbitMQ broker connection tools may allow remote unauthenticated actors to obtain broker credentials or OAuth access tokens.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.