# GHSA-29g5-m8v7-v564: Measured is vulnerable to Path Traversal attacks during class initialization

> An attacker can read arbitrary files by manipulating inputs during Measured::Cache::Json class initialization in this Ruby library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2025

## What is GHSA-29g5-m8v7-v564?

GHSA-29g5-m8v7-v564 is a path traversal vulnerability in measured, published on 15 Jul 2025. 

### Official 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.

## Which versions are affected by GHSA-29g5-m8v7-v564?

2 open source packages ship an affected version, including measured.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `measured` | RubyGems | All versions | 3.2.1 |
| `measured` | RubyGems | All versions | 3.2.1 |

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

Upgrade measured to 3.2.1 or later.

## Is GHSA-29g5-m8v7-v564 being exploited?

There is no known exploitation of GHSA-29g5-m8v7-v564 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-29g5-m8v7-v564 and fix it if it is affected.

What it is: GHSA-29g5-m8v7-v564 is a path traversal vulnerability in measured, published on 15 Jul 2025. 
Exploitation: There is no known exploitation of GHSA-29g5-m8v7-v564 in the wild and no public exploit code.

Affected packages and fixed versions:
- measured (RubyGems): affected all versions; fixed in 3.2.1
- measured (RubyGems): affected all versions; fixed in 3.2.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-29g5-m8v7-v564/ (Markdown: https://insights.sbomify.com/GHSA-29g5-m8v7-v564/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-29g5-m8v7-v564

---
From sbomify Insights: https://insights.sbomify.com/GHSA-29g5-m8v7-v564/
Summaries are generated and may contain mistakes; the official description above is the record.