ActiveRecord::Tenanted::Storage::DiskService#path_for has a possible path traversal
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (activerecord-tenanted 0.7.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
RubyGems activerecord-tenanted
- Affected
- < 0.7.0
- Fixed in
- 0.7.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-pmwx-rm49-xv39 lists affected ranges: RubyGems activerecord-tenanted >=0 <0.7.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-pmwx-rm49-xv39 lists affected ranges: RubyGems activerecord-tenanted >=0 <0.7.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 2.3 · CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Summary Active Record Tenanted's override of Active Storage's DiskService#pathfor 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-pmwx-rm49-xv39
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-pmwx-rm49-xv39
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-pmwx-rm49-xv39 Advisory: ActiveRecord::Tenanted::Storage::DiskService#path_for has a possible path traversal IDs: GHSA-pmwx-rm49-xv39 Record: https://patchnext.com/advisories/ghsa-pmwx-rm49-xv39 (revision 3, source checked 26 Oct 2026, 15:52 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: activerecord-tenanted 0.7.0. A vendor fix does not mean a deployment is fixed. ## Affected components - RubyGems activerecord-tenanted: affected < 0.7.0; fixed in 0.7.0 ## Suggested inspection (read-only) - RubyGems activerecord-tenanted: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on activerecord-tenanted. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-pmwx-rm49-xv39 (OSV record GHSA-pmwx-rm49-xv39 lists affected ranges: RubyGems activerecord-tenanted >=0 <0.7.0 (fixed)) - Verified: https://github.com/advisories/GHSA-pmwx-rm49-xv39 (GitHub-reviewed advisory GHSA-pmwx-rm49-xv39 lists affected ranges: RubyGems activerecord-tenanted >=0 <0.7.0) Commands are suggestions: review each one before running it.
Loading voting…