# CVE-2026-33183: Saloon has a Fixture Name Path Traversal Vulnerability

> Attackers can read or write arbitrary files via path traversal in fixture names if input is user-controlled, affecting Saloon PHP library users.

- **Severity:** High 8.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-f7xc-5852-fj99

## What is CVE-2026-33183?

CVE-2026-33183 is a high-severity path traversal vulnerability in saloonphp saloon, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Saloon is a PHP library that gives users tools to build API integrations and SDKs. Prior to version 4.0.0, fixture names were used to build file paths under the configured fixture directory without validation. A name containing path segments (e.g. ../traversal or ../../etc/passwd) resulted in a path outside that directory. When the application read a fixture (e.g. for mocking) or wrote one (e.g. when recording responses), it could read or write files anywhere the process had access. If the fixture name was derived from user or attacker-controlled input (e.g. request parameters or config), this constituted a path traversal vulnerability and could lead to disclosure of sensitive files or overwriting of critical files. The fix in version 4.0.0 adds validation in the fixture layer (rejecting names with /, \, .., or null bytes, and restricting to a safe character set) and defense-in-depth in the storage layer (ensuring the resolved path remains under the base directory before any read or write).

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

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

2 open source packages ship an affected version, including saloonphp/saloon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `saloonphp/saloon` | Packagist | All versions | 4.0.0 |
| `saloonphp/saloon` | Packagist | All versions | 4.0.0 |

Products: Saloon Saloon.

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

Upgrade saloonphp/saloon to 4.0.0 or later.

## Is CVE-2026-33183 being exploited?

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

## Other vulnerabilities in saloonphp saloon

- [CVE-2026-33942](https://insights.sbomify.com/CVE-2026-33942/): Saloon has insecure deserialization in AccessTokenAuthenticator (object injection / RCE) (high 8.1)
- [CVE-2026-33182](https://insights.sbomify.com/CVE-2026-33182/): Saloon is vulnerable to SSRF and credential leakage via absolute URL in endpoint overriding base URL (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33183 is a high-severity path traversal vulnerability in saloonphp saloon, published on 26 Mar 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-33183 in the wild and no public exploit code.

Affected packages and fixed versions:
- saloonphp/saloon (Packagist): affected all versions; fixed in 4.0.0
- saloonphp/saloon (Packagist): affected all versions; fixed in 4.0.0

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

## Sources

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

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