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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-pmwx-rm49-xv39 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.

How does O3 Security protect against GHSA-pmwx-rm49-xv39?

O3 pinpoints whether GHSA-pmwx-rm49-xv39 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

GHSA-pmwx-rm49-xv39

GHSA-pmwx-rm49-xv39 is a security vulnerability in activerecord-tenanted. O3 Security confirms whether GHSA-pmwx-rm49-xv39 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ActiveRecord::Tenanted::Storage::DiskService#path_for has a possible path traversal

Published

Jul 29, 2026

Updated

Jul 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
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.
How O3 protects you
O3 pinpoints whether GHSA-pmwx-rm49-xv39 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pmwx-rm49-xv39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-pmwx-rm49-xv39 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works