Magento security: patch gaps, checkout scripts and Admin access
Adobe announces security fixes for Adobe Commerce and Magento Open Source in its security bulletins, and Adobe's shared responsibility page for its cloud infrastructure says applying patches is the merchant's responsibility.
This guide explains how Adobe ships patches, where scripts reach a Magento checkout, and which Admin and API settings matter, then gives you an owner-run register to find your own patch gap.
In this guide
Magento patch-gap and checkout-script register
Copy the table into a spreadsheet, one copy per installation, and add a column for your answer. The patch rows find your release and patch level, the bulletin rows compare it with Adobe's fixes, the checkout and access rows record what runs on the checkout and who can change it, and the indicator rows read the Admin action history, the Security Scan Tool reports and the web root for leftovers.
How to use itHide the instructions
Each row reads a setting, list, file, log, report, document or Adobe page, asks your host or developer, requests a page or address of your own store, or runs a command that reports versions, patch status or advisories; the Content Security Policy row also uses one guest cart on your staging copy. Record that a token, key or password exists, never its value. The bulletin log covers the Adobe Commerce bulletins in Adobe's HelpX archive from APSB25-88 (9 September 2025) to APSB26-138 (8 September 2026), each read on 14 November 2026. The archive page says bulletins published through 22 September 2026 remain there, and points to the Trust Center page "Adobe Security Bulletins and Advisories" for future bulletins. This log may not include bulletins published after 8 September 2026: check that Trust Center page for anything published since before you rely on it.
28 rows
Item to check
Where to look
Patch gap: product and hosting
- Where to look
- Your contract or hosting agreement, and the product package named in composer.lock.
- What the documentation says
- Adobe's upgrade guide names magento/product-community-edition as the Magento Open Source product package for an on-premises installation, with a separate product package for Adobe Commerce. Adobe's shared responsibility page is written for Adobe Commerce on cloud infrastructure, a platform-as-a-service offering.
- What to record
- Adobe Commerce on-premises, Adobe Commerce on cloud infrastructure, or Magento Open Source; who hosts it; and whether Adobe's shared responsibility page applies to you.
Patch gap: installed release and patch level
- Where to look
- On Commerce on Cloud, the bottom-right corner of any Admin page, or bin/magento --version where the version is hidden; on any installation, the product package version in composer.lock.
- What the documentation says
- Adobe's security notice, which applies to Commerce on Cloud versions 2.4.4 to 2.4.9, gives both ways to read the version there. Adobe's upgrade guide says security patches use the Composer naming convention 2.4.x-px, such as 2.4.6-p3.
- What to record
- The release line and -p level for production and for staging, if they differ, with the date read.
Patch gap: monthly isolated patches
- Where to look
- From the project root, php vendor/bin/patch-status, run by your developer. On Adobe Commerce on cloud infrastructure, where the Commerce Version Tool is not available and the Quality Patches Tool is already installed, Adobe's alternative is vendor/bin/magento-patches -n status, filtered for one patch file name.
- What the documentation says
- Adobe says the Commerce Version Tool reports applied_patches, missing_patches and a per-CVE vulnerability_status of PROTECTED, VULNERABLE or UNKNOWN. Adobe's September 2026 release notes say it is only available in the July 2026 security isolated patch file; the tool's own page says it is included with each monthly security patch. It is informational only, and can write cache files, temporary dry-run files and audit-log entries.
- What to record
- Applied, missing and unknown patches, and every CVE marked VULNERABLE or UNKNOWN, with the JSON or CSV output saved and dated. If the tool is not present, write "not present": installing it means applying a patch, which is patch work, not this review.
Patch gap: release line support
- Where to look
- The End of support dates table in Adobe's lifecycle policy.
- What the documentation says
- Adobe gives each version three years of standard support from General Availability, with quality fixes and security patches, and describes extended support and a security-only transitional period for some older lines. It says a hotfix is not comprehensive and does not address all security issues that upgrading would resolve.
- What to record
- The end of standard, extended and any security-only support for your line, copied from the table with the date read.
Patch gap: platform services
- Where to look
- On cloud infrastructure, the "Containers" tab for each environment in the Cloud Console. On your own servers, your host or developer.
- What the documentation says
- Adobe's shared responsibility page puts the database, cache, search, PHP runtime and web server on actively supported versions among the merchant's duties. Its lifecycle policy says Adobe does not provide security and quality fixes for third-party dependencies, such as PHP and MySQL, that may reach end of life during a release's support period.
- What to record
- Each service and its version per environment, and whether its vendor still supports that version, with where you checked.
Patch gap: extensions and Composer packages
- Where to look
- composer.lock, and composer audit --locked run by your developer.
- What the documentation says
- Adobe's best practices say to source extensions only from the Adobe Commerce Marketplace or through the solution integrator, and to limit the number of extensions and vendors. Composer says audit checks installed packages against defined dependency policies, such as security advisories, and --locked audits the lock file.
- What to record
- Each third-party package with its version, vendor, where it was obtained and the vendor's advisory page, plus each advisory composer audit reports and the vendor's fixed version for it.
Bulletin APSB26-146, published 7 September 2026, Adobe priority 1 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center, and Adobe's hotfix article for CVE-2026-75650.
- What the documentation says
- Resolves a critical vulnerability in Adobe Commerce and Magento Open Source that could result in arbitrary code execution; Adobe is aware of CVE-2026-75650 being exploited in the wild. Affected: Adobe Commerce 2.4.9-2026-aug and earlier, 2.4.8-2026-aug and earlier, 2.4.7-2026-aug and earlier, 2.4.6-2026-aug and earlier, 2.4.5-2026-aug and earlier and 2.4.4-2026-aug and earlier; Magento Open Source 2.4.9-2026-aug and earlier, 2.4.8-2026-aug and earlier, 2.4.7-2026-aug and earlier and 2.4.6-2026-aug and earlier. Fix: the "Hotfix for CVE-2026-75650". The hotfix article says to apply the patch for your version and rotate your encryption keys.
- What to record
- Whether your line is on the affected list; whether the hotfix is applied, using the check in Adobe's article (for Commerce on Cloud where the Quality Patches Tool is already installed, its status for the VULN-39341 hotfix file) or your developer's record of applying it; and whether the key and credential rotation the article lists was done, as yes or no with a date. Never the keys.
Bulletin APSB26-138, published 8 September 2026, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center, and its September 2026 release notes.
- What the documentation says
- Resolves critical, important and moderate vulnerabilities; successful exploitation could result in security feature bypass and privilege escalation; Adobe is not aware of any exploits in the wild. Affected: the same Adobe Commerce and Magento Open Source lists as APSB26-146. Updated versions: Adobe Commerce 2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sep, 2.4.6-2026-sep, 2.4.5-2026-sep and 2.4.4-2026-sep; Magento Open Source 2.4.9-2026-sep, 2.4.8-2026-sep and 2.4.7-2026-sep. The bulletin asks for the APSB26-146 hotfix as well.
- What to record
- Whether the September 2026 isolated patch files for your line show as applied in the patch-status output, and whether the July and August 2026 files before them do too.
Bulletin APSB26-92, published 11 August 2026, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center.
- What the documentation says
- Resolves critical, important and moderate vulnerabilities; successful exploitation could result in security feature bypass, arbitrary code execution and privilege escalation; Adobe is not aware of any exploits in the wild. Affected: Adobe Commerce 2.4.9-2026-jul and earlier, 2.4.8-2026-jul and earlier, 2.4.7-2026-jul and earlier, 2.4.6-2026-jul and earlier, 2.4.5-2026-jul and earlier and 2.4.4-2026-jul and earlier; Magento Open Source 2.4.9-2026-jul and earlier, 2.4.8-2026-jul and earlier, 2.4.7-2026-jul and earlier and 2.4.6-2026-jul and earlier. Updated versions: Adobe Commerce 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug and 2.4.4-2026-aug; Magento Open Source 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug and 2.4.6-2026-aug.
- What to record
- Whether the August 2026 isolated patch files for your line show as applied in the patch-status output.
Bulletin APSB26-73, published 14 July 2026, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center.
- What the documentation says
- Resolves critical, important and moderate vulnerabilities; successful exploitation could lead to arbitrary code execution, privilege escalation and security feature bypass; Adobe is not aware of any exploits in the wild. Affected: Adobe Commerce 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier, 2.4.6-p15 and earlier, 2.4.5-p17 and earlier and 2.4.4-p18 and earlier; Magento Open Source 2.4.9, 2.4.8-p5 and earlier, 2.4.7-p10 and earlier and 2.4.6-p15 and earlier; also Adobe Commerce Events 1.6.0 to 1.20.0. Updated versions: Adobe Commerce 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul, 2.4.5-2026-jul and 2.4.4-2026-jul; Magento Open Source 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul and 2.4.6-2026-jul; Adobe Commerce Events 1.21.0.
- What to record
- Whether the July 2026 isolated patch files for your line show as applied; and, if Adobe Commerce Events is installed, its version from composer.lock.
Bulletin APSB26-49, published 12 May 2026, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center.
- What the documentation says
- Resolves critical, important and moderate vulnerabilities; successful exploitation could lead to arbitrary code execution, arbitrary file system write, application denial-of-service and security feature bypass; Adobe is not aware of any exploits in the wild. Affected: Adobe Commerce 2.4.9-beta1, 2.4.8-p4 and earlier, 2.4.7-p9 and earlier, 2.4.6-p14 and earlier, 2.4.5-p16 and earlier and 2.4.4-p17 and earlier; Magento Open Source 2.4.9-beta1, 2.4.8-p4 and earlier, 2.4.7-p9 and earlier and 2.4.6-p14 and earlier. Updated versions: Adobe Commerce 2.4.9, 2.4.8-p5, 2.4.7-p10, 2.4.6-p15, 2.4.5-p17 and 2.4.4-p18; Magento Open Source 2.4.9, 2.4.8-p5, 2.4.7-p10 and 2.4.6-p15.
- What to record
- Whether composer.lock shows the updated version for your line or a later -p level, read from the product package.
Bulletin APSB26-05, published 10 March 2026, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's Trust Center.
- What the documentation says
- Resolves critical, important and moderate vulnerabilities; successful exploitation could lead to security feature bypass, application denial-of-service, privilege escalation, arbitrary code execution and arbitrary file system read; Adobe is not aware of any exploits in the wild. Affected: Adobe Commerce 2.4.9-alpha3 and earlier, 2.4.8-p3 and earlier, 2.4.7-p8 and earlier, 2.4.6-p13 and earlier, 2.4.5-p15 and earlier and 2.4.4-p16 and earlier; Magento Open Source 2.4.9-alpha3, 2.4.8-p3 and earlier, 2.4.7-p8 and earlier, 2.4.6-p13 and earlier and 2.4.5-p15 and earlier. Updated versions: 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14 and 2.4.5-p16 for both products, and 2.4.4-p17 for Adobe Commerce.
- What to record
- Whether composer.lock shows the updated version for your line or a later -p level.
Bulletin APSB25-94, published 14 October 2025, Adobe priority 2 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's HelpX archive.
- What the documentation says
- Resolves critical and important vulnerabilities; successful exploitation could lead to security feature bypass, privilege escalation and arbitrary code execution; Adobe is not aware of any exploits in the wild. Affected: Adobe Commerce 2.4.9-alpha2 and earlier, 2.4.8-p2 and earlier, 2.4.7-p7 and earlier, 2.4.6-p12 and earlier, 2.4.5-p14 and earlier and 2.4.4-p15 and earlier; Magento Open Source 2.4.9-alpha2, 2.4.8-p2 and earlier, 2.4.7-p7 and earlier and 2.4.6-p12 and earlier. Updated versions: 2.4.9-alpha3, 2.4.8-p3, 2.4.7-p8 and 2.4.6-p13 for both products, and 2.4.5-p15 and 2.4.4-p16 (written "2.4.4 p16" in the bulletin) for Adobe Commerce.
- What to record
- Whether composer.lock shows the updated version for your line or a later -p level.
Bulletin APSB25-88, published 9 September 2025, Adobe priority 1 (read 14 November 2026)
- Where to look
- The bulletin on Adobe's HelpX archive.
- What the documentation says
- Resolves a critical vulnerability; successful exploitation could lead to security feature bypass; Adobe is aware of CVE-2025-54236 being exploited in the wild. Affected: Adobe Commerce 2.4.9-alpha2 and earlier, 2.4.8-p2 and earlier, 2.4.7-p7 and earlier, 2.4.6-p12 and earlier, 2.4.5-p14 and earlier and 2.4.4-p15 and earlier; Magento Open Source 2.4.9-alpha2 and earlier, 2.4.8-p2 and earlier, 2.4.7-p7 and earlier, 2.4.6-p12 and earlier and 2.4.5-p14 and earlier. Fix: the "Hotfix for CVE-2025-54236", which the bulletin describes as compatible with all Adobe Commerce and Magento Open Source versions between 2.4.4 and 2.4.7. Adobe's patch release schedule says security patches include all previously released security, compliance and quality hotfixes.
- What to record
- Whether your line was on the affected list; whether the hotfix was applied, from your developer's record of applying it; and the first security patch release your store moved to afterwards, read from composer.lock.
Checkout scripts: HTML Head
- Where to look
- Content > Design > Configuration, Edit on each row, then HTML Head, "Scripts and Style Sheets". Leave each form without saving.
- What the documentation says
- Adobe's page setup guide says the field holds scripts included before the closing head tag, such as third-party JavaScript, and Adobe's Security Scan Tool setup pastes a confirmation code into it. Adobe's best practices say that in the most commonly experienced attacks, malicious code is injected into the absolute header or absolute footer of a customer store.
- What to record
- For each scope: every script or tag present, the domain it loads from or sends data to, and who recognises it and why it is there. If the field holds a key, note that a key is present and leave the value out.
Checkout scripts: Footer
- Where to look
- Content > Design > Configuration, the same rows, then Footer, "Miscellaneous HTML".
- What the documentation says
- Adobe's page setup guide says the field holds miscellaneous scripts placed just before the closing body tag. Adobe's incident guidance says to review the HTML Header and Footer configuration in all scope levels, including website and store view, and retain only recognised code such as tracking snippets.
- What to record
- The same as the HTML Head row, for each scope.
Checkout scripts: Content Security Policy
- Where to look
- Your own staging copy only, never the live store: add one product to a guest cart once, then open the checkout page once with the browser's developer tools showing response headers. Place no order, type nothing into the checkout form and send no other requests. Also Stores > Settings > Configuration, Security, Content Security Policy for report addresses, leaving the form without saving, and your developer for any module config.xml or csp_whitelist.xml that changes the policy.
- What the documentation says
- In 2.4.7 and later, Adobe says CSP runs in restrict mode by default on payment pages in the storefront and admin areas and report-only elsewhere, sent as Content-Security-Policy or Content-Security-Policy-Report-Only, and the payment-page policy omits unsafe-inline from script-src. JavaScript in the header and footer fields must be whitelisted or it will not be executed on the Checkout pages.
- What to record
- Which header the checkout sends, the script-src hosts it lists, whether unsafe-inline appears in script-src, whether a report address is set for the storefront and for the Checkout page, and who reads the reports. The cart record is a test record on staging.
Checkout scripts: Subresource Integrity
- Where to look
- The installed version from the patch rows, and the pub/static folder on the server.
- What the documentation says
- Adobe says 2.4.4-p9, 2.4.5-p8, 2.4.6-p6, 2.4.7, 2.4.8 and later support SRI for JavaScript assets in the local filesystem, by default on the payment pages for the admin and storefront areas. From 2.4.9, hashes sit in sri-hashes.json files under pub/static, scoped by area, theme and locale.
- What to record
- Whether your version is at or above the SRI level for its line; on 2.4.9 and later, whether sri-hashes.json files exist under pub/static; and each script the checkout loads from another domain, since Adobe's page said, when read, that there is no SRI support for custom remote JavaScript resources.
Checkout scripts: custom layout updates
- Where to look
- Content > Elements > Pages, each page's Design section, "Custom Layout Update"; each category's Design settings; and the theme's layout folders on the server.
- What the documentation says
- Adobe says advanced layout updates are XML saved on the server and selected in the Admin as a "Custom Layout Update", with CMS page file names beginning cms_page_view_selectable_. The Widget tool adds an existing content block to a page's layout.
- What to record
- Each page or category with a custom layout update selected, the file it uses, whether that file is in version control, and when it last changed.
Checkout scripts: code against version control
- Where to look
- Your developer's comparison of the production code base with the repository.
- What the documentation says
- Adobe's incident guidance says to compare the current production code base to the code base stored in the version control system.
- What to record
- Each file that differs, by path and date only, and who explained the difference. Moving or deleting a file is a change for the owner to decide.
Access: Admin users and two-factor sign-in
- Where to look
- The Admin's user list and roles; Stores > Settings > Configuration, Security, 2FA for the required providers.
- What the documentation says
- Adobe says 2FA is required to sign in to the Admin and applies to the Admin only, and stores that enabled Adobe IMS authentication have native 2FA disabled. Its best practices recommend least privilege when assigning Admin permissions.
- What to record
- Each Admin user matched to a named person who still needs access, with their role, the 2FA providers required, and whether IMS sign-in is on. No passwords or codes, and if the 2FA settings show a provider key or secret, record only that one is set.
Access: Admin security settings
- Where to look
- Stores > Settings > Configuration, Advanced, Admin, Security.
- What the documentation says
- The section includes "Admin Account Sharing", "Add Secret Key to URLs" (enabled by default) and "Maximum Login Failures to Lockout Account" (six attempts by default, unlimited when left empty), with the session and password lifetimes. Adobe's best practices recommend a non-default Admin URL rather than admin or a common term such as backend.
- What to record
- Each value as set, and whether the Admin address you sign in at uses the default or a common term.
Access: integrations
- Where to look
- System > Extensions > Integrations: read the grid only. For each integration's API resource access, ask the developer who set it up, and do not open its edit page.
- What the documentation says
- Adobe says each integration has a callback URL, an identity link URL and resource access set to All or Custom, and the grid shows an "Integration not secure" label until HTTPS URLs are saved for both. The Activate and "Reauthorize" links display or generate tokens, and Adobe's OAuth-based authentication page says the Integration Details on an integration's edit page show the credentials that can be used to make an authenticated API request using OAuth 1.0.
- What to record
- Each integration's name, status, resource access, the owner of the system it connects, whether the warning label shows, and whether it is still used. Do not click Activate or "Reauthorize", and do not open an integration's edit page, during the review.
Access: integration tokens as bearer tokens
- Where to look
- Stores > Configuration > Services > OAuth > Consumer Settings, "Allow OAuth Access Tokens to be used as standalone Bearer tokens".
- What the documentation says
- Adobe says an integration token lasts until someone revokes it, that using it on its own as a bearer token is disabled by default because a compromised token provides undetected persistent access to a store, and that restoring it is not recommended.
- What to record
- Yes or No, and if Yes, which integration needs it and who decided. Never the token.
Access: anonymous web API
- Where to look
- Stores > Settings > Configuration > Services > Magento Web API > Web API Security, "Allow Anonymous Guest Access".
- What the documentation says
- By default, Adobe says Commerce prevents anonymous users from reaching web APIs that could reveal sensitive information, such as product, category, CMS and store endpoints. Setting the option to Yes turns that protection off, which Adobe says may be needed when a third-party integration fails.
- What to record
- Yes or No, and if Yes, which integration needed it and whether it still does.
Indicators: Admin action history (Adobe Commerce only)
- Where to look
- System > Actions Logs > Report, and the Admin Actions Logging screen in the store settings.
- What the documentation says
- Adobe says the report records the time, action, IP address, username and result of each Admin action enabled for logging, exports to CSV or Excel XML, and is not available in Magento Open Source.
- What to record
- Which action types are enabled, and for the review period, any change to header or footer fields, users, roles or integrations that nobody can explain. On Magento Open Source, write "not available" and name whatever other record you keep.
Indicators: Security Scan Tool reports
- Where to look
- Your Commerce/Magento account, Security Scan, "Monitored Websites", "View Report", if the store is already registered.
- What the documentation says
- Adobe says the tool monitors Adobe Commerce and Magento Open Source sites for security risks and malware, gives access to historical security reports, and shows a scan report of successful and failed checks with any recommended actions. For a Commerce storefront, registering a store adds a confirmation code to its HTML Head scripts field and saves the configuration, which is a change.
- What to record
- Whether the store is registered, the date of its last report, each failed check, and each result in "Ignored Results". Leave the ignore settings as they are during the review.
Indicators: development leftovers
- Where to look
- A listing of the web root from your developer; and your own store's app/etc/local.xml and var addresses, each requested once by your developer with a command that prints only the HTTP status code, never the response body, so nothing the address serves appears on screen.
- What the documentation says
- Adobe's best practices say to ensure no accessible log files, .git directories, SQL tunnels, database dumps or php info files exist. Its incident guidance says to verify that the site's app/etc/local.xml and var URLs are not publicly accessible.
- What to record
- Each leftover by path, and the status code each address returned. If an address is served, record that it was served, never its contents.
Magento security starts with the product and hosting you run
Magento security covers Adobe Commerce and Magento Open Source, the names Adobe's security bulletins use, and the bulletins read for this guide list the affected versions for each product separately.
Adobe's documentation describes Adobe Commerce running on-premises or on Adobe Commerce on cloud infrastructure, which its shared responsibility page calls a platform-as-a-service (PaaS) offering. Some features belong to Adobe Commerce alone: Adobe's page for the Action Logs report, for example, says the report is not available in Magento Open Source.
Adobe's documentation also describes Adobe Commerce as a Cloud Service, which its security notice for Commerce on Cloud calls Adobe's fully managed commerce platform. Some pages this guide relies on are limited to other forms. Adobe's token authentication page says it is for Platform-as-a-Service (PaaS) customers only, and its security notice says that guidance does not apply to Adobe Commerce as a Cloud Service (SaaS) environments or to Adobe Commerce on-premises deployments. This guide covers the on-premises, cloud infrastructure and Open Source forms.
A Magento store has more ways in than its storefront. The Admin, in the words of Adobe's two-factor authentication page, provides access to your store, orders and customer data. The web APIs answer integrations and the storefront itself, and Adobe's page on anonymous web APIs lists guest cart, checkout and customer endpoints among those that stay open to anonymous users, most of which, Adobe says, must remain accessible to support checkout and add-to-cart.
Adobe's integrations page says defining an integration establishes the location of OAuth credentials for a third-party integration and identifies the API resources it needs.
Adobe's upgrade guide upgrades the product with Composer: for an on-premises installation, Magento Open Source is the magento/product-community-edition package, and Adobe Commerce has a product package of its own. The checkout then runs whatever scripts the store's configuration, theme and extensions put on the page.
How Adobe ships Magento security patches
Adobe announces fixes in security bulletins with ids such as APSB26-138, and the bulletins read for this guide list the Magento vulnerabilities they resolve by CVE id.
Adobe's patch release schedule names these channels for news of a patch: Adobe Security Bulletins and Advisories, email, and in-product alerts. The HelpX bulletins page for Adobe Commerce says bulletins have moved to the Adobe Trust Center, and that bulletins published through 22 September 2026 remain on HelpX as an archive. The Trust Center bulletins page itself says bulletins and advisories published before January 2026 are available on HelpX.
The fixes arrive in different forms, and the form decides how you check for them:
- Security patches. Adobe's upgrade guide says they contain security fixes only and use the Composer naming convention 2.4.x-px, such as 2.4.6-p3. The patch release schedule says they are released at minimum annually for all supported release lines, and include all previously released security, compliance and quality hotfixes.
- Isolated security patch files. The schedule describes them as individual, non-cumulative files released independently for faster remediation and incorporated into the next full security patch. To apply one, a store must be on the most recent security-only patch release, the most recent -p version, for its release line.
- Hotfixes. Adobe's lifecycle policy says that for critical security issues, such as zero-day vulnerabilities, Adobe provides hotfixes for all customers on a supported version, and that a hotfix is not comprehensive and does not address all security issues that upgrading to the most recent release would resolve.
Monthly isolated patches change what composer.lock tells you
From July 2026, the bulletins in this guide's log give the updated versions of Adobe Commerce and Magento Open Source as a release line and a month, such as 2.4.8-2026-sep, apart from the APSB26-146 hotfix. Adobe's release notes for the September 2026 update, APSB26-138, say the September fixes are provided as isolated patch files only, and that Composer packages aren't published alongside them.
The same notes say each monthly isolated patch builds on the ones released before it and must be applied in release order, on top of the most recent -p release for the line.
Adobe's Commerce Version Tool page shows how the tool answers the question. It reads composer.lock to find the Adobe Commerce base version, then runs a dry-run check for each applicable patch to see whether it is already applied, is not applied, or has an unknown status. In this guide's reading, composer.lock is the starting point for a patch gap and the patch-status report is the evidence.
Release lines end
Adobe's lifecycle policy gives each version a three-year standard support window from its General Availability date, with quality fixes and security patches, and keeps a table of end-of-support dates for each release. It also describes extended support for some versions and a one-time, time-limited security-only transitional period available only for 2.4.4, 2.4.5 and 2.4.6.
Read the table for your own line on the day you fill in the register, and copy the dates with the date you read them.
Finding your Magento patch gap
A patch gap is the distance between what is installed and what Adobe's bulletins say fixes each issue.
The register on this page builds it from readings taken on the store itself, not from memory or an agency's last report.
- The release. Adobe's security notice for Commerce on Cloud, which applies to Commerce on Cloud versions 2.4.4 to 2.4.9, says the version displays in the bottom-right corner of any Admin page, and gives bin/magento --version for when it is hidden. Adobe's Commerce Version Tool reads the base version, such as 2.4.7-p10, from composer.lock.
- The monthly patches. Adobe's release notes for APSB26-138 recommend the Commerce Version Tool, run as php vendor/bin/patch-status from the project root, which reports applied_patches, missing_patches and a per-CVE status of PROTECTED, VULNERABLE or UNKNOWN. The same notes say the tool is only available in the July 2026 security isolated patch file, while Adobe's Commerce Version Tool page says it is included with each monthly security patch and installed at vendor/bin/patch-status when the patch is applied. Adobe calls it informational only: it does not apply or revert patches or modify source files, but it can write cache files, temporary dry-run files and audit-log entries.
- Hotfixes. Under a heading for Adobe Commerce on Cloud merchants only, Adobe's article on the APSB26-146 hotfix says it isn't possible to easily determine if the issue was patched, recommends checking that the hotfix was applied, and shows a Quality Patches Tool status check for the hotfix file.
- Third-party packages. According to Composer's documentation, composer audit checks the packages you have installed against defined dependency policies, such as security advisories, and adding --locked audits the packages in the lock file regardless of what the vendor folder holds. This page treats that as a check on third-party packages and takes Adobe's own fixes from the bulletins.
- Platform services. For cloud infrastructure, Adobe's shared responsibility page lists keeping the database, cache, search, PHP runtime and web server on actively supported versions among the merchant's responsibilities, and Adobe's security notice for Commerce on Cloud shows where to read them: the "Containers" tab for each environment in the Cloud Console.
Extensions and custom code
Adobe's security best practices say to source extensions only from the Adobe Commerce Marketplace or through the solution integrator, to reduce risk by limiting the number of extensions and vendors, and, if possible, to review extension code for security before integrating it.
The same page asks merchants to review the server and source code repository for development leftovers, and to ensure no accessible log files, .git directories, SQL tunnels, database dumps or php info files exist. Adobe's bulletins cover Adobe's code.
For each extension, the register asks for the vendor's own advisory page, because, for cloud infrastructure, Adobe's shared responsibility page lists applying patches to all custom extensions and code, as each vendor releases them, among the merchant's responsibilities.
Where scripts get into a Magento checkout
Adobe's own security guidance describes the attack the second half of the register looks for.
It says that in the most commonly experienced attacks, malicious code is injected into the absolute header or absolute footer of a customer store. There the code collects form data a customer enters in the storefront, including login credentials and checkout form data, and sends it to another location rather than to the Commerce backend.
Adobe adds that malware can compromise the Admin to execute code that replaces the original payment form with a fake form that overrides any protections set by the payment provider.
It also says that after actions such as form submission or field modification, a client-side skimmer serialises the data and sends it to third-party endpoints, which are typically other compromised websites that act as a relay.
In the Admin, scripts for the head and the footer of each page are entered in fields. Under Content > Design > Configuration, each store view has an HTML Head section with a "Scripts and Style Sheets" field for scripts placed before the closing head tag, and a Footer section with a "Miscellaneous HTML" field for scripts placed just before the closing body tag.
Adobe's incident guidance says to review the HTML Header and Footer configuration at all scope levels, including website and store view, remove any unknown JavaScript code from those settings, and retain only recognised code such as tracking snippets.
The register records every script in those fields, at every scope, with a named person who recognises it.
What PCI DSS asks a merchant to show about payment-page scripts is the subject of the payment script controls guide in this library. This page stays with what Magento's settings and Adobe's documentation say.
Content Security Policy on payment pages
Adobe's developer guide says Adobe Commerce and Magento Open Source support Content Security Policy headers from version 2.3.5, in a report-only mode and a restrict mode. In report-only mode the application reports violations but does not interfere; in restrict mode it acts on them.
The guide says that in 2.4.7 and later, CSP is configured in restrict mode by default for payment pages in the storefront and admin areas and in report-only mode for all other pages, and the payment-page header does not contain the unsafe-inline keyword in script-src.
Adobe's page setup guide adds that JavaScript entered in the "Scripts and Style Sheets" or "Miscellaneous HTML" fields must be whitelisted in the CSP settings, in Adobe's term, or it will not be executed on the Checkout pages.
Other details from the same developer guide matter for a review. A custom module can set the CSP mode in its own config.xml, and can add domains for a policy in a csp_whitelist.xml file. The policy in force is therefore whatever the checkout page actually sends.
And eval() is still allowed. Violations can be reported to an endpoint set under Stores > Settings > Configuration, Security, Content Security Policy, where the storefront Checkout page can have its own report address.
Adobe's overview notes that because CSP is configured from the server rather than the Admin, most merchants need the assistance of a system integrator or developer to configure it properly.
Subresource Integrity on payment pages
Adobe's Subresource Integrity page says Adobe Commerce and Magento Open Source 2.4.4-p9, 2.4.5-p8, 2.4.6-p6, 2.4.7, 2.4.8 and later include SRI support, with integrity hashes for JavaScript assets in the local filesystem, and that the default feature covers only the payment pages for the admin and storefront areas.
From 2.4.8 the hashes are kept in the local filesystem rather than a cache, and from 2.4.9 they sit in sri-hashes.json files under pub/static, scoped by area, theme and locale. When read on 14 November 2026, the page said there was no SRI support for custom remote JavaScript resources, and showed how a merchant can generate an integrity hash for a remote resource.
This page's advice: list every script the checkout loads from another domain, since Adobe's hashes cover assets in the local filesystem.
Layout updates and widgets
Adobe's layout update guide describes ways to change what a page contains from the Admin. The Widget tool adds an existing content block to a page's layout. For more advanced updates, XML layout update code is saved on the server and then selected in the Admin as a "Custom Layout Update"; for CMS pages, the file name begins with cms_page_view_selectable_.
Category pages have the same setting, which lists the available custom layout update files on the server. A custom layout update therefore leaves a file on the server and a selection in the Admin.
The register records both and checks the file against version control, in line with Adobe's incident guidance to compare the production code base with the code base in version control.
Admin accounts, integrations and the web API
Adobe's Admin security page says two-factor authentication is required to verify users' identity with a one-time password generated by an app or device, with users prompted to set it up the first time they sign in to the Admin, and that the Admin login can also be configured to require a CAPTCHA.
Stores that have enabled Adobe Identity Management Services (IMS) authentication have native Adobe Commerce and Magento Open Source 2FA disabled, with authentication handled by Adobe IMS. Adobe's 2FA page notes that this 2FA applies to the Admin only and is not available for customer accounts.
The Admin security settings sit under Stores > Settings > Configuration, Advanced, Admin, Security. They include "Admin Account Sharing", which when set to No prevents Admin users logging in from the same account on different devices; "Add Secret Key to URLs", enabled by default; and "Maximum Login Failures to Lockout Account", which allows six attempts by default and unlimited attempts when left empty, alongside the session lifetime and the password lifetime.
Adobe's best practices also recommend a non-default Admin URL instead of admin or a common term such as backend, and the principle of least privilege when assigning Admin permissions.
Integrations and their tokens
Integrations are how outside systems reach the store through the API. Adobe's integrations page says each one is defined under System > Extensions > Integrations with a callback URL, an identity link URL and API resource access set to All or Custom, and that the grid shows an "Integration not secure" label until HTTPS URLs are saved for both.
Adobe's token documentation says an integration token has no default expiry: it lasts until someone revokes it. It also says using an integration's access token on its own as a bearer token has been disabled by default because of the security implications of a never-expiring token: if it is compromised, it provides undetected persistent access to a store.
Adobe says that, while not recommended, the behaviour can be restored with the "Allow OAuth Access Tokens to be used as standalone Bearer tokens" setting.
Anonymous REST access
Adobe's page on restricting anonymous web APIs says that, by default, Commerce prevents anonymous users from reaching APIs that could reveal sensitive information, among them product, category, CMS page and block, and store endpoints. It warns that this could cause third-party integrations to fail, and that the protection is turned off by setting "Allow Anonymous Guest Access" to Yes under Stores > Settings > Configuration > Services > Magento Web API > Web API Security.
A Yes there is a deliberate change from the default, so the register records it with the integration that needed it.
A record of Admin changes
Adobe Commerce keeps an Action Logs report at System > Actions Logs > Report, with the time, action, IP address, username and result of each logged Admin action, exportable as CSV or Excel XML. Actions appear only when they are enabled on the Admin Actions Logging screen, and Adobe says the report is not available in Magento Open Source.
Adobe's incident guidance lists these logs among the tools for analysing an incident. For a review, they are where to look for an unexplained change to a header field, a user or an integration.
How to use the register as a Magento security checklist
The register on this page is for the store owner, an office manager with Admin access, and the developer or agency who looks after the code.
Work through it together, one copy per installation.
- Fill the patch rows from the installation that serves production. If staging runs different code, fill a second copy for it.
- Each row reads a setting, list, file, log, report, document or Adobe page, asks your host or developer, requests a page or address of your own store, or runs a command that reports versions, patch status or advisories; the Content Security Policy row also uses a guest cart, covered below. None applies a patch, changes a setting, activates or reauthorises an integration, or rotates a credential. Adobe says its Commerce Version Tool can write cache files, temporary dry-run files and audit-log entries, so run it where your developer agrees it may run.
- The Content Security Policy row needs one product in a guest cart. Do it on your staging copy only: it creates one cart record there, places no order, takes no card details and sends no request beyond the add to cart and one checkout page load.
- Record names, versions, statuses, people and dates. Never copy an integration token, an encryption key, an API key or a password into the register. Where a file can hold a secret, such as app/etc/env.php, where Adobe's lock commands write configuration values, or a log, record only whether the secret is present.
- For each script, record the field and scope it is set in, the domain it loads from or sends data to, and the person who recognises it. Removing an unrecognised script is a change and a decision for the store owner, made with whoever handles incidents for you.
- For each bulletin row, compare your installed version with the affected list for your product, then record the evidence that row asks for: the patch-status output for a monthly patch, composer.lock for a -p release, or the hotfix check or your developer's record for a hotfix.
- Repeat the review after each new bulletin, each extension install or update, and each change of agency or host.
Limits of a register filled in from your own store
The register records configuration and versions.
It records the evidence on whether each bulletin's fix is applied, which scripts the Admin puts on each store view, and which integrations hold which access. It does not show what an extension's code does with a request, whether one customer can reach another customer's orders through the API, or whether a script served from another domain changed after you read it. Answering them takes a test of the running application.
It also cannot see past a compromise. Adobe's incident guidance says to look for the attack vector by reviewing server log files and file changes, and to keep monitoring after an incident, since many sites get compromised again within hours. A register filled in today says nothing about what ran on the checkout last month.
And it is a snapshot. Adobe can publish a bulletin, someone can change a setting, or a vendor can update an extension the day after you finish.
Before anyone tests the store
Adobe's testing guidance for Commerce on cloud infrastructure lists a penetration test among the testing types it says to consider as a best practice before site launch, and describes it as an authorised simulated cyber attack designed to evaluate the security of the system.
The same page warns that customers are not permitted to conduct any security assessments of AWS infrastructure or the AWS services themselves, and says a security issue found in an AWS service should go to AWS Security immediately.
This guide found no Adobe page that sets out what else a customer may test on Adobe's infrastructure. Read your agreement with Adobe before any active test, and get the answer in writing where it leaves doubt. For a store you host yourself, the testing terms are your hosting provider's, and the same advice applies.
If you think the checkout is already compromised
The register is a review, not incident response.
If a header or footer field holds a script nobody recognises, or customers report card fraud after buying from the store, stop filling in the register and treat it as an incident. For Adobe Commerce on cloud infrastructure, Adobe's incident guidance lists critical first steps: audit all admin user account access, enable advanced multi-factor authentication controls, preserve critical logs, and review security upgrades for your version. It also recommends engaging your system integrator and appropriate security personnel to investigate.
Clever Ops does not clean up malware or run incident response. Contact an incident response specialist first, and keep logs before anything is deleted. For CVE-2026-75650, Adobe's hotfix article shows how far remediation can reach: it says to rotate not only the encryption key but all credentials that may have been encrypted or exposed using it, including server, API and integration credentials, with payment gateway credentials rotated at the provider.
For the first hours after you find a compromise, turn to the hacked website guide in this library.
Where Clever Ops picks up
Nothing in this guide describes a Magento-specific Clever Ops service; it is here for information.
Clever Ops does not test Adobe's platform or its cloud infrastructure. The Clever Ops methodology keeps services run by other businesses, and your host's platform, outside the method.
Active tests against your own store, treated as an application, belong to a scoped web application and API penetration test. That service is a signed-in test of a custom application with an API behind it, and its coverage includes authentication and sessions, what each role can see and change, whether one customer can reach another customer's records, the API called directly rather than only through the screens, and payment and billing flows.
On payments, it looks at your application's part of each payment and leaves the payment provider's platform out. Each target's owner signs an authorisation, and your host's testing policy is checked, before any test starts.
Payment testing of this kind is not a PCI DSS assessment. Clever Ops is not a PCI Approved Scanning Vendor or a Qualified Security Assessor; for a PCI DSS external scan or assessment, look for a provider on the PCI Security Standards Council's list for that role. Nor does Clever Ops monitor a store around the clock or run emergency incident response.
A store that Clever Ops built or hosts is reviewed, not independently tested: the work is called a security review, and the report states which business built the store and which hosts it.
Frequently asked questions
The Adobe pages read for this guide give no yes or no. For Adobe Commerce on cloud infrastructure, Adobe's shared responsibility page gives Adobe secure core application code, platform security and periodic security updates, and gives the merchant applying patches, custom code and integrations, user access and incident response. That page is written for Adobe's cloud infrastructure, so for a store you host yourself, read your hosting agreement for the server side. The register on this page checks your own store: patches, scripts, Admin access and integrations.
Read the base release from composer.lock; for Commerce on Cloud, Adobe's security notice also gives the bottom-right corner of any Admin page, or bin/magento --version. Then run Adobe's Commerce Version Tool with php vendor/bin/patch-status. Adobe says it reports applied and missing monthly patches and a per-CVE status of PROTECTED, VULNERABLE or UNKNOWN. Adobe's September 2026 release notes say the tool is only available in the July 2026 security isolated patch file, while the tool's own page says it is included with each monthly security patch. The same release notes say the September fixes were provided as isolated patch files, without Composer packages. In this guide's reading, a version read from composer.lock therefore shows the base release, not the monthly patches applied on top of it.
The bulletins read for this guide cover both, with a separate version list for each. In APSB26-138, the updated versions for Magento Open Source are 2.4.9-2026-sep, 2.4.8-2026-sep and 2.4.7-2026-sep, while Adobe Commerce also has updated versions for its 2.4.6, 2.4.5 and 2.4.4 lines. Adobe's release notes for that update say Open Source merchants can only download patches for version 2.4.7 or later. Some security tooling differs too: Adobe says the Action Logs report is not available in Magento Open Source.
Adobe's Admin security page says two-factor authentication is required to verify users' identity with a one-time password, and users are prompted to set it up the first time they sign in to the Admin. The required providers are chosen under Stores > Settings > Configuration, Security, 2FA. Adobe notes limits: this 2FA covers the Admin only, not customer accounts, and stores that enabled Adobe IMS authentication have native 2FA disabled, with sign-in handled by Adobe IMS instead.
It tells the browser which sources of script and other content to trust. Adobe's developer guide says that in 2.4.7 and later, CSP runs in restrict mode by default on payment pages in the storefront and admin areas and in report-only mode elsewhere, and that the payment-page policy omits unsafe-inline from script-src. A custom module can change the mode, so read the header your checkout actually sends. Adobe's page setup guide says scripts added in the Admin header or footer fields must be whitelisted in the CSP settings or they will not run on the Checkout pages.
Adobe's testing guidance for Commerce on cloud infrastructure lists a penetration test among the testing types it says to consider as a best practice before site launch, and says customers are not permitted to conduct any security assessments of AWS infrastructure or the AWS services themselves. This guide found no other Adobe page on what customers may test, so read your agreement with Adobe, or your host's terms for a self-hosted store, and get answers in writing where they leave doubt. Testing your own store application sits within a scoped web application and API penetration test.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.