{"answers":{"affected":"5 open source packages ship an affected version, including sagemaker.","exploited":"There is no known exploitation of CVE-2026-8596 in the wild and no public exploit code.","fix":"Upgrade sagemaker to a fixed version for your release line: 2.257.2 or 3.8.0.","what":"CVE-2026-8596 is a high-severity vulnerability in AWS Amazon SageMaker Python SDK, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8596 and fix it if it is affected.\n\nWhat it is: CVE-2026-8596 is a high-severity vulnerability in AWS Amazon SageMaker Python SDK, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8596 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2, 3.8.0\n- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2\n- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2\n- sagemaker (PyPI): affected from 3.0.0; fixed in 3.8.0\n- sagemaker (PyPI): affected from 3.0.0; fixed in 3.8.0\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-8596/ (Markdown: https://insights.sbomify.com/CVE-2026-8596/index.md)","id":"CVE-2026-8596","markdown":"https://insights.sbomify.com/CVE-2026-8596/index.md","name":"CVE-2026-8596","record":{"aliases":["GHSA-7hh5-prp2-mfh5","PYSEC-2026-3059"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SageMaker Python SDK","requires_auth":"high_privilege","summary":"Authenticated attackers can extract HMAC keys from API responses to forge signatures and execute code in inference containers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Cleartext storage of sensitive information in the ModelBuilder/Serve component in Amazon SageMaker Python SDK before v2.257.2 and v3 before v3.8.0 might allow a remote authenticated actor to extract the HMAC signing key from SageMaker API responses and forge valid integrity signatures for specially crafted model artifacts, achieving code execution in inference containers. This issue requires a remote authenticated actor with permissions to call SageMaker describe APIs and S3 write access to the model artifact path.\n\nTo remediate this issue, we recommend upgrading to Amazon SageMaker Python SDK v2.257.2 or v3.8.0 and rebuild any models previously created with ModelBuilder using the updated SDK.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cleartext storage of HMAC signing key in Amazon SageMaker Python SDK ModelBuilder/Serve path","id":"CVE-2026-8596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":5,"n_references":4,"next":{"headline":"Missing integrity verification in Triton inference handler in Amazon SageMaker Python SDK","id":"CVE-2026-8597"},"packages":[{"ecosystem":"PyPI","fixed":["2.257.2","3.8.0"],"introduced":["2.199.0","3.0.0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"PYSEC-2026-3059"},{"ecosystem":"PyPI","fixed":["2.257.2"],"introduced":["2.199.0"],"last_affected":[],"package":"sagemaker","purl":null,"source":"GHSA-7hh5-prp2-mfh5"},{"ecosystem":"PyPI","fixed":["2.257.2"],"introduced":["2.199.0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"GHSA-7hh5-prp2-mfh5"},{"ecosystem":"PyPI","fixed":["3.8.0"],"introduced":["3.0.0"],"last_affected":[],"package":"sagemaker","purl":null,"source":"GHSA-7hh5-prp2-mfh5"},{"ecosystem":"PyPI","fixed":["3.8.0"],"introduced":["3.0.0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"GHSA-7hh5-prp2-mfh5"}],"prev":{"headline":"Stored XSS in the table panel (TableNG)","id":"CVE-2026-8595"},"products":["Amazon SageMaker Python SDK"],"published":"2026-05-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["AWS"]},"summary":"Authenticated attackers can extract HMAC keys from API responses to forge signatures and execute code in inference containers.","url":"https://insights.sbomify.com/CVE-2026-8596/"}