{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-115413 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-115413 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-115413 is a high-severity vulnerability in aws-api-mcp-server, published on 27 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115413 and fix it if it is affected.\n\nWhat it is: CVE-2026-115413 is a high-severity vulnerability in aws-api-mcp-server, published on 27 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-115413 in the wild and no public exploit code.\n\nAffected product: aws-api-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-115413/ (Markdown: https://insights.sbomify.com/CVE-2026-115413/index.md)","id":"CVE-2026-115413","markdown":"https://insights.sbomify.com/CVE-2026-115413/index.md","name":"CVE-2026-115413","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"AMZN","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server's configured AWS credentials via an access token issued to another application by the same identity provider.\n\nTo remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.","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":"AWS API MCP Server OAuth Token Audience Validation Bypass","id":"CVE-2026-115413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OS command injection in the Terraform hook in AWS SAM CLI","id":"CVE-2026-115414"},"packages":[],"prev":{"headline":"crawlseo before 0.2.4 Server-Side Request Forgery via Crawler","id":"CVE-2026-115411"},"products":["aws-api-mcp-server"],"published":"2026-10-27","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-27","vendors":["AWS"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115413/"}