How severe is GHSA-pmwx-rm49-xv39?

No CVSS score has been assigned to GHSA-pmwx-rm49-xv39 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pmwx-rm49-xv39?

GHSA-pmwx-rm49-xv39 affects the following packages: activerecord-tenanted (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-pmwx-rm49-xv39?

Update activerecord-tenanted to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmwx-rm49-xv39 is resolved across your whole dependency graph.

How do I detect GHSA-pmwx-rm49-xv39 in my RubyGems dependencies?

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

How do I mitigate GHSA-pmwx-rm49-xv39 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-pmwx-rm49-xv39 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pmwx-rm49-xv39 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.

When was GHSA-pmwx-rm49-xv39 published, and has it been updated?

GHSA-pmwx-rm49-xv39 was published on July 29, 2026 and was last updated on July 29, 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

ActiveRecord::Tenanted::Storage::DiskService#path_for has a possible path traversalGHSA-pmwx-rm49-xv39

Fix: basecamp/activerecord-tenanted#307

GHSA-pmwx-rm49-xv39 is a security vulnerability in activerecord-tenanted. A fix is available for activerecord-tenanted — see the affected versions and patch details below.

Published

Jul 29, 2026

Updated

Jul 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 29, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

💎activerecord-tenanted

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

Summary

Active Record Tenanted's override of 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.

Mitigation

Upgrade to Active Record Tenanted v0.7.0 or later.

As a workaround, do not use untrusted user input as blob keys. Blob keys are expected to be trusted strings.

Credit

This issue was responsibly reported by @tonghuaroot.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activerecord-tenanted`	all versions	0.7.0`bundle update activerecord-tenanted --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord-tenanted, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activerecord-tenanted to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pmwx-rm49-xv39 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.

Frequently Asked Questions

### Summary Active Record Tenanted's override of 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. ### Mitigation Upgrade to Active Record Tenanted v0.7.0 or later. As a workaround, do not use untrusted user input as blob keys. Blob key

O3 Security · Impact-Aware SCA

Is GHSA-pmwx-rm49-xv39 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works