SessionReaper
SessionReaper is a critical improper input validation vulnerability in the Adobe Commerce and Magento Open Source REST API. Affected Adobe Commerce releases include 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15, and earlier releases in the corresponding branches. The Web API ServiceInputProcessor permits unsafe nested object construction from attacker-controlled input, exposing sensitive session-management classes. Attackers can bypass security controls and manipulate session state to take over customer accounts without victim interaction. On installations using file-based session storage, a demonstrated chain combines session save-path manipulation, unauthenticated file upload, and PHP object deserialization to achieve remote code execution. The vulnerability has a CVSS v3 base score of 9.1 and has been exploited in the wild.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises session confidentiality and integrity, allowing customer impersonation, access to sensitive account information, and unauthorized changes to account or transaction data. Administrative session compromise is also reported as a potential outcome. Where the remote-code-execution chain is viable, attackers can execute code with the web-server process's privileges, steal application secrets and database credentials, deploy web shells, establish persistence, and compromise the storefront. Remote code execution is conditional and should not be assumed for every affected configuration.
If you can’t patch tonight, do this now.
Until remediation is complete, restrict REST API access to trusted networks and required integrations, deploy WAF rules for known SessionReaper and malicious deserialization patterns, and disable unnecessary integrations. Restrict administrator access through network controls and MFA. Monitor API requests, abnormal session behavior, unexpected administrator or API-token creation, and unauthorized server-side files. Redis-backed session storage prevents the published filesystem-dependent remote-code-execution chain, but is not a complete mitigation for the underlying vulnerability. Adobe Commerce Cloud WAF protections do not replace required patches.
Patch, then assume compromise.
Immediately apply Adobe hotfix VULN-32437-2-4-X-patch and any applicable module updates specified in security bulletin APSB25-88, or upgrade to an applicable vendor-confirmed fixed release. The patch restricts constructor deserialization to simple types and permitted Magento API data-object types, preventing the demonstrated object chain. Verify successful deployment across production and staging environments and regression-test API integrations. Investigate previously exposed installations for compromise, invalidate existing sessions, and rotate administrator credentials and API tokens. If compromise is confirmed, remove malicious artifacts, rotate exposed secrets, and restore or rebuild affected systems from trusted sources as necessary.
8 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
234 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.