How severe is GHSA-c83f-3xp6-hfcp?

No CVSS score has been assigned to GHSA-c83f-3xp6-hfcp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c83f-3xp6-hfcp?

GHSA-c83f-3xp6-hfcp affects the following packages: saloonphp/saloon (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c83f-3xp6-hfcp?

Update saloonphp/saloon to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c83f-3xp6-hfcp is resolved across your whole dependency graph.

How do I detect GHSA-c83f-3xp6-hfcp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saloonphp/saloon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c83f-3xp6-hfcp if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-c83f-3xp6-hfcp actively exploited in the wild?

No public exploit code has been indexed for GHSA-c83f-3xp6-hfcp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c83f-3xp6-hfcp?

GHSA-c83f-3xp6-hfcp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c83f-3xp6-hfcp?

GHSA-c83f-3xp6-hfcp is classified as CWE-522 (CWE-522), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c83f-3xp6-hfcp published, and has it been updated?

GHSA-c83f-3xp6-hfcp was published on March 25, 2026 and was last updated on March 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Saloon is vulnerable to SSRF and credential leakage via absolute URL in endpoint overriding base URLGHSA-c83f-3xp6-hfcp

GHSA-c83f-3xp6-hfcp is a CWE-522 vulnerability in saloonphp/saloon. A fix is available for saloonphp/saloon — see the affected versions and patch details below.

Also known asCVE-2026-33182

Published

Mar 25, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c83f-3xp6-hfcp.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘saloonphp/saloon

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Users providing user generated input into the resolveEndpoint method on requests.

Patches

Upgrade to Saloon v4+

Upgrade guide: https://docs.saloon.dev/upgrade/upgrading-from-v3-to-v4

Description

When building the request URL, Saloon combined the connector's base URL with the request endpoint. If the endpoint was a valid absolute URL (e.g. https://attacker.example.com/callback), 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 the next major version) 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.

Credits

Saloon thanks @HuajiHD for finding the issue and recommending solutions and @JonPurvis for applying the fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`saloonphp/saloon`	all versions	4.0.0`composer require saloonphp/saloon:^4.0.0`

Affected Products

1 product · 1 configurations

Application

saloonsaloon

< 4.0.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saloonphp/saloon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update saloonphp/saloon to 4.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c83f-3xp6-hfcp is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### Impact Users providing user generated input into the `resolveEndpoint` method on requests. ### Patches Upgrade to Saloon v4+ Upgrade guide: https://docs.saloon.dev/upgrade/upgrading-from-v3-to-v4 ### Description When building the request URL, Saloon combined the connector's base URL with the request endpoint. If the endpoint was a valid absolute URL (e.g. https://attacker.example.com/callback), 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 t

O3 Security · Impact-Aware SCA

Is GHSA-c83f-3xp6-hfcp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Saloon is vulnerable to SSRF and credential leakage via absolute URL in endpoint overriding base URLGHSA-c83f-3xp6-hfcp

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Impact

Patches

Description

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-c83f-3xp6-hfcp in your dependencies?