Information Exposure Through Server Log Files Affecting opensearch-3-repository-gcs package, versions <3.4.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.14% (35th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-OPENSEARCH3REPOSITORYGCS-16299312
  • published26 Apr 2026
  • disclosed20 Apr 2026

Introduced: 20 Apr 2026

NewCVE-2026-33558  (opens in a new tab)
CWE-533  (opens in a new tab)

How to fix?

Upgrade Minimos:latest opensearch-3-repository-gcs to version 3.4.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream opensearch-3-repository-gcs package and not the opensearch-3-repository-gcs package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.