5.9 CVE-2026-1778
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.
https://nvd.nist.gov/vuln/detail/CVE-2026-1778
Categories
CWE-295 : Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate. Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key. If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname. A Go framework for robotics, drones, and IoT devices skips verification of root CA certificates by default. Chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -> CWE-561 (Dead Code) -> CWE-295 (Improper Certificate Validation) -> CWE-393 (Return of Wrong Status Code) -> CWE-300 (Channel Accessible by Non-Endpoint). The code's whitespace indentation did not reflect the actual control flow (CWE-1114) and did not explicitly delimit the block (CWE-483), which could have made it more difficult for human code auditors to detect the vulnerability. Chain: router's firmware update procedure uses curl with "-k" (insecure) option that disables certificate validation (CWE-295), allowing adversary-in-the-middle (AITM) compromise with a malicious firmware image (CWE-494). Verification function trusts certificate chains in which the last certificate is self-signed. Web browser uses a TLS-related function incorrectly, preventing it from verifying that a server's certificate is signed by a trusted certification authority (CA) Web browser does not check if any intermediate certificates are revoked. Operating system does not check Certificate Revocation List (CRL) in some cases, allowing spoofing using a revoked certificate. Mobile banking application does not verify hostname, leading to financial loss. Cloud-support library written in Python uses incorrect regular expression when matching hostname. Web browser does not correctly handle '' character (NUL) in Common Name, allowing spoofing of https sites. Smartphone device does not verify hostname, allowing spoofing of mail services. Application uses third-party library that does not validate hostname. Cloud storage management application does not validate hostname. Java library uses JSSE SSLSocket and SSLEngine classes, which do not verify the hostname. chain: incorrect calculation allows attackers to bypass certificate checks. LDAP client accepts certificates even if they are not from a trusted CA. chain: DNS server does not correctly check return value from the OpenSSL EVP_VerifyFinal function allows bypass of validation of the certificate chain. chain: product checks if client is trusted when it intended to check if the server is trusted, allowing validation of signed code. Cryptographic API, as used in web browsers, mail clients, and other software, does not properly validate Basic Constraints. chain: OS package manager does not check properly check the return value, allowing bypass using a revoked certificate.
References
ff89ba41-3aa1-4d27-914a-91399e9639e5
AFFECTED (from MITRE)
| Vendor |
Product |
Versions |
| AWS |
SageMaker Python SDK |
- 3.1.1 [unaffected]
- 2.256.0 [unaffected]
|
| © 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. |
CPE
REMEDIATION
EXPLOITS
Exploit-db.com
| id |
description |
date |
|
| No known exploits |
POC Github
Other Nist (github, ...)
CAPEC
Common Attack Pattern Enumerations and Classifications
| id |
description |
severity |
| 459 |
Creating a Rogue Certification Authority Certificate
An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority. [Craft Certificates] The adversary crafts two different, but valid X.509 certificates that when hashed with an insufficiently collision resistant hashing algorithm would yield the same value. [Send CSR to Certificate Authority] The adversary sends the CSR for one of the certificates to the Certification Authority which uses the targeted hashing algorithm. That request is completely valid and the Certificate Authority issues an X.509 certificate to the adversary which is signed with its private key. [Insert Signed Blob into Unsigned Certificate] The adversary takes the signed blob and inserts it into the second X.509 certificate that the attacker generated. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob is valid in the second certificate. The result is two certificates that appear to be signed by a valid certificate authority despite only one having been signed. |
Very High |
| 475 |
Signature Spoofing by Improper Validation
An adversary exploits a cryptographic weakness in the signature verification algorithm implementation to generate a valid signature without knowing the key. |
High |
Cybersecurity needs ?
Strengthen software security from the outset with our DevSecOps expertise
Integrate security right from the start of the software development cycle for more robust applications and greater customer confidence.
Our team of DevSecOps experts can help you secure your APIs, data pipelines, CI/CD chains, Docker containers and Kubernetes deployments.
Discover this offer
