CISA added CVE-2025-54236 to the Known Exploited Vulnerabilities catalog on October 24, 2025. For U.S. federal agencies, the listing carried a November 14 remediation deadline. Private-sector teams are not bound by that schedule, but the listing provides a clear signal: Adobe had already confirmed exploitation, and the flaw was no longer a theoretical patch item.

Vulnerability overview

Adobe APSB25-88 describes CVE-2025-54236 as an improper input validation flaw in Adobe Commerce and Magento Open Source. The CVSS 3.1 score is 9.1, with network access, low complexity, no privileges, and no user interaction. The CNA vector rates confidentiality and integrity impact as high.

NVD records CWE-20 and notes that the issue can enable session takeover. Sansec's research adds that the weakness can support unauthenticated RCE under certain conditions when a malicious session interacts with nested deserialization in the REST API. Adobe's own bulletin calls the impact a security feature bypass, so the two descriptions should not be merged into an unsupported claim about every target.

What KEV changes

A KEV entry requires affected U.S. federal civilian agencies to apply vendor mitigations or discontinue use under the applicable directive. It also gives security leaders outside government a useful prioritization reference. The date records observed exploitation.

The deadline does not make a vulnerable store explode on the due date. It requires an accountable remediation record. That record should show which assets were in scope, which patch or mitigation was applied, who validated the result, and whether a compromise review was needed after late remediation.

Exploitation and impact

Adobe confirmed active exploitation on October 22, 2025. Sansec reported that attacks began after public technical analysis and that only 38 percent of Magento stores were protected at the time. Within days, the company observed broad scanning and attempts, with PHP webshells and phpinfo probes in payloads.

A successful attacker may obtain customer-account access, modify storefront data, add administrator or integration access, and reach code execution. A store that patched late may also retain malicious session files, backdoors, or CMS modifications. The KEV response needs to include those possibilities when evidence supports them.

Affected products and scope

Adobe's affected Adobe Commerce versions include 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, and 2.4.4-p15 and earlier. Adobe Commerce B2B versions 1.5.3-alpha2, 1.5.2-p2, 1.4.2-p7, 1.3.4-p14, and 1.3.3-p15 and earlier are also listed. Magento Open Source is affected through the listed 2.4.5 to 2.4.9 branches. The emergency hotfix covers 2.4.4 through 2.4.7.

Exposure context

ZoomEye returned 134,273 matches for app="Magento" and 134,273 for the selected CVE filter. The procedure selected the Search query because the counts tied. The figure describes internet-visible product fingerprints at query time and does not establish patch level or exploitation.

That limitation matters for KEV reporting. A broad asset count can show scale, but an agency or enterprise still needs CMDB ownership, installed version, exposure path, and remediation evidence.

Remediation and mitigations

Apply the Adobe hotfix or a supported security release containing the correction. Test custom modules and customer flows before production deployment. If the patch cannot meet the required schedule, document compensating controls, their coverage, and the residual risk.

After any delayed patch, check for webshells, anomalous sessions, new administrators, unknown API integrations, and modified CMS blocks. Sansec recommends rotating the Magento crypt key after a confirmed compromise because an exposed key can allow continued content modification. Reset administrator passwords and remove integrations that are not recognized.

Track closure as a verified state. The final record should include patch evidence, validation results, compromise disposition, monitoring, and an owner. A ticket marked "patched" without those checks is not enough for a known exploited vulnerability.

References