CVE-2026-10143

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-11. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
41%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

kafka-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-py
github_pr

kafka.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/3026
github_pr

KafkaProtocol: 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/3019
github_commit

commit 6e4831444f97 (dpkp/kafka-python)

Fix landed in dpkp/kafka-python commit 6e4831444f97 — awaiting tagged release

https://github.com/dpkp/kafka-python/commit/6e4831444f972d169cdd11f5c8d50333cea3f19b

Vendor 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.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatquay/quay-rhel8:17824877172026-06-30redhat
redhatquay/quay-rhel8:17819373572026-06-25redhat
redhatquay/quay-rhel8:17818780702026-06-23redhat

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
kafka-python0.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 17× in last 7d / 108× 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 165 total refreshes for this CVE.

  1. 2026-07-27 09:55 UTCVendor advisory
  2. 2026-07-27 09:55 UTCGHSA enrichment
  3. 2026-07-26 20:55 UTCEG score recompute
  4. 2026-07-26 20:55 UTCVendor advisory
  5. 2026-07-26 20:55 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 05:18 UTCEG score recompute
  9. 2026-07-26 05:18 UTCVendor advisory
  10. 2026-07-26 05:18 UTCGHSA enrichment
  11. 2026-07-25 14:17 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:04 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:24 UTCEPSS rescore
  17. 2026-07-20 17:08 UTCEPSS rescore
  18. 2026-07-19 14:30 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-17 06:43 UTCVendor advisory
  22. 2026-07-17 06:43 UTCGHSA enrichment
  23. 2026-07-16 17:02 UTCEPSS rescore
  24. 2026-07-16 11:27 UTCVendor advisory
  25. 2026-07-16 11:27 UTCGHSA enrichment
Show 75 more
  1. 2026-07-15 21:35 UTCVendor advisory
  2. 2026-07-15 21:35 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 07:59 UTCVendor advisory
  5. 2026-07-15 07:59 UTCGHSA enrichment
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 15:49 UTCVendor advisory
  8. 2026-07-14 15:49 UTCGHSA enrichment
  9. 2026-07-14 02:41 UTCVendor advisory
  10. 2026-07-14 02:41 UTCGHSA enrichment
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 13:41 UTCVendor advisory
  13. 2026-07-13 13:41 UTCGHSA enrichment
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 22:58 UTCVendor advisory
  16. 2026-07-12 22:58 UTCGHSA enrichment
  17. 2026-07-12 09:42 UTCVendor advisory
  18. 2026-07-12 09:42 UTCGHSA enrichment
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-11 20:41 UTCVendor advisory
  21. 2026-07-11 20:41 UTCGHSA enrichment
  22. 2026-07-11 08:27 UTCEPSS rescore
  23. 2026-07-11 07:41 UTCVendor advisory
  24. 2026-07-11 07:41 UTCGHSA enrichment
  25. 2026-07-10 17:59 UTCVendor advisory
  26. 2026-07-10 17:59 UTCGHSA enrichment
  27. 2026-07-09 19:10 UTCEPSS rescore
  28. 2026-07-09 13:36 UTCVendor advisory
  29. 2026-07-09 13:36 UTCGHSA enrichment
  30. 2026-07-08 23:56 UTCVendor advisory
  31. 2026-07-08 23:56 UTCGHSA enrichment
  32. 2026-07-08 15:15 UTCEPSS rescore
  33. 2026-07-08 15:15 UTCEPSS rescore
  34. 2026-07-08 10:55 UTCVendor advisory
  35. 2026-07-08 10:55 UTCGHSA enrichment
  36. 2026-07-07 21:49 UTCVendor advisory
  37. 2026-07-07 21:49 UTCGHSA enrichment
  38. 2026-07-07 13:46 UTCEPSS rescore
  39. 2026-07-07 03:28 UTCVendor advisory
  40. 2026-07-07 03:28 UTCGHSA enrichment
  41. 2026-07-06 16:27 UTCEPSS rescore
  42. 2026-07-06 02:40 UTCVendor advisory
  43. 2026-07-06 02:40 UTCGHSA enrichment
  44. 2026-07-06 02:23 UTCEPSS rescore
  45. 2026-07-05 13:40 UTCVendor advisory
  46. 2026-07-05 13:40 UTCGHSA enrichment
  47. 2026-07-05 02:30 UTCEPSS rescore
  48. 2026-07-05 02:30 UTCEPSS rescore
  49. 2026-07-05 00:40 UTCVendor advisory
  50. 2026-07-05 00:39 UTCGHSA enrichment
  51. 2026-07-04 11:39 UTCVendor advisory
  52. 2026-07-04 11:39 UTCGHSA enrichment
  53. 2026-07-04 06:31 UTCEPSS rescore
  54. 2026-07-03 14:58 UTCVendor advisory
  55. 2026-07-03 14:58 UTCGHSA enrichment
  56. 2026-07-03 01:56 UTCVendor advisory
  57. 2026-07-03 01:56 UTCGHSA enrichment
  58. 2026-07-02 12:54 UTCVendor advisory
  59. 2026-07-02 12:54 UTCGHSA enrichment
  60. 2026-07-01 23:54 UTCVendor advisory
  61. 2026-07-01 23:54 UTCGHSA enrichment
  62. 2026-07-01 15:06 UTCEPSS rescore
  63. 2026-07-01 15:06 UTCEPSS rescore
  64. 2026-07-01 10:54 UTCVendor advisory
  65. 2026-07-01 10:54 UTCGHSA enrichment
  66. 2026-06-30 23:22 UTCEPSS rescore
  67. 2026-06-30 21:50 UTCVendor advisory
  68. 2026-06-30 21:50 UTCGHSA enrichment
  69. 2026-06-30 08:46 UTCVendor advisory
  70. 2026-06-30 08:46 UTCGHSA enrichment
  71. 2026-06-29 19:46 UTCVendor advisory
  72. 2026-06-29 19:46 UTCGHSA enrichment
  73. 2026-06-29 06:46 UTCVendor advisory
  74. 2026-06-29 06:46 UTCGHSA enrichment
  75. 2026-06-28 16:15 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-10143?
CVE-2026-10143 is a high vulnerability published on June 10, 2026. 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.processserverfirstmessage()…
When was CVE-2026-10143 disclosed?
CVE-2026-10143 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10143 actively exploited?
CVE-2026-10143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 59.1% of all scored CVEs.
What is the CVSS score of CVE-2026-10143?
CVE-2026-10143 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-10143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10143, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10143

Explore →

Is Your Infrastructure Affected by CVE-2026-10143?

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

Start Free Scan →Browse All CVEs