CVE-2026-92943
CVE-2026-92943 is a high-severity vulnerability with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-297.
Key facts
- Severity: High (CVSS 3.x base score 8.1)
- CVSS v4: 9.2
- EPSS exploit prediction: 0% (30th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-297
- Published:
- Last modified:
Description
Improper validation of certificate with host mismatch in the MQTT client TLS connection layer in AWS IoT Device SDK for Python 1.5.3 through 1.6.0 on Python 3.7 and later might allow an adversary-in-the-middle actor to impersonate the AWS IoT Core endpoint, read device telemetry, and inject arbitrary MQTT messages that the device processes as authentic, via a certificate issued for an unrelated hostname by a certificate authority present in the device trust store. To remediate this issue, users should upgrade to version 1.6.1.
Frequently asked questions
- What is CVE-2026-92943?
- Improper validation of certificate with host mismatch in the MQTT client TLS connection layer in AWS IoT Device SDK for Python 1.5.3 through 1.6.0 on Python 3.7 and later might allow an adversary-in-the-middle actor to impersonate the AWS IoT Core endpoint, read device telemetry, and inject arbitrary MQTT messages that the device processes as authentic, via a certificate issued for an unrelated hostname by a certificate authority present in the device trust store. To remediate this issue, users should upgrade to version 1.6.1.
- How severe is CVE-2026-92943?
- CVE-2026-92943 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2026-92943 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2026-92943?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2026-92943 published?
- CVE-2026-92943 was published on 2026-09-17 and last updated on 2026-09-18.
References
- https://aws.amazon.com/security/security-bulletins/2026-114-aws/
- https://github.com/aws/aws-iot-device-sdk-python/releases/tag/v1.6.1
- https://github.com/aws/aws-iot-device-sdk-python/security/advisories/GHSA-g7vp-3rxx-v25r
- https://pypi.org/project/AWSIoTPythonSDK/1.6.1/
Other CWE-297 vulnerabilities
- CVE-2025-46408 — Critical (CVSS 9.8): An issue was discovered in the methods push.lite.avtech.com.AvtechLib.GetHttpsResponse and…
- CVE-2026-15925 — Critical (CVSS 9.2): Improper TLS hostname verification in Snowflake Connector for Python versions prior to 4.7.1 and 3.18.1 may have…
- CVE-2026-48144 — Critical (CVSS 9.1): Improper Validation of Certificate with Host Mismatch vulnerability in Apache Thrift c_glib bindings. This issue…
- CVE-2025-68637 — Critical (CVSS 9.1): The Uniffle HTTP client is configured to trust all SSL certificates and disables hostname verification by default.…
- CVE-2026-35563 — High (CVSS 8.5): It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate…
- CVE-2025-3501 — High (CVSS 8.2): A flaw was found in Keycloak. By setting a verification policy to 'ALL', the trust store certificate verification is…