kafka-python prior to 2.3.2 contains a denial-of-service vulnerability in SCRAM authentication handling that allows a malicious or machine-in-the-middle broker to freeze the client event loop by supplying an excessively large iteration count. In scram.py, ScramClient.process_server_first_message() passes the broker-controlled SCRAM iteration count directly to hashlib.pbkdf2_hmac() without validation, blocking producer sends, consumer polls, admin operations, and heartbeats, which can cause consumer group eviction and repeated reconnect failures.
CVE-2026-10143
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-11. the CNA's CVSS baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/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 computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
June 10, 2026
Last Modified
August 24, 2026
Advisory Details (4)
Auto-updated Jun 11, 2026kafka-python prior to 2.3.2 DoS via SCRAM Iteration Count in scram.py | Advisories | VulnCheck
https://www.vulncheck.com/advisories/kafka-python-prior-to-dos-via-scram-iteration-count-in-scram-pykafka.net: Validate SASL/SCRAM iterations
Fix merged in dpkp/kafka-python PR #3026 on 2026-06-03 — awaiting tagged release
https://github.com/dpkp/kafka-python/pull/3026KafkaProtocol: validate network frame size; retore log-prefix; fix 0.8.2 quirk check
Fix merged in dpkp/kafka-python PR #3019 on 2026-05-30 — awaiting tagged release
https://github.com/dpkp/kafka-python/pull/3019commit 6e4831444f97 (dpkp/kafka-python)
Fix landed in dpkp/kafka-python commit 6e4831444f97 — awaiting tagged release
https://github.com/dpkp/kafka-python/commit/6e4831444f972d169cdd11f5c8d50333cea3f19bVendor Advisories for CVE-2026-10143(6)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:42796Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.15.6
- RHSA-2026:41066Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.16.5
- RHSA-2026:33683Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.10.23
- RHSA-2026:30076Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.12.19
- RHSA-2026:28571Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Quay 3.9.23
- GHSA-2jcm-hq8r-84wxGitHub Security AdvisoriesHigh
kafka-python prior to 2.3.2 contains a denial-of-service vulnerability in SCRAM authentication...
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | quay/quay-rhel8:1784351966 | 2026-07-21 | redhat |
| redhat | quay/quay-rhel9:1783955846 | 2026-07-16 | redhat |
| redhat | quay/quay-rhel8:1782487717 | 2026-06-30 | redhat |
| redhat | quay/quay-rhel8:1781937357 | 2026-06-25 | redhat |
| redhat | quay/quay-rhel8:1781878070 | 2026-06-23 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-kafka | 2.0.1-2 ... 2.0.2-9 (13 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-kafka | 2.0.2-10 ... 2.0.2-9 (10 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-kafka | 2.0.2-10, 2.0.2-11, 2.0.2-12, 2.0.2-9 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-kafka | 2.0.2-10, 2.0.2-11, 2.0.2-9 | 2.0.2-12 | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kafka-python | 0.9.0 ... 2.3.1 (68 versions) | 2.3.2 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 30× in last 7d / 152× 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.
Showing the most recent 100 of 315 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 01:21 UTCEG score recompute
- 2026-08-25 01:21 UTCVendor advisory
- 2026-08-25 01:21 UTCGHSA enrichment
- 2026-08-24 12:21 UTCEG score recompute
- 2026-08-24 12:21 UTCVendor advisory
- 2026-08-24 12:20 UTCGHSA enrichment
- 2026-08-23 23:45 UTCVendor advisory
- 2026-08-23 23:45 UTCGHSA enrichment
- 2026-08-23 10:45 UTCEG score recompute
- 2026-08-23 10:45 UTCVendor advisory
- 2026-08-23 10:45 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:55 UTCEG score recompute
- 2026-08-21 23:55 UTCVendor advisory
- 2026-08-21 23:55 UTCGHSA enrichment
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 10:55 UTCEG score recompute
- 2026-08-21 10:55 UTCVendor advisory
- 2026-08-21 10:55 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:52 UTCVendor advisory
- 2026-08-20 21:52 UTCGHSA enrichment
- 2026-08-20 08:52 UTCEG score recompute
- 2026-08-20 08:52 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-20 08:52 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 14:55 UTCEG score recompute
- 2026-08-19 14:55 UTCVendor advisory
- 2026-08-19 14:55 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 12:19 UTCEG score recompute
- 2026-08-17 12:19 UTCVendor advisory
- 2026-08-17 12:19 UTCGHSA enrichment
- 2026-08-17 12:12 UTCEG score recompute
- 2026-08-17 12:12 UTCVendor advisory
- 2026-08-17 12:12 UTCGHSA enrichment
- 2026-08-16 23:28 UTCEG score recompute
- 2026-08-16 23:28 UTCVendor advisory
- 2026-08-16 23:28 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:57 UTCEG score recompute
- 2026-08-16 07:57 UTCVendor advisory
- 2026-08-16 07:57 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 18:58 UTCVendor advisory
- 2026-08-15 18:58 UTCGHSA enrichment
- 2026-08-15 05:58 UTCEG score recompute
- 2026-08-15 05:58 UTCVendor advisory
- 2026-08-15 05:58 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 16:57 UTCVendor advisory
- 2026-08-14 16:57 UTCGHSA enrichment
- 2026-08-14 03:46 UTCEG score recompute
- 2026-08-14 03:46 UTCVendor advisory
- 2026-08-14 03:46 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 14:46 UTCVendor advisory
- 2026-08-13 14:46 UTCGHSA enrichment
- 2026-08-13 01:36 UTCEG score recompute
- 2026-08-13 01:36 UTCVendor advisory
- 2026-08-13 01:36 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 12:36 UTCEG score recompute
- 2026-08-12 12:36 UTCVendor advisory
- 2026-08-12 12:36 UTCGHSA enrichment
- 2026-08-12 12:11 UTCVendor advisory
- 2026-08-12 12:11 UTCGHSA enrichment
- 2026-08-12 03:28 UTCVendor advisory
- 2026-08-12 03:28 UTCGHSA enrichment
- 2026-08-11 14:28 UTCEG score recompute
- 2026-08-11 14:28 UTCVendor advisory
- 2026-08-11 14:28 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 01:25 UTCEG score recompute
- 2026-08-11 01:25 UTCVendor advisory
- 2026-08-11 01:25 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 12:25 UTCVendor advisory
- 2026-08-10 12:25 UTCGHSA enrichment
- 2026-08-10 04:00 UTCVendor advisory
- 2026-08-10 04:00 UTCGHSA enrichment
- 2026-08-09 15:00 UTCEG score recompute
- 2026-08-09 15:00 UTCVendor advisory
- 2026-08-09 15:00 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:01 UTCEG score recompute
- 2026-08-09 02:01 UTCVendor advisory
- 2026-08-09 02:01 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:01 UTCVendor advisory
- 2026-08-08 13:01 UTCGHSA enrichment
- 2026-08-08 00:01 UTCEG score recompute
- 2026-08-08 00:01 UTCVendor advisory
- 2026-08-08 00:01 UTCGHSA enrichment
- 2026-08-07 11:01 UTCVendor advisory
- 2026-08-07 11:01 UTCGHSA enrichment
- 2026-08-06 22:01 UTCEG score recompute
- 2026-08-06 22:01 UTCVendor advisory
- 2026-08-06 22:01 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-10143?
When was CVE-2026-10143 disclosed?
Is CVE-2026-10143 actively exploited?
What is the CVSS score of CVE-2026-10143?
How do I remediate CVE-2026-10143?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10143
Is Your Infrastructure Affected by CVE-2026-10143?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.