How severe is GHSA-29g5-m8v7-v564?

No CVSS score has been assigned to GHSA-29g5-m8v7-v564 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-29g5-m8v7-v564?

GHSA-29g5-m8v7-v564 affects the following packages: measured (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-29g5-m8v7-v564?

Update measured to 3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29g5-m8v7-v564 is resolved across your whole dependency graph.

How do I detect GHSA-29g5-m8v7-v564 in my RubyGems dependencies?

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

How do I mitigate GHSA-29g5-m8v7-v564 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-29g5-m8v7-v564?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-29g5-m8v7-v564 can be triaged on real exposure rather than presence alone.

Is GHSA-29g5-m8v7-v564 actively exploited in the wild?

No public exploit code has been indexed for GHSA-29g5-m8v7-v564 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-29g5-m8v7-v564 published, and has it been updated?

GHSA-29g5-m8v7-v564 was published on July 15, 2025 and was last updated on July 15, 2025. 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

GHSA-29g5-m8v7-v564 — measured

Fix: Shopify/measured@d631998

GHSA-29g5-m8v7-v564 is a security vulnerability in measured. A fix is available for measured — see the affected versions and patch details below.

Measured is vulnerable to Path Traversal attacks during class initialization

Published

Jul 15, 2025

Updated

Jul 15, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 15, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

💎measured

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

A path traversal vulnerability exists where an attacker with access to manipulate inputs when initializing the Measured::Cache::Json class would be able to instruct the library to read arbitrary files.

Patches

Users should update to the latest version.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`measured`	all versions	3.2.1`bundle update measured --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for measured, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update measured to 3.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29g5-m8v7-v564 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-29g5-m8v7-v564 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-29g5-m8v7-v564. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A path traversal vulnerability exists where an attacker with access to manipulate inputs when initializing the `Measured::Cache::Json class` would be able to instruct the library to read arbitrary files. ### Patches Users should update to the latest version.

O3 Security · Impact-Aware SCA

Is GHSA-29g5-m8v7-v564 in your dependencies?

O3 Security finds GHSA-29g5-m8v7-v564 across RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works