# CVE-2026-33182: Saloon is vulnerable to SSRF and credential leakage via absolute URL in endpoint overriding base URL

> Attackers can trigger SSRF and leak credentials by supplying absolute URLs in API endpoints, affecting developers using the Saloon PHP library.

- **Severity:** Medium 6.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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-c83f-3xp6-hfcp

## What is CVE-2026-33182?

CVE-2026-33182 is a medium-severity server-side request forgery 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, when building the request URL, Saloon combined the connector's base URL with the request endpoint. If the endpoint was a valid absolute URL, the code used that URL as-is and ignored the base URL. The request—and any authentication headers, cookies, or tokens attached by the connector—was then sent to the attacker-controlled host. If the endpoint could be influenced by user input or configuration (e.g. redirect_uri, callback URL), this allowed server-side request forgery (SSRF) and/or credential leakage to a third-party host. The fix in version 4.0.0 is to reject absolute URLs in the endpoint: URLHelper::join() throws InvalidArgumentException when the endpoint is a valid absolute URL, unless explicitly allowed, requiring callers to opt-in to the functionality on a per-connector or per-request basis.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-522 (Insufficiently Protected Credentials)

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

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-33182?

Upgrade saloonphp/saloon to 4.0.0 or later.

## Is CVE-2026-33182 being exploited?

There is no known exploitation of CVE-2026-33182 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-33183](https://insights.sbomify.com/CVE-2026-33183/): Saloon has a Fixture Name Path Traversal Vulnerability (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33182 is a medium-severity server-side request forgery 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-33182 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-33182/ (Markdown: https://insights.sbomify.com/CVE-2026-33182/index.md)
```

## Sources

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

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