CVE-2026-10143

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-36128 (ENISA EUVD) · GHSA-2jcm-hq8r-84wx (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 10, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
Patch available. Sources: github_pr, github_commit.
Web page

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 pull request

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 pull request

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17861819812026-08-12redhat
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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-kafka2.0.1-2 ... 2.0.2-9 (13 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-kafka2.0.2-10 ... 2.2.3-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-kafka2.0.2-10 ... 2.2.3-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-kafka2.0.2-10, 2.0.2-11, 2.0.2-9
  • every version up to 2.0.2-12: fixed in 2.0.2-12
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
kafka-python0.9.0 ... 2.3.1 (68 versions)
  • every version up to 2.3.2: fixed in 2.3.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 398 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 298 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-10143?
CVE-2026-10143 is a high-severity vulnerability; its CVE record was 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.process_server_first_message()…
When was CVE-2026-10143 made public?
CVE-2026-10143 was made public on June 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 10, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-10143 actively exploited?
CVE-2026-10143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10143?
CVE-2026-10143 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10143?
A fix for CVE-2026-10143 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-10143 are linked in the Vendor Advisories panel on this page.

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.