Martech Partners Contact
MartechPartners

Adobe Commerce CVE-2026-71362 Added to CISA KEV: What to Do

Adobe Commerce · Editorial Team · 1 October 2026

Rescana reports that CVE-2026-71362, an incorrect authorization flaw in Adobe Commerce and Magento that allows account takeover, is being actively exploited and has been added to CISA's Known Exploited Vulnerabilities (KEV) catalog. That moves it from a patch-when-scheduled item to a drop-what-you're-doing item. If you run Adobe Commerce, treat the next few days as an incident-readiness exercise, not routine maintenance.

Key takeaways

  • Rescana reports active exploitation of CVE-2026-71362, an incorrect authorization account takeover flaw, and its addition to CISA's KEV list.
  • A KEV entry means attackers are already using the flaw. Patch ahead of your normal release train.
  • Take the fixed version number from Adobe's official security bulletin, then verify it on every environment, not only production.
  • Patching does not evict an attacker who got in earlier. Review admin users, customer account changes, integrations and logs.
  • Small teams with a working release process can patch themselves. Bring in a partner for forensics, heavy customisation and post-incident hardening.
  • Done means a verified version, a reviewed account list and a written decision on whether this was an incident.

What does the CISA KEV listing change for an Adobe Commerce store?

It changes the timeline and the question you're answering. Most vulnerability advisories describe something that could be abused. A KEV entry says someone has abused it, in real attacks, and that CISA has enough evidence to say so publicly. Rescana's alert is built around exactly that: active exploitation, not theoretical risk.

The practical effect is that your usual scoring habits stop being useful. Teams often rank patches by severity score, then by how busy the sprint is. A flaw on the KEV list should skip that queue. The score tells you how bad it could be. The KEV listing tells you it's already happening to somebody.

There's a second effect people miss. Once a flaw is public and exploited, automated scanning follows. Attackers don't pick targets by brand. They sweep for reachable stores running something vulnerable. A mid-size retailer with a quiet admin panel and no special profile is just as likely to be hit as a famous one.

Other outlets covered the same development. BleepingComputer and The Hacker News both ran stories about CISA adding Adobe Commerce and WSO2 flaws to the list. If your security team reads one of those first, they'll land on the same conclusion.

Who is affected by this Adobe Commerce account takeover flaw?

Assume you're in scope until Adobe's bulletin tells you otherwise. The headline names Adobe Commerce and Magento, so that covers self-hosted installations and, depending on how Adobe scopes the advisory, possibly its hosted offerings. The exact affected version range and the fixed releases are in Adobe's security bulletin. Read it directly rather than relying on a summary, including this one.

Some situations deserve extra attention:

  • Stores that lag a release or more behind. Older installs are the most common casualties of any exploited flaw, because the patch path is longer and more likely to collide with custom code.
  • Stores with forgotten environments. A staging site cloned from production, with real customer data and a public URL, is a live target. So is the old regional storefront nobody owns.
  • Stores with many admin users or shared logins. An account takeover flaw is most dangerous where accounts carry a lot of privilege.
  • Stores with third-party extensions that touch customer or admin accounts. Single sign-on modules, B2B account tools and loyalty plugins sit near the authorization logic. They don't make you vulnerable, but they make patching harder to test.

Incorrect authorization is a category, not a recipe. It means the system fails to properly check whether the person making a request is allowed to. The consequence here, per the headline, is account takeover. Which accounts, and with what reach, is something to read out of Adobe's description rather than guess.

What should we do in the first 24 hours?

Keep it short and ordered. The aim is to close the exposure, then find out whether it was already used.

  1. Name an owner. One person decides, and one person executes. Security incidents drift when five people each assume another has it.
  2. Read Adobe's security bulletin. Get the affected range and fixed versions from Adobe directly. Write down the exact version you need to reach.
  3. Inventory every environment. Production, staging, UAT, regional stores, and any agency-hosted copies. Record each one's current version.
  4. Apply the fix or Adobe's stated mitigation. If the full upgrade can't ship today, ask whether Adobe publishes an interim mitigation and apply it while you plan the proper release.
  5. Preserve logs before they rotate. Web server, application and admin action logs. Copy them somewhere safe first. You can't investigate what's already been overwritten.
  6. Tighten the admin surface. Restrict the admin panel by IP or VPN where you can, and confirm multi-factor authentication is on for every admin user.

None of this requires a project plan. It requires a morning.

How do we check whether we were already compromised?

Patching closes the door. It says nothing about who's already inside. This is the step teams skip, and it's the one that decides whether you have a closed ticket or an open breach.

Start with accounts, because that's what this flaw is about:

  • List every admin user and compare it to the people who should have access. Look for accounts you don't recognise, recent creations, and role changes.
  • Check for admin accounts that were recently modified, especially permission or email changes.
  • Review customer accounts for unexpected email or password changes, particularly on high-value or B2B accounts.
  • Review API integration tokens and any newly created integrations. Remove anything nobody can explain.

Then look at the store itself. Check for modified or unexpected files in your codebase, compare against your deployment history, and look at what the checkout and payment pages load. Card-skimming scripts tend to turn up after storefront compromises, so inspect any script that loads on payment pages and ask who added it.

If you find something, don't clean it up and move on. Contain it, keep the evidence, rotate credentials and keys that the affected account could reach, and bring in someone who does incident response for a living. Depending on where you operate and what customer data was reachable, you may also have notification obligations. That's a conversation for your legal and security leads, not a developer.

If you find nothing, write that down too. A dated note saying what you checked, when and with what result is worth having if anyone asks later.

How should we roll the patch out without breaking checkout?

Speed matters, but a broken checkout during a sale is its own incident. The compromise is a short, disciplined path rather than your full release ceremony.

Use a staging copy that matches production as closely as you can, apply the fix there first, and run the flows that make money: guest checkout, logged-in checkout, payment authorisation, discount codes, account login, password reset, and any B2B quote or company-account flows. Customer account behaviour deserves particular attention here, since the flaw concerns who is allowed to do what.

Step Owner What to confirm Typical risk
Version inventory Platform lead Every environment's current version recorded Missed staging or regional store
Apply fix on staging Developer Update installs cleanly, no failed setup scripts Custom module conflict
Regression pass QA or developer Login, checkout, payments, B2B flows Extension that overrides account logic
Production release Platform lead Deployed in a low-traffic window, rollback ready Cache or indexing side effects
Post-release verification Security owner Version matches Adobe's fixed release Config drift between nodes
Account review Security owner Admin and customer accounts checked Evidence already rotated away

If you run several nodes behind a load balancer, check each one. A fleet where one server missed the deploy is a common way to believe you're patched when you aren't.

Take a full backup before you start, and know how you'd roll back. But don't treat rollback as a reason to wait. Rolling back to a vulnerable version is a decision, and it should be a short-lived one.

What should we ignore, and what shouldn't we do?

Ignore the urge to wait for a perfect picture. You'll see conflicting commentary, differing claims about scale and a lot of breathless headlines. Cybernews, for instance, ran a headline about mass exploitation of a critical Magento and Adobe Commerce flaw. Whether or not that refers to this exact CVE, it's a reminder that stores of every size get swept. Don't spend a day debating attribution. Spend it patching.

Also ignore any advice that begins with a proof-of-concept. You don't need to reproduce the issue to protect yourself, and testing exploit code against production is a self-inflicted incident. Verification means checking versions and reviewing evidence, not attacking your own store.

What not to do:

  • Don't treat a web application firewall as the fix. Rules can help buy time, but they're a layer, not a replacement for the vendor patch.
  • Don't patch production only. An exposed staging site with a copy of live data is still a way in.
  • Don't skip the account review because the patch went smoothly. A clean deploy and a clean store are different claims.
  • Don't reset every password blindly and call it done. Rotate what a compromised account could reach, and understand why.
  • Don't rely on a summary like this one for version numbers. Confirm them in Adobe's official bulletin.

Where does an implementation partner help, and where can we do it ourselves?

Be honest about your team. If you ship releases regularly, have a staging environment that mirrors production, and have someone who can read logs, you can handle the patch and the first-pass review yourselves. The steps above are ordinary platform operations.

A partner earns its fee in a few specific places:

  • Forensics. If your account review turns up anything strange, you want people who've investigated Magento compromises before. Mistakes here destroy evidence.
  • Heavily customised stores. When years of custom modules sit around account and admin logic, a partner who knows the codebase can tell you quickly whether the update is safe.
  • Stores far behind on versions. Jumping several releases is a project, not a patch. A partner can scope it and keep you protected in the meantime.
  • Hardening afterwards. Admin access policy, extension hygiene, monitoring and a patch cadence that means the next advisory is a one-day job.

If you don't have a relationship with one, the Adobe Commerce partners directory is a reasonable place to see who specialises in the platform, and you can find partners by region and size. When you brief one, a written scope matters more than a sales call. Our Adobe Commerce RFP template gives you a structure for stating the environments, version, custom code and what you need back, including a written findings report.

One caution. Ask any partner what they'll deliver for incident work, not just what they'll bill. A report of what was checked, what was found and what changed is the thing you'll need later.

How do we know we're actually done?

A closed ticket isn't evidence. Use outcomes you can check.

  • Version verified on every environment. Matches the fixed release in Adobe's bulletin, confirmed from the system itself, not from a deploy note.
  • Admin list reconciled. Every admin account maps to a named, current person. Multi-factor authentication is enforced.
  • Customer account review completed. Unexpected email, password or role changes investigated, with a record of the result.
  • Integrations audited. Every API token and integration has an owner and a purpose.
  • Logs preserved. The relevant period is stored outside the server that generated it.
  • Decision recorded. A short written statement: no evidence of compromise found, or incident declared with a link to its record.

Then look at the process, not just this one flaw. How long did it take from the CISA listing to a verified production fix? If the answer is measured in weeks, that's the number to fix. A store that can move from advisory to verified patch in a day or two is far harder to hurt, whatever the next headline says.

For teams comparing options for ongoing platform support, the Adobe Commerce partner rankings are worth a look once the immediate work is done. Do that after you've patched, not instead of it.

Sources

  • Rescana — Alert on active exploitation of CVE-2026-71362 and its addition to the CISA KEV catalog
  • BleepingComputer — Coverage of CISA's warning on exploited SharePoint, WSO2 and Adobe Commerce flaws
  • The Hacker News — Coverage of WSO2 and Adobe Commerce flaws exploited in attacks and added to CISA KEV

Frequently Asked Questions

What is CVE-2026-71362 in Adobe Commerce?

Rescana describes it as an incorrect authorization flaw in Adobe Commerce and Magento that can lead to account takeover, and reports it is being actively exploited. Read Adobe's own security bulletin for the exact affected and fixed versions.

What does a CISA KEV listing mean for my store?

The Known Exploited Vulnerabilities catalog lists flaws that CISA has evidence of being used in real attacks. For a merchant, it means the question is no longer whether someone could exploit the issue but whether they already have, so patch fast and check for signs of compromise.

Is patching enough to fix an Adobe Commerce account takeover vulnerability?

Patching closes the hole going forward but does not remove anything an attacker did before the fix. Review admin users, customer account changes, API integrations and logs, and rotate credentials if anything looks off.

Do I need an implementation partner to respond to this vulnerability?

Not for the patch itself if your team already runs regular releases. A partner helps most with forensic review, heavily customised stores where the update is risky, and hardening afterwards.