How severe is GHSA-73f9-jhhh-hr5m?

No CVSS score has been assigned to GHSA-73f9-jhhh-hr5m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-73f9-jhhh-hr5m?

GHSA-73f9-jhhh-hr5m affects the following packages: activestorage (RubyGems), activestorage (RubyGems), activestorage (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-73f9-jhhh-hr5m?

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

How do I detect GHSA-73f9-jhhh-hr5m 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-73f9-jhhh-hr5m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-73f9-jhhh-hr5m actively exploited in the wild?

No public exploit code has been indexed for GHSA-73f9-jhhh-hr5m 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-73f9-jhhh-hr5m?

GHSA-73f9-jhhh-hr5m has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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-73f9-jhhh-hr5m?

GHSA-73f9-jhhh-hr5m is classified as CWE-74 (CWE-74). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-73f9-jhhh-hr5m published, and has it been updated?

GHSA-73f9-jhhh-hr5m 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 glob injection in its DiskServiceGHSA-73f9-jhhh-hr5m

Fix: rails/rails@8c9676b

GHSA-73f9-jhhh-hr5m is a CWE-74 vulnerability in activestorage. A fix is available for activestorage — see the affected versions and patch details below.

Also known asCVE-2026-33202

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.
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-73f9-jhhh-hr5m.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs53th percentile — riskier than 53% 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

Active Storage allows users to attach cloud and local files in Rails applications. Prior to versions 8.1.2.1, 8.0.4.1, and 7.2.3.1, Active Storage's DiskService#delete_prefixed passes blob keys directly to Dir.glob without escaping glob metacharacters. If a blob key contains attacker-controlled input or custom-generated keys with glob metacharacters, it may be possible to delete unintended files from the storage directory. Versions 8.1.2.1, 8.0.4.1, and 7.2.3.1 contain a patch.

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-73f9-jhhh-hr5m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatModerate

This flaw is rated as Moderate by Red Hat. Successful exploitation of this vulnerability requires an attacker to control or influence blob keys and trigger deletion operations within the Active Storage component. In typical deployments, these capabilities are restricted to authenticated users or internal application…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for GHSA-73f9-jhhh-hr5m (CC BY 4.0)

Frequently Asked Questions

### Impact Active Storage's `DiskService#delete_prefixed` passes blob keys directly to `Dir.glob` without escaping glob metacharacters. If a blob key contains attacker-controlled input or custom-generated keys with glob metacharacters, it may be possible to delete unintended files from the storage directory. ### Releases The fixed releases are available at the normal locations.

O3 Security · Impact-Aware SCA

Is GHSA-73f9-jhhh-hr5m in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works