Skip to content
VulniPulse
Advisory severityMedium5.3Apache Software Foundation

Medium [CVE-2026-33558] Apache Kafka: Information exposure vulnerability has been identified in Apache Kafka.

This medium-severity Apache Software Foundation advisory covers CVE-2026-33558 affecting Apache Kafka.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-33558 Source published Source updated

VulniPulse record published Record updated

Affected products & platforms
Apache Software FoundationMessagingKafka
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Information exposure vulnerability has been identified in Apache Kafka.

The NetworkClient component will output entire requests and responses information in the DEBUG log level in the logs. By default, the log level is set to INFO level.

If the DEBUG level is enabled, the sensitive information will be exposed via the requests and responses output log. The entire lists of impacted requests and responses are:

  • AlterConfigsRequest
  • AlterUserScramCredentialsRequest
  • ExpireDelegationTokenRequest
  • IncrementalAlterConfigsRequest
  • RenewDelegationTokenRequest
  • SaslAuthenticateRequest
  • createDelegationTokenResponse
  • describeDelegationTokenResponse
  • SaslAuthenticateResponse

This issue affects Apache Kafka: from any version supported the listed API above through v3.9.1, v4.0.0. We advise the Kafka users to upgrade to v3.9.2, v4.0.1, or later to avoid this vulnerability.

Affected versions
  • through 3.9.1

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 3 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.