LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22860: Rack has a Directory Traversal via Rack:Directory

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Rack can accidentally expose directory listings outside the intended folder when Rack::Directory is enabled. An unauthenticated remote requester may read files from a nearby path that shares the configured root prefix. The known impact is confidentiality loss, not file modification or service outage.

Executive priority

Treat as high priority for internet-facing Ruby services that expose directory listings. Prioritize upgrade or disabling Rack::Directory because the issue can disclose sensitive files without authentication.

Technical view

Before Rack 2.2.22, 3.1.20, and 3.2.5, Rack::Directory validated expanded paths with a string prefix check. Certain parent-directory paths could pass when the destination began with the configured root string, causing directory traversal and unintended listing outside the root.

Likely exposure

Exposure is likely limited to Ruby applications using affected Rack versions and enabling Rack::Directory or a framework path that invokes it. General Rack usage alone is not enough evidence of exposure from the provided sources.

Exploitation context

The CVSS vector is network-accessible, low complexity, unauthenticated, and no user interaction. The bundle says KEV is false, and no cited source in the bundle confirms active exploitation.

Researcher notes

The core issue maps to CWE-22 and CWE-548. The provided sources identify fixed upstream versions and the vulnerable path-check pattern. Product-specific downstream impact is incomplete in the bundle, so distribution advisories should be checked before asserting package status.

Mitigation direction

  • Upgrade Rack to 2.2.22, 3.1.20, 3.2.5, or later supported versions.
  • Disable Rack::Directory where directory listing is not required.
  • Restrict public access to any route serving directory listings.
  • Check vendor-specific guidance, especially Red Hat advisories, for packaged Rack status.

Validation and detection

  • Inventory deployed Rack versions across applications and container images.
  • Review application configuration and middleware for Rack::Directory usage.
  • Confirm exposed routes do not provide unintended directory listings.
  • Run regression checks after upgrade against intended directory-root boundaries.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-548: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22860 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-22860Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPrubygem-rack: Rack Directory Traversal via Rack:Directory
other:Red Hat severity ratingcvssV3_1
  • 2026-02-18T20:02:32.128Z: Reported to Red Hat.
  • 2026-02-18T18:45:02.095Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
rackrack< 2.2.22, >= 3.0.0.beta1, < 3.1.20, >= 3.2.0, < 3.2.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.