{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15737 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15737 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15737 is a medium-severity vulnerability in AWS bedrock-agentcore, published on 16 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-15737 and fix it if it is affected.\n\nWhat it is: CVE-2026-15737 is a medium-severity vulnerability in AWS bedrock-agentcore, published on 16 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-15737 in the wild and no public exploit code.\n\nAffected product: AWS bedrock-agentcore. 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-15737/ (Markdown: https://insights.sbomify.com/CVE-2026-15737/index.md)","id":"CVE-2026-15737","markdown":"https://insights.sbomify.com/CVE-2026-15737/index.md","name":"CVE-2026-15737","record":{"aliases":["GHSA-hqf8-7w95-9r33"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS Bedrock SDK","requires_auth":"low_privilege","summary":"Local authenticated users with CloudWatch access can read sensitive prompts and responses logged in OpenTelemetry spans by the AWS Bedrock AgentCore Python SDK.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"AWS Bedrock AgentCore Python SDK is an open-source Python library that provides client tools for building AI agents on the Amazon Bedrock AgentCore platform.\n\nUnintended logging of sensitive user content in the OpenTelemetry instrumentation in AWS Bedrock AgentCore Python SDK versions 1.4.8 and 1.5.0 might allow a local authenticated user with access to CloudWatch Logs to access raw user prompts and agent responses containing sensitive data via span attributes. The SDK wrote raw user prompts and complete agent responses into OpenTelemetry span attributes on every invocation without filtering or masking. These spans flow into the customer's aws/spans CloudWatch log group, exposing sensitive content to any principal with log read access.\n\nWe recommend you upgrade to version 1.5.1 or later. Users who ran affected versions should also review and purge sensitive content from their aws/spans CloudWatch log groups.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Sensitive content disclosure via OpenTelemetry spans in AgentCore Python SDK","id":"CVE-2026-15737","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-namespace traffic interception via incorrect route precedence ordering in AWS Load Balancer Controller","id":"CVE-2026-15738"},"packages":[],"prev":{"headline":"Multiple SQL/DDL Injection and Arbitrary File Read Vulnerabilities in snowflake-sqlalchemy","id":"CVE-2026-15736"},"products":["bedrock-agentcore"],"published":"2026-07-16","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-07-16","vendors":["AWS"]},"summary":"Local authenticated users with CloudWatch access can read sensitive prompts and responses logged in OpenTelemetry spans by the AWS Bedrock AgentCore Python SDK.","url":"https://insights.sbomify.com/CVE-2026-15737/"}