Trendyol kafka-konsumer 2.3.3 before 2.6.18 Denial of Service via Batch Consumer Panic
Affects Trendyol kafka-konsumer from 2.3.3 before 2.6.18 when batch consumers set a positive MessageGroupByteSizeLimit. The fix is in 2.6.18.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.6.18
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. BatchConfiguration.MessageGroupByteSizeLimit is enabled (positive value) in batch mode Batch consumers configured with a positive MessageGroupByteSizeLimit The oversized record must also be within the Kafka broker and reader size limits
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Trendyol kafka-konsumer library, a Go package for consuming Kafka messages, is affected by a bug in its batch consumer. An attacker who can remotely publish messages to the consumed topic, which requires some login, can send one oversized record that crashes the consumer and causes it to keep crashing, denying service.
Read the original description
Trendyol kafka-konsumer from 2.3.3 before 2.6.18 contains a denial of service vulnerability in batch_consumer.go that panics when a single record exceeds MessageGroupByteSizeLimit. Attackers able to produce to the consumed topic can publish one oversized record that terminates the consumer before offset commit, causing a persistent crash loop.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
BatchConfiguration.MessageGroupByteSizeLimit is enabled (positive value) in batch mode Batch consumers configured with a positive MessageGroupByteSizeLimit The oversized record must also be within the Kafka broker and reader size limitsUpgrade to a fixed version: 2.6.18.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Trendyol kafka-konsumer
From 2.3.3 · fixed in 2.6.18
Evidence 5
- Advisory
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124465
Is CVE-2026-124465 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A record larger than the configured byte-size limit makes a batch consumer panic, which terminates the consumer process. If the same unacknowledged record is replayed, the process can keep crashing in a loop.Source: github.com
Which versions are affected by CVE-2026-124465?
kafka-konsumer: from 2.3.3 before 2.6.18.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 2.3.3 up to but not including 2.6.18 are in scope. The setup involves batch mode with BatchConfiguration.MessageGroupByteSizeLimit set to a positive value, and the oversized record must also be within the Kafka broker and reader size limits. To check, look at the library version in the project's dependency file and at the BatchConfiguration settings in the consumer config.Source: github.com
How do I fix CVE-2026-124465?
Upgrade kafka-konsumer to version 2.6.18 or later.Source: github.com