CVE-2026-33942: Saloon has insecure deserialization in AccessTokenAuthenticator
Impact Users of the OAuth2 utilities in Saloon, specifically the AccessTokenAuthenticator class. Patches Upgrade to Saloon v4+ Upgrade guide: https://docs.saloon.dev/upgrade/upgrading-from-v3-to-v4 Description The Saloon PHP library used PHP's unserialize() in AccessTokenAuthenticator::unserialize() to restore OAuth token state from cache or storage, with allowedclasses = true.
Published Mar 27, 2026
Affected packages
saloonphp/saloon
- Ecosystem
- Composer (PHP)
- Affected
- < 4.0.0
- Fixed in
- 4.0.0
- Check
composer show saloonphp/saloon
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Users of the OAuth2 utilities in Saloon, specifically the AccessTokenAuthenticator class.
Patches
Upgrade to Saloon v4+
Upgrade guide: https://docs.saloon.dev/upgrade/upgrading-from-v3-to-v4
Description
The Saloon PHP library 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 removes PHP serialization from the AccessTokenAuthenticator class requiring users to store and resolve the authenticator manually.
Credits
Saloon thanks @HuajiHD for finding the issue and recommending solutions and @jonpurvis for applying the fix.
Credited to JonPurvis, Sammyjo20, HuajiHD.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
