Raw vector
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-33183 is a high-severity Path Traversal (CWE-22) vulnerability in Saloon Saloon. Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33183 is a path traversal vulnerability (CWE-22) affecting the Saloon PHP library, a tool for building API integrations and SDKs, in versions prior to 4.0.0. The issue arises because fixture names are used to construct file paths under a configured fixture directory without proper validation. This allows names containing path traversal segments, such as "../traversal" or "../../etc/passwd", to resolve to paths outside the intended directory. Consequently, applications using Saloon for reading fixtures (e.g., for mocking) or writing them (e.g., recording responses) risk accessing arbitrary files based on the process's permissions.
The vulnerability can be exploited by remote attackers with no required privileges (AV:N/AC:L/PR:N/UI:N), as indicated by its CVSS v3.1 base score of 9.1. Exploitation requires the fixture name to be derived from attacker-controlled input, such as request parameters or configuration values. Successful attacks enable high confidentiality impact through disclosure of sensitive files and high integrity impact by overwriting critical files, though availability remains unaffected (S:U/C:H/I:H/A:N).
Mitigation is addressed in Saloon version 4.0.0, which introduces validation at the fixture layer to reject names containing slashes (/ or \), parent directory references (..), null bytes, or characters outside a safe set. Additionally, defense-in-depth measures in the storage layer ensure resolved paths remain within the base directory before any read or write operations. Security practitioners should upgrade to version 4.0.0 or later, as detailed in the official upgrade guide and GitHub security advisory.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16060
Vulnerability Data
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.…
more
../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).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Security testing in development catches path traversal via static/dynamic analysis.
Information access restriction limits which files an application may read or write.