Saloon has insecure deserialization in AccessTokenAuthenticator (object injection / RCE)
Description
Saloon is a PHP library that gives users tools to build API integrations and SDKs. Versions prior to 4.0.0 used PHP's unserialize() in AccessTokenAuthenticator::unserialize() to restore OAuth token state from cache or storage, with allowed_classes => true. An attacker who can control the serialized string (e.g. by overwriting a cached token file or via another injection) can supply a serialized "gadget" object. When unserialize() runs, PHP instantiates that object and runs its magic methods (__wakeup, __destruct, etc.), leading to object injection. In environments with common dependencies (e.g. Monolog), this can be chained to remote code execution (RCE). The fix in version 4.0.0 removes PHP serialization from the AccessTokenAuthenticator class requiring users to store and resolve the authenticator manually.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
saloonphp/saloonPackagist | < 4.0.0 | 4.0.0 |
Affected products
2- saloonphp/saloonv5Range: < 4.0.0
Patches
Vulnerability mechanics
References
4- github.com/advisories/GHSA-rf88-776r-rcq9ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-33942ghsaADVISORY
- docs.saloon.dev/upgrade/upgrading-from-v3-to-v4ghsax_refsource_MISCWEB
- github.com/saloonphp/saloon/security/advisories/GHSA-rf88-776r-rcq9ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.