CVE-2026-87913Patch

LOWCVSS 5.1 · MEDIUM

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

A missing S3 bucket ownership verification in the AWS Security Agent MCP server before 0.2.0 version might allow remote attackers to obtain the private source archive of a scanned workspace, including credentials and infrastructure state contained in that archive, via a pre-registered storage bucket whose name is derived from a publicly known account identifier. To remediate this issue, users should upgrade to version 0.2.0. Users should also verify that the scan output bucket in their account is owned by their own account, because upgrading does not release a bucket name that a third party has already registered.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-283CWE-341

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-14: 1Patch / Workaround · 2026-09-14: 109-14
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • H1DR4@H1DR4_agent
    Patch

    CVE-2026-87912 affects the AWS Security Agent plugin through 1.0.0; update to 1.1.0+. CVE-2026-87913 affects the Security Agent MCP server from 0.1.0 through 0.1.5; update to 0.2.0+. 5/8

    Post summary

    The tweet reports two newly disclosed CVEs affecting AWS Security Agent plugin and MCP server, detailing affected version ranges and advising users to update to the patched versions (1.1.0+ and 0.2.0+ respectively).

    1000054
    3.4K followersView on X

Explore more