Improper Check for Unusual or Exceptional Conditions Affecting sonarqube package, versions <26.8.0.126808-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.32% (25th 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-CHAINGUARDLATEST-SONARQUBE-19758547
  • published13 Sept 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

NewCVE-2026-75595  (opens in a new tab)
CWE-754  (opens in a new tab)

How to fix?

Upgrade Chainguard sonarqube to version 26.8.0.126808-r3 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream sonarqube package and not the sonarqube package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Netty is an asynchronous, event-driven network application framework. Prior to 4.1.137.Fina and 4.2.17.Final, io.netty.handler.ssl.SslClientHelloHandler#decode checks the wrong offset before reading the four-byte TLS handshake header, so a ClientHello whose handshake header spans records can cause an IndexOutOfBoundsException and invoke select(ctx, null). This selects the default SslContext instead of the SNI-specific context. In deployments where per-SNI clientAuth=REQUIRE is the sole mutual TLS gate, the default SslContext uses clientAuth=NONE or clientAuth=OPTIONAL, and no application-layer certificate verification exists, an unauthenticated remote attacker can bypass the protected route's mutual TLS requirement. This issue is fixed in versions 4.1.137.Final and 4.2.17.Final.