CVE-2026-92943

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(low)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 17, 2026
Patch available. Sources: github, github_release.
github Patch Available

Improper validation of certificate with host mismatch in AWS IoT Device SDK for Python · Advisory · aws/aws-iot-device-sdk-python · GitHub

https://github.com/aws/aws-iot-device-sdk-python/security/advisories/GHSA-g7vp-3rxx-v25r
generic

CVE-2026-92943 - Improper validation of certificate with host mismatch in AWS IoT Device SDK for Python

https://aws.amazon.com/security/security-bulletins/2026-114-aws/
github_release Patch Available

v1.6.1

Patch available: aws/aws-iot-device-sdk-python v1.6.1

https://github.com/aws/aws-iot-device-sdk-python/releases/tag/v1.6.1
generic

AWSIoTPythonSDK · PyPI

https://pypi.org/project/AWSIoTPythonSDK/1.6.1/

Vendor Advisories for CVE-2026-92943(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 20:27 UTCEG score recompute
  3. 2026-09-17 20:05 UTCEG score recompute
  4. 2026-09-17 19:20 UTCEG score recompute
  5. 2026-09-17 19:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92943?
CVE-2026-92943 is a high vulnerability published on September 17, 2026. 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…
When was CVE-2026-92943 disclosed?
CVE-2026-92943 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92943 actively exploited?
CVE-2026-92943 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.0% of all scored CVEs.
What is the CVSS score of CVE-2026-92943?
CVE-2026-92943 has a CVSS v3 base score of 8.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-92943?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92943, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92943

Explore →

Is Your Infrastructure Affected by CVE-2026-92943?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs