CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-2229 remediation guide

undici undici, Cryostat 4 on RHEL 9, Red Hat Enterprise Linux 10

ImpactThe undici WebSocket client is vulnerable to a denial-of-service attack due to improper validation of the server_max_window_bits parameter in the permessage-deflate extension. When a WebSocket client connects to a server, it automatically advertises support for permessage-deflate compression. A malicious server can respond with an out-of-range server_max_window_bits value (outside zlib's valid range of 8-15). When the server subsequently sends a compressed frame, the client attempts to create a zlib InflateRaw instance with the invalid windowBits value, causing a synchronous RangeErro...

Open CVE record
Productundici undici, Cryostat 4 on RHEL 9, Red Hat Enterprise Linux 10
Affected versions>= < 6.24.0, 7.0.0 < 7.24.0, < 6.24.0, >= 7.0.0 < 7.24.0
Fixed versions6.24.0, 7.24.0
Priority basisReview · CVSS 7.5 · EPSS 0.87%
01

Identify the affected asset

Confirm whether undici undici, Cryostat 4 on RHEL 9, Red Hat Enterprise Linux 10 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 6.24.0, 7.0.0 < 7.24.0, < 6.24.0, >= 7.0.0 < 7.24.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.24.0, 7.24.0. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.