How severe is GHSA-9xrj-h377-fr87?

No CVSS score has been assigned to GHSA-9xrj-h377-fr87 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9xrj-h377-fr87?

GHSA-9xrj-h377-fr87 affects the following packages: activestorage (RubyGems), activestorage (RubyGems), activestorage (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-9xrj-h377-fr87?

Update activestorage to 8.1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xrj-h377-fr87 is resolved across your whole dependency graph.

How do I detect GHSA-9xrj-h377-fr87 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activestorage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9xrj-h377-fr87 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-9xrj-h377-fr87 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9xrj-h377-fr87 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-9xrj-h377-fr87?

GHSA-9xrj-h377-fr87 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-9xrj-h377-fr87?

GHSA-9xrj-h377-fr87 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9xrj-h377-fr87 published, and has it been updated?

GHSA-9xrj-h377-fr87 was published on March 23, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

Rails Active Storage has possible Path Traversal in DiskServiceGHSA-9xrj-h377-fr87

Fix: rails/rails@4933c1e

GHSA-9xrj-h377-fr87 is a Path Traversal vulnerability in activestorage. A fix is available for activestorage — see the affected versions and patch details below.

Also known asCVE-2026-33195

Published

Mar 23, 2026

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-9xrj-h377-fr87.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

💎activestorage💎activestorage💎activestorage

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Active Storage's DiskService#path_for does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. ../) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected.

Releases

The fixed releases are available at the normal locations.

Credit

This issue was responsibly reported by Hackerone researcher ksw9722.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activestorage`	≥ 8.1.0.beta1&&< 8.1.2.1	8.1.2.1`bundle update activestorage --conservative`
💎RubyGems	`activestorage`	≥ 8.0.0.beta1&&< 8.0.4.1	8.0.4.1`bundle update activestorage --conservative`
💎RubyGems	`activestorage`	all versions	7.2.3.1`bundle update activestorage --conservative`

Affected Products

1 product · 3 configurations

Application

railsrubyonrails

≥ 8.1.0 && < 8.1.2.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activestorage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activestorage to 8.1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9xrj-h377-fr87 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Satellite: The Active Storage engine is explicitly commented out and disabled at runtime across all Satellite/Foreman builds. No Satellite plugin or component re-enables Active Storage. Hence, Red Hat Satellite is not affected.

Workaround published by Red Hat

To mitigate this issue, ensure that blob keys used by Active Storage are not derived from untrusted user input. Applications should validate and sanitize any user-provided data before it is used in blob keys to prevent path traversal sequences.

Source: Red Hat security advisory for GHSA-9xrj-h377-fr87 (CC BY 4.0)

Frequently Asked Questions

### Impact Active Storage's `DiskService#path_for` does not validate that the resolved filesystem path remains within the storage root directory. If a blob key containing path traversal sequences (e.g. `../`) is used, it could allow reading, writing, or deleting arbitrary files on the server. Blob keys are expected to be trusted strings, but some applications could be passing user input as keys and would be affected. ### Releases The fixed releases are available at the normal locations. ### Credit This issue was responsibly reported by Hackerone researcher [ksw9722](https://hackerone.com/ksw

O3 Security · Impact-Aware SCA

Is GHSA-9xrj-h377-fr87 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works