On this page (6 sections)

Two critical vulnerabilities in Adobe Experience Manager (AEM), tracked as CVE-2026-113580 and CVE-2026-113579, were published on 2026-11-10. Both are code injection flaws that could let a low-privileged attacker execute arbitrary code without any user interaction, according to the NVD record for CVE-2026-113580 and the NVD record for CVE-2026-113579.

If you run AEM yourself, or manage it for clients, treat this as a priority to review. The public records are short, so this article separates what is confirmed from what is still unknown, and focuses on how to prepare while you read Adobe's bulletin.

What was disclosed

Both NVD entries carry the same text: AEM is affected by an Improper Control of Generation of Code vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could exploit it, no user interaction is required, and the scope is changed. Both reference a single Adobe bulletin, APSB26-189, and both were published on 2026-11-10.

CVSS score for each CVE
9.9
CVE identifiers with the same description
2

The research does not explain how the two CVEs differ from each other. They may be separate injection points, but the sources do not say, so do not assume that fixing one addresses the other. Only one independent publisher covers this story so far, and the sources available are the NVD records themselves.

What the weakness means in plain terms

Code injection happens when an application builds code from input that an attacker can influence, and then runs it. Instead of treating the input as data, the system treats part of it as instructions. The result described here is code running as the current user, meaning the account or service context the application uses at that moment.

Three phrases in the description matter for risk:

  • Low-privileged attacker: the attacker needs some account, but not an administrator. On a site with many authors, contributors or registered users, that bar may be low.
  • Scope is changed: a successful attack can affect resources beyond the vulnerable component itself, which is typically why scores for such flaws are so high.
  • No user interaction: nobody has to click a link or open a file for the attack to work.

Who is realistically exposed

Any organization running Adobe Experience Manager is in scope until Adobe's bulletin says otherwise for its version. Exposure is likely to be higher where:

  • AEM author or publish instances are reachable from the internet or from a large internal user base.
  • Many people hold accounts, such as content authors, agency staff or partners.
  • Accounts are shared, weakly protected or not reviewed regularly.
  • AEM runs with broad access to internal systems, databases or file storage.

The research does not state which versions, deployment types or configurations are affected, so do not rule yourself out based on assumptions. Confirm with the vendor bulletin.

How to check your exposure

Start by finding every AEM instance you own, including staging, development and agency-hosted ones, then record the version of each. Compare that against the affected and fixed versions listed in Adobe's bulletin APSB26-189. The research does not include version numbers, so that bulletin is the source of truth.

Also review who can log in. Because the attacker needs only low privileges, a list of active accounts and their roles tells you how many people could theoretically reach the flaw.

What to do now

  1. Inventory all Adobe Experience Manager instances, including non-production and agency-managed ones, and note each version.
  2. Open Adobe bulletin APSB26-189 and confirm whether your versions are affected and which fixed version or patch applies.
  3. Schedule the update on a short timeline given the CVSS 9.9 rating, testing on staging first if you can.
  4. Remove or disable unused and shared accounts, and enforce strong passwords and multi-factor authentication for the rest.
  5. Restrict network access to author instances so they are not exposed to the open internet unless required.
  6. Review recent logs and content changes for unexpected activity from low-privileged accounts, and keep those logs.
  7. Make sure you have a recent, tested backup before patching.
Caution. Applying updates to a production AEM instance usually involves a restart and can affect custom code and packages. Test on staging and plan a maintenance window before changing production.

If a patch is not yet available for your version, the research does not describe any workaround. Reduce exposure with the access and account steps above and check Adobe's bulletin for updates.

Detection and monitoring afterwards

The sources give no indicators of compromise and no confirmation of exploitation, so there is no specific signature to hunt for. General signs worth watching after any code execution flaw include unexpected new content or packages, new or changed accounts, unfamiliar scheduled jobs, and outbound connections from the AEM server that you do not recognize.

An outside-in view helps with the public side of your site. A free website malware scanner can check for visible injected content, and monitoring can alert you to certificate, DNS and header changes. Neither can see inside your server, so keep server-side logging in place. For background, see what outside-in malware detection can and cannot see.

If you find signs of compromise, follow the steps in Website hacked: what to do.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-113580: Adobe Experience Manager is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability that could result in arbitrary code…nvd.nist.gov ·
  2. CVE-2026-113579: Adobe Experience Manager is affected by an Improper Control of Generation of Code ('Code Injection') vulnerability that could result in arbitrary code…nvd.nist.gov ·
  • Adobe
  • Experience Manager
  • Code injection
  • CVE-2026-113580
  • CMS security