# CVE-2026-61505: Rejetto HFS < 3.2.1 Limited File Disclosure via Path Traversal in lang Parameter

> Remote attackers can read specific JSON files outside shared folders via path traversal in the lang parameter of Rejetto HFS.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-2jh3-2rfc-9fhf

## What is CVE-2026-61505?

CVE-2026-61505 is a medium-severity path traversal vulnerability in rejetto hfs, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rejetto HFS 3.0.0 through 3.2.0 allows path traversal through the lang query parameter, permitting a remote unauthenticated attacker to read certain JSON files outside the shared folders. Exploitation is constrained to files matching a narrow naming and format pattern, limiting practical impact.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-61505?


## How do I fix CVE-2026-61505?

No fix has been published for CVE-2026-61505 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61505 being exploited?

There is no known exploitation of CVE-2026-61505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61505 and fix it if it is affected.

What it is: CVE-2026-61505 is a medium-severity path traversal vulnerability in rejetto hfs, published on 13 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61505 in the wild and no public exploit code.

Affected product: rejetto hfs. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-61505/ (Markdown: https://insights.sbomify.com/CVE-2026-61505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61505
- OSV: https://osv.dev/vulnerability/CVE-2026-61505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61505/
Summaries are generated and may contain mistakes; the official description above is the record.