CVE-2026-22860 remediation guide

rack rack, Logging Subsystem for Red Hat OpenShift, Red Hat 3scale API Management Platform 2

Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory`’s path check used a string prefix match on the expanded path. A request like `/../root_example/` can escape the configured root if the target path starts with the root string, allowing directory listing outside the intended root. Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.

Open CVE record

Productrack rack, Logging Subsystem for Red Hat OpenShift, Red Hat 3scale API Management Platform 2

Affected versions>= < 2.2.22, >= >= 3.0.0.beta1, < 3.1.20, >= >= 3.2.0, < 3.2.5, < 2.2.22, >= 3.0.0 < 3.1.20, >= 3.2.0 < 3.2.5

Fixed versions2.2.22, 3.1.20, 3.2.5

Priority basisReview · CVSS 7.5 · EPSS 0.66%

Identify the affected asset

Confirm whether rack rack, Logging Subsystem for Red Hat OpenShift, Red Hat 3scale API Management Platform 2 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.

Validate the affected-version match

Compare the deployed version with the affected range: >= < 2.2.22, >= >= 3.0.0.beta1, < 3.1.20, >= >= 3.2.0, < 3.2.5, < 2.2.22, >= 3.0.0 < 3.1.20, >= 3.2.0 < 3.2.5. Treat incomplete inventory results as unresolved.

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.

Apply supported remediation

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

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.