{"answers":{"affected":"5 open source packages ship an affected version, including sagemaker.","exploited":"There is no known exploitation of CVE-2026-1778 in the wild and no public exploit code.","fix":"Upgrade sagemaker to a fixed version for your release line: 2.256.0 or 3.1.1.","what":"CVE-2026-1778 is a high-severity vulnerability in AWS SageMaker Python SDK, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-1778 and fix it if it is affected.\n\nWhat it is: CVE-2026-1778 is a high-severity vulnerability in AWS SageMaker Python SDK, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-1778 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sagemaker (PyPI): affected all versions; fixed in 2.256.0, 3.1.1\n- sagemaker (PyPI): affected all versions; fixed in 2.256.0\n- sagemaker (PyPI): affected all versions; fixed in 2.256.0\n- sagemaker (PyPI): affected from 3.0; fixed in 3.1.1\n- sagemaker (PyPI): affected from 3.0; fixed in 3.1.1\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-1778/ (Markdown: https://insights.sbomify.com/CVE-2026-1778/index.md)","id":"CVE-2026-1778","markdown":"https://insights.sbomify.com/CVE-2026-1778/index.md","name":"CVE-2026-1778","record":{"aliases":["GHSA-62rc-f4v9-h543","PYSEC-2026-1886"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SageMaker Python SDK","requires_auth":"none","summary":"The SageMaker Python SDK disables TLS verification for Triton models, allowing man-in-the-middle attacks against HTTPS connections.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Amazon SageMaker Python SDK before v3.1.1 or v2.256.0 disables TLS certificate verification for HTTPS connections made by the service when a Triton Python model is imported, incorrectly allowing for requests with invalid and self-signed certificates to succeed.","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":"TLS disabled by default in select aws/sagemaker-python-sdk configurations","id":"CVE-2026-1778","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":5,"n_references":4,"next":{"headline":"User Registration \u0026 Membership \u003c= 5.1.2 - Authentication Bypass","id":"CVE-2026-1779"},"packages":[{"ecosystem":"PyPI","fixed":["2.256.0","3.1.1"],"introduced":["0","3.0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"PYSEC-2026-1886"},{"ecosystem":"PyPI","fixed":["2.256.0"],"introduced":["0"],"last_affected":[],"package":"sagemaker","purl":null,"source":"GHSA-62rc-f4v9-h543"},{"ecosystem":"PyPI","fixed":["2.256.0"],"introduced":["0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"GHSA-62rc-f4v9-h543"},{"ecosystem":"PyPI","fixed":["3.1.1"],"introduced":["3.0"],"last_affected":[],"package":"sagemaker","purl":null,"source":"GHSA-62rc-f4v9-h543"},{"ecosystem":"PyPI","fixed":["3.1.1"],"introduced":["3.0"],"last_affected":[],"package":"sagemaker","purl":"pkg:pypi/sagemaker","source":"GHSA-62rc-f4v9-h543"}],"prev":{"headline":"Cleartext transmission of sensitive materials in aws/sagemaker-python-sdk","id":"CVE-2026-1777"},"products":["SageMaker Python SDK"],"published":"2026-02-02","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":"partial"},"state":"PUBLISHED","updated":"2026-02-04","vendors":["AWS"]},"summary":"The SageMaker Python SDK disables TLS verification for Triton models, allowing man-in-the-middle attacks against HTTPS connections.","url":"https://insights.sbomify.com/CVE-2026-1778/"}