CVE-2026-10143 — kafka-python
Fix: dpkp/kafka-python@6e48314CVE-2026-10143 is a Uncontrolled Resource Consumption vulnerability in kafka-python. A fix is available for kafka-python — see the affected versions and patch details below.
kafka-python prior to 2.3.2 DoS via SCRAM Iteration Count in scram.py
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-10143.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
kafka-pythonReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | kafka-python | all versions | 2.3.2pip install --upgrade 'kafka-python==2.3.2' |
Affected Products
kafka-pythondpkpDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kafka-python, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kafka-python to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-10143 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2026-10143 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Quay 3.10 | quay/quay-rhel8:1782487717 | RHSA-2026:33683 |
| Red Hat Quay 3.12 | quay/quay-rhel8:1781937357 | RHSA-2026:30076 |
| Red Hat Quay 3.14 | quay/quay-rhel8:1788593843 | RHSA-2026:70267 |
| Red Hat Quay 3.15 | quay/quay-rhel8:1784351966 | RHSA-2026:42796 |
| Red Hat Quay 3.16 | quay/quay-rhel9:1783955846 | RHSA-2026:41066 |
| Red Hat Quay 3.17 | quay/quay-rhel9:1786181981 | RHSA-2026:54395 |
| Red Hat Quay 3.9 | quay/quay-rhel8:1781878070 | RHSA-2026:28571 |
Frequently Asked Questions
Is CVE-2026-10143 in your dependencies?
Find it across PyPI, including transitive dependencies.