CVE-2026-33183: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in saloonphp saloon
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).
AI Analysis
Technical Summary
CVE-2026-33183 is a path traversal vulnerability (CWE-22) found in the Saloon PHP library, a tool used to build API integrations and SDKs. In versions prior to 4.0.0, the library used fixture names to construct file paths under a configured fixture directory without proper validation. This allowed an attacker to include path traversal sequences such as '../' or '..\' in fixture names, causing the application to access files outside the intended directory. When the application reads or writes fixtures (for example, during mocking or recording API responses), it could inadvertently read sensitive files like system configuration files or overwrite critical files if the fixture name was attacker-controlled. The vulnerability is particularly dangerous because it does not require authentication or user interaction and can be triggered remotely if fixture names are derived from user input such as request parameters or configuration files. The fix implemented in version 4.0.0 includes validation that rejects fixture names containing path separators, traversal sequences, or null bytes, and restricts names to a safe character set. Additionally, a defense-in-depth measure was added to verify that the resolved file path remains within the base fixture directory before any file operation is performed. This layered approach mitigates the risk of path traversal exploitation. The vulnerability has a CVSS 4.0 score of 8.0 (high severity) due to its potential to disclose sensitive information and modify files without requiring privileges or user interaction. No public exploits have been reported yet, but the vulnerability poses a significant risk to applications using affected Saloon versions.
Potential Impact
The impact of CVE-2026-33183 is substantial for organizations using the Saloon PHP library versions prior to 4.0.0 in their API integrations or SDKs. Successful exploitation can lead to unauthorized disclosure of sensitive files such as configuration files, credentials, or private data, compromising confidentiality. Additionally, attackers may overwrite critical files, potentially causing application malfunction, data corruption, or enabling further compromise, thus impacting integrity and availability. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by attackers who can control fixture names, increasing the attack surface. Organizations relying on Saloon in web-facing applications or services are at risk of data breaches, service disruption, or lateral movement within their infrastructure. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially given the ease of exploitation and high severity rating. Failure to patch could expose organizations to targeted attacks or automated scanning and exploitation attempts once public exploit code becomes available.
Mitigation Recommendations
To mitigate CVE-2026-33183, organizations should immediately upgrade the Saloon PHP library to version 4.0.0 or later, where the vulnerability is fully addressed. If upgrading is not immediately feasible, implement strict input validation on any user or attacker-controlled data used as fixture names, ensuring they do not contain path traversal sequences, path separators, or null bytes. Employ allowlisting of acceptable characters and patterns for fixture names. Additionally, enforce file system permissions to restrict the application process's access to only necessary directories and files, minimizing the impact of potential traversal. Use runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block suspicious path traversal attempts. Conduct thorough code reviews and security testing to identify any other areas where unvalidated file paths might be used. Finally, monitor logs for unusual file access patterns that may indicate exploitation attempts.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Japan, Netherlands, India, Brazil
CVE-2026-33183: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in saloonphp saloon
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).
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33183 is a path traversal vulnerability (CWE-22) found in the Saloon PHP library, a tool used to build API integrations and SDKs. In versions prior to 4.0.0, the library used fixture names to construct file paths under a configured fixture directory without proper validation. This allowed an attacker to include path traversal sequences such as '../' or '..\' in fixture names, causing the application to access files outside the intended directory. When the application reads or writes fixtures (for example, during mocking or recording API responses), it could inadvertently read sensitive files like system configuration files or overwrite critical files if the fixture name was attacker-controlled. The vulnerability is particularly dangerous because it does not require authentication or user interaction and can be triggered remotely if fixture names are derived from user input such as request parameters or configuration files. The fix implemented in version 4.0.0 includes validation that rejects fixture names containing path separators, traversal sequences, or null bytes, and restricts names to a safe character set. Additionally, a defense-in-depth measure was added to verify that the resolved file path remains within the base fixture directory before any file operation is performed. This layered approach mitigates the risk of path traversal exploitation. The vulnerability has a CVSS 4.0 score of 8.0 (high severity) due to its potential to disclose sensitive information and modify files without requiring privileges or user interaction. No public exploits have been reported yet, but the vulnerability poses a significant risk to applications using affected Saloon versions.
Potential Impact
The impact of CVE-2026-33183 is substantial for organizations using the Saloon PHP library versions prior to 4.0.0 in their API integrations or SDKs. Successful exploitation can lead to unauthorized disclosure of sensitive files such as configuration files, credentials, or private data, compromising confidentiality. Additionally, attackers may overwrite critical files, potentially causing application malfunction, data corruption, or enabling further compromise, thus impacting integrity and availability. Since the vulnerability requires no authentication or user interaction, it can be exploited remotely by attackers who can control fixture names, increasing the attack surface. Organizations relying on Saloon in web-facing applications or services are at risk of data breaches, service disruption, or lateral movement within their infrastructure. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially given the ease of exploitation and high severity rating. Failure to patch could expose organizations to targeted attacks or automated scanning and exploitation attempts once public exploit code becomes available.
Mitigation Recommendations
To mitigate CVE-2026-33183, organizations should immediately upgrade the Saloon PHP library to version 4.0.0 or later, where the vulnerability is fully addressed. If upgrading is not immediately feasible, implement strict input validation on any user or attacker-controlled data used as fixture names, ensuring they do not contain path traversal sequences, path separators, or null bytes. Employ allowlisting of acceptable characters and patterns for fixture names. Additionally, enforce file system permissions to restrict the application process's access to only necessary directories and files, minimizing the impact of potential traversal. Use runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block suspicious path traversal attempts. Conduct thorough code reviews and security testing to identify any other areas where unvalidated file paths might be used. Finally, monitor logs for unusual file access patterns that may indicate exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-17T22:16:36.720Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c4854ef4197a8e3b9c70b6
Added to database: 3/26/2026, 1:01:02 AM
Last enriched: 3/26/2026, 1:16:43 AM
Last updated: 3/26/2026, 5:40:51 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.