Improper Validation of Specified Index, Position, or Offset in Input Affecting opensearch-3-repository-gcs package, versions <3.6.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (42nd 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-16298776
  • published26 Apr 2026
  • disclosed20 Apr 2026

Introduced: 20 Apr 2026

NewCVE-2026-33557  (opens in a new tab)
CWE-1285  (opens in a new tab)

How to fix?

Upgrade Minimos:latest opensearch-3-repository-gcs to version 3.6.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.

A possible security vulnerability has been identified in Apache Kafka.

By default, the broker property sasl.oauthbearer.jwt.validator.class is set to org.apache.kafka.common.security.oauthbearer.DefaultJwtValidator. It accepts any JWT token without validating its signature, issuer, or audience. An attacker can generate a JWT token from any issuer with the preferred_username set to any user, and the broker will accept it.

We advise the Kafka users using kafka v4.1.0 or v4.1.1 to set the config sasl.oauthbearer.jwt.validator.class to org.apache.kafka.common.security.oauthbearer.BrokerJwtValidator explicitly to avoid this vulnerability. Since Kafka v4.1.2 and v4.2.0 and later, the issue is fixed and will correctly validate the JWT token.

CVSS Base Scores

version 3.1