ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-68xw-fqpj-h922

DoS in zstd decompression

Published Oct 22, 2026 · catalog updated Oct 22, 2026 · DoS in zstd decompression

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-68xw-fqpj-h922. A missing EPSS score is not a low risk. Compare DoS in zstd decompression with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (DoS in zstd decompression).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
maven org.opensearch.plugin:opensearch-security · maven org.opensearch:opensearch

### Summary A single HTTP request with a header and a non-empty body causes the receiving OpenSearch node to terminate its JVM via . OpenSearch 2.19.4 through 2.19.6 and the opensearch-security plugin 2.19.4.0 through 2.19.6.0 are affected. 2.19.0–2.19.3 and 3.x are not. ### Details Netty's (since 4.1.125.Final) calls as its first operation on inbound bytes. Every 2.19.x release pins , which does not contain that method (added in ). Netty's availability check ( ) only confirms the class loads and the native library initializes, so still advertises and builds the decoder. The first decode then throws , which OpenSearch's uncaught-exception handling treats as fatal and answers with . Introduced in 2.19.4 by the netty bump from to (#19270). 3.x pins , which includes the method. Affected components: (default HTTP transport), (when selected via ), and opensearch-security's , which extends the same Netty class and decompresses only after successful authentication. ### Proof of concept Against a default 2.19.6 node (security plugin not installed): The node logs a fatal from and exits. With the security plugin installed, the same request sent over HTTPS with valid credentials produces the same result. ### Impact Availability only. Without the plugin, anyone who can reach the HTTP port can halt the node without authenticating (CVSS 7.5), and can repeat the request to keep it down. With the plugin, the request must first pass authentication. Any authenticated user can then halt the node without needing specific privileges (CVSS 6.5), and a cluster configured to accept anonymous requests is exposed to unauthenticated clients as well (CVSS 7.5). Halting skips JVM shutdown hooks. No confidentiality or integrity impact was identified.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • maven org.opensearch.plugin:opensearch-security>= 2.19.4.0, <= 2.19.6.0
  • maven org.opensearch:opensearch>= 2.19.4, <= 2.19.6

How to fix GHSA-68xw-fqpj-h922

  • Upgrade

    GHSA-68xw-fqpj-h922 lists a fix boundary at 2.19.6.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 2.19.6.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-68xw-fqpj-h922. A missing EPSS score is not a low risk. Compare DoS in zstd decompression with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 2.19.4.0, <= 2.19.6.0, >= 2.19.4, <= 2.19.6. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-248. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

OpenSearch security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 22, 2026 · Maintainer security tabs

    Detected

    ### Summary A single HTTP request with a header and a non-empty body causes the receiving OpenSearch node to terminate its JVM via . OpenSearch 2.19.4 through 2.19.6 and the opensearch-security plugin 2.19.4.0 through 2.19.6.0 are affected. 2.19.0–2.19.3 and 3.x are not. ### Details Netty's (since 4.1.125.Final) calls as its first operation on inbound bytes. Every 2.19.x release pins , which does

Sources

  • Maintainer security tabsVendor advisoryGHSA-68xw-fqpj-h922

    ### Summary A single HTTP request with a header and a non-empty body causes the receiving OpenSearch node to terminate its JVM via . OpenSearch 2.19.4 through 2.19.6 and the opensearch-security plugin 2.19.4.0 through 2.19.6.0 are affected. 2.19.0–2.19.3 and 3.x are not. ### Details Netty's (since 4.1.125.Final) calls as its first operation on inbound bytes. Every 2.19.x release pins , which does

    github.com

Freshness

Last verified in this catalog Oct 22, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026