Vulnerability in Amazon (CVE-2026-9133)
Summary
Vulnerability in Amazon (CVE-2026-9133). Confidential information can be exposed externally. Exploitable via PUT /api/aws/arn/validate.
Original description
The description as published by the source.
Bulletin ID: 2026-034-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 05/20/2026 12:45 PM PDT Description: rabbitmq-aws is a RabbitMQ plugin that resolves AWS ARNs in broker configuration at startup, fetching secrets (e.g., TLS certificates, private keys, passwords) from AWS services (Secrets Manager, S3, ACM Private CA) and passing them in-memory to RabbitMQ. We identified CVE-2026-9133, an active debug code issue in the plugin's ARN resolver. A debug ARN scheme (arn:aws-debug:file) accepted by the PUT /api/aws/arn/validate validation endpoint might allow remote authenticated users to perform arbitrary file reads on any file accessible to the RabbitMQ process. The debug code was inadvertently shipped in production builds with no mechanism to disable it. Impacted versions: >=0.1.0,
Source: AWS Security Bulletins NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9133 has been found in Amazon.
Attackers can target a specific entry point like PUT /api/aws/arn/validate over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Amazon CVE-2026-9133" on the vendor's site.
CVE-2026-9133 (Amazon) — CWE-489 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PUT /api/aws/arn/validate
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-489) exists in Amazon. Attackers reach the vulnerable code path via PUT /api/aws/arn/validate.
Check the vendor advisory for the affected versions of Amazon. Attack surface: PUT /api/aws/arn/validate.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual PUT /api/aws/arn/validate requests with malformed payloads or SQL meta-characters. Run grep -r 'Amazon' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Amazon' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Amazonを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'PUT /api/aws/arn/validate' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
PUT /api/aws/arn/validateへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against PUT /api/aws/arn/validate on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- AWS aws.amazon.com
- web aws.amazon.com
- web github.com
- web github.com