{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-87913 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-87913 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-87913 is a medium-severity missing authorization vulnerability in AWS Security Agent MCP server, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-87913 and fix it if it is affected.\n\nWhat it is: CVE-2026-87913 is a medium-severity missing authorization vulnerability in AWS Security Agent MCP server, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-87913 in the wild and no public exploit code.\n\nAffected product: AWS Security Agent MCP server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-87913/ (Markdown: https://insights.sbomify.com/CVE-2026-87913/index.md)","id":"CVE-2026-87913","markdown":"https://insights.sbomify.com/CVE-2026-87913/index.md","name":"CVE-2026-87913","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS Security Agent MCP","requires_auth":"none","summary":"Attackers can steal private source archives and credentials by exploiting missing S3 bucket ownership checks in the AWS Security Agent MCP server.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-341","name":"Predictable from Observable State"},{"id":"CWE-283","name":"Unverified Ownership"}],"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.\n\nTo 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing S3 bucket ownership verification in the AWS Security Agent MCP server","id":"CVE-2026-87913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Popup Maker \u003c= 1.24.0 - Unauthenticated Stored Cross-Site Scripting via values[Name] Parameter","id":"CVE-2026-87915"},"packages":[],"prev":{"headline":"Missing S3 bucket ownership verification in the AWS Security Agent plugin for aws-agents-for-devsecops","id":"CVE-2026-87912"},"products":["AWS Security Agent MCP server"],"published":"2026-09-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-10","vendors":["AWS"]},"summary":"Attackers can steal private source archives and credentials by exploiting missing S3 bucket ownership checks in the AWS Security Agent MCP server.","url":"https://insights.sbomify.com/CVE-2026-87913/"}