Ubuntu USN-8933-1 Fixes Twelve RabbitMQ Server Vulnerabilities
Quick Answer
Ubuntu published USN-8933-1 for twelve RabbitMQ Server vulnerabilities across supported LTS and ESM releases. Match each host to the notice's release-specific scope, install the listed package, restart rabbitmq-server, validate messaging, TLS, management, and authentication paths, and retain evidence.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory RabbitMQ nodes, Ubuntu releases, package versions, enabled management and trust-store plugins, AMQP and WebSocket endpoints, OAuth or JWKS integration, clusters, and clients; install the release-specific package; restart rabbitmq-server; and validate cluster and application health.
Last verified: 2026-10-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | RabbitMQ Server on Ubuntu 16.04 ESM through Ubuntu 26.04 LTS |
|---|---|
| Advisory | USN-8933-1 |
| CVEs | CVE-2026-66070, CVE-2026-66077, CVE-2026-66079, CVE-2026-67231, CVE-2026-67232, CVE-2026-67235, CVE-2026-67236, CVE-2026-67237, CVE-2026-67238, CVE-2026-67239, CVE-2026-67404, CVE-2026-67409 |
| Authoritative release date | 2026-10-15 17:27:24.712969 UTC |
| Authority revision date | 2026-10-15 17:27:24.712969 UTC |
| Affected versions | The Ubuntu RabbitMQ Server packages and releases enumerated in USN-8933-1; individual CVE applicability differs by Ubuntu release and enabled RabbitMQ function. |
| Fixed version | bionic: rabbitmq-server 3.6.10-1ubuntu0.5+esm1 / focal: rabbitmq-server 3.8.3-0ubuntu0.3+esm2 / jammy: rabbitmq-server 3.9.27-0ubuntu0.6 / noble: rabbitmq-server 3.12.1-1ubuntu1.7 / resolute: rabbitmq-server 4.0.5-10ubuntu5.2 / xenial: rabbitmq-server 3.5.7-1ubuntu0.16.04.4+esm3 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
Ubuntu corrected twelve RabbitMQ issues spanning CORS, certificate validation and display, AMQP parsing, WebSocket and message sizing, credential and OAuth handling, and JWKS response validation. Ubuntu directs administrators to update and restart rabbitmq-server.
What To Validate Now
- Inventory. Locate RabbitMQ Server on Ubuntu 16.04 ESM through Ubuntu 26.04 LTS deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: The Ubuntu RabbitMQ Server packages and releases enumerated in USN-8933-1; individual CVE applicability differs by Ubuntu release and enabled RabbitMQ function. Do not infer applicability from product family or severity alone.
- Remediate. Apply bionic: rabbitmq-server 3.6.10-1ubuntu0.5+esm1 / focal: rabbitmq-server 3.8.3-0ubuntu0.3+esm2 / jammy: rabbitmq-server 3.9.27-0ubuntu0.6 / noble: rabbitmq-server 3.12.1-1ubuntu1.7 / resolute: rabbitmq-server 4.0.5-10ubuntu5.2 / xenial: rabbitmq-server 3.5.7-1ubuntu0.16.04.4+esm3 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
The twelve CVEs do not apply uniformly to every Ubuntu release or RabbitMQ feature. Ubuntu 16.04, 18.04, and 20.04 fixes require the applicable Pro, ESM, or Legacy Support entitlement; coordinate clustered restarts to preserve service availability. Preserve the authority snapshot, asset and owner records, before-and-after versions, change approval, installation output, validation results, exceptions, and rollback evidence.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.

