Automated Threat Modeling

Brief Summary: Adobe Experience Manager CVE-2026-113580 Code Injection (CVSS 9.9)

A brief summary of CVE-2026-113580, a CVSS 9.9 code injection flaw in Adobe Experience Manager that lets a low-privileged attacker execute arbitrary code without user interaction. Covers affected versions, Adobe's fix mapping in APSB26-189, and a hotfix identifier discrepancy to check before deployment.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Experience Manager CVE-2026-113580 Code Injection (CVSS 9.9)

Introduction

Adobe's November 10, 2026 security bulletin APSB26-189 fixes a code injection flaw in Adobe Experience Manager (AEM) that lets an attacker holding only a low-privileged account execute arbitrary code, with no user interaction and a changed CVSS scope. For organizations running Sites, Assets, or Forms on AEM, the 9.9 score reflects a short path from a basic account to code execution on a platform that often sits at the center of content and publishing workflows.

Adobe positions Experience Manager within Adobe Experience Cloud, with Sites for creating and delivering digital experiences, Assets for digital asset management, and Forms for digital documents and forms. Adobe states it was named a Leader in the 2025 Gartner Magic Quadrant for Digital Experience Platforms for the eighth consecutive year, which is a vendor claim about recognition rather than a measured market share. Published customer stories, such as Volkswagen Group standardizing content management across its brands on AEM Sites and Assets, show how deeply the platform can be embedded in enterprise content operations.

Technical Information

Root cause

The CVE record classifies the issue as CWE-94, Improper Control of Generation of Code ('Code Injection'). MITRE describes this weakness class as code generation where externally influenced input is incorporated into a code segment without adequate neutralization of elements that change its syntax or behavior. The reported impact is arbitrary code execution in the context of the current user.

That is as far as the public root cause goes. AEM is proprietary, and Adobe has not published a commit, diff, or changelog. The bulletin does not name the affected servlet, script engine, or template path, and it does not describe which input reaches the code generation path or what validation or sandboxing the fix adds. Any more specific description of the vulnerable component would be speculation, so we do not offer one here.

CVSS breakdown

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Base score 9.9 (Critical)

Reading the vector with the FIRST CVSS 3.1 definitions:

  • AV:N, AC:L: the flaw is reachable over the network and does not depend on conditions outside the attacker's control.
  • PR:L: the attacker must already hold low privileges, meaning basic user capabilities or access to non-sensitive resources. This is not an unauthenticated bug, and it should not be described as one.
  • UI:N: once the attacker meets that precondition, no victim action is needed.
  • S:C: exploitation can affect resources beyond the security scope of the vulnerable component. This is a CVSS boundary concept. The records do not say which boundary is crossed, and S:C on its own does not establish administrator access, a container escape, or cross-tenant impact.
  • C:H, I:H, A:H: high potential impact to confidentiality, integrity, and availability.

Attack flow

The public record supports only a precondition-level view of exploitation, not an endpoint- or payload-level one:

  1. The attacker obtains low-privileged access to an affected AEM deployment that is reachable over the network.
  2. The attacker supplies input that reaches a code generation path in AEM without adequate neutralization. The specific input, endpoint, and request format are not documented.
  3. The injected code executes in the context of the current user, with no interaction required from any other user.
  4. Because the scope is changed, the effects can extend beyond the vulnerable component's own security scope. The specific resources affected are not documented.

No reviewed source describes persistence, post-exploitation behavior, or any prerequisites beyond low privileges. We treat that as an intelligence gap rather than evidence that such behavior is impossible.

According to the patch information, the same release and hotfix also fix two other critical 9.9 issues reported by the same researcher ("edra"): CVE-2026-113579, another CWE-94 code injection, and CVE-2026-114371, a CWE-863 incorrect authorization flaw. Several stored and DOM-based cross-site scripting issues in APSB26-189 are covered as well. The shared fix suggests, without proving it, that these bugs live in a common code area that Adobe hardened at once.

Exploitation status

Adobe states it is not aware of exploits in the wild for the issues addressed in APSB26-189. Secondary summaries (CVE Watchtower, VulDB, StackFlag) also list exploitation as not known or not confirmed, without forensic detail. No threat actor is named, and no verified public proof of concept exists. The sources we reviewed did not establish CISA KEV status for this CVE.

Patch Information

Adobe shipped the fix in APSB26-189 on November 10, 2026. The only authoritative patch information is the version-to-fix mapping in that bulletin.

How the fix is delivered

  • AEM as a Cloud Service: versions 2026.10.29023 and earlier are vulnerable. The fix is release 2026.10.29251. Adobe patches the platform itself, so the fix is present once an environment runs 2026.10.29251 or later. Check the AEM release version your Cloud Manager environments are actually running instead of assuming the platform updated automatically.
  • AEM 6.5: Service Pack 25 and earlier are vulnerable. The fix is the Cumulative Hotfix for GRANITE-75052. Adobe's table provides package links for Service Packs 23, 24, and 25.
  • AEM 6.5 LTS: Service Pack 3 and earlier are vulnerable. The fix is the same Cumulative Hotfix for GRANITE-75052, with package links for Service Packs 1, 2, and 3.

For the 6.5 lines, no new service pack contains the fix. It ships as a cumulative hotfix keyed to a Granite ticket. Granite is the foundation layer of AEM, the platform services underneath Sites, Assets, and Forms, so the fix lands in a core platform package rather than an optional add-on. "Cumulative" means the package rolls up earlier Granite fixes. Install it through Package Manager on top of the current service pack (SP25 for 6.5, SP3 for 6.5 LTS). There is no need to apply older hotfixes first.

Adobe classifies the update as Priority 2, which it defines as an update for a product historically at elevated risk with no currently known or anticipated imminent exploits, and recommends installing soon, for example within 30 days. Neither the Adobe bulletin nor the NVD entry documents a workaround or compensating control.

Conflicting hotfix identifier

The sources disagree on which hotfix fixes the 6.5 lines:

  • Adobe's bulletin names the Cumulative Hotfix for GRANITE-75052 and links its packages.
  • NVD's affected products data, derived from the CVE record Adobe filed, lists the unaffected state as "6.5.25 Cumulative Hotfix for GRANITE-75398" and "6.5 LTS SP3 Cumulative Hotfix for GRANITE-75398".
  • GitHub's advisory GHSA-8fg5-vfp7-7h9g is unreviewed with an empty vulnerabilities array, so it lists no patched package versions.

The vendor bulletin is the primary source, so we treat GRANITE-75052 as the reference fix. Before rollout, confirm in Adobe Software Distribution that the package you download is the one Adobe currently ties to APSB26-189, and keep the discrepancy visible in your remediation records. The CVE record metadata may be corrected later, or Adobe may have reissued the hotfix under a newer ticket number.

What the patch does not tell you

Because Adobe has not published root-cause details, you verify remediation by checking the installed release or hotfix, not by inspecting code.

Affected Systems and Versions

  • AEM as a Cloud Service: version 2026.10.29023 and earlier. Fixed in 2026.10.29251.
  • AEM 6.5: Service Pack 25 and earlier. Fixed by the Cumulative Hotfix for GRANITE-75052 (Adobe bulletin). NVD lists GRANITE-75398.
  • AEM 6.5 LTS: Service Pack 3 and earlier. Fixed by the Cumulative Hotfix for GRANITE-75052 (Adobe bulletin). NVD lists GRANITE-75398.

No specific vulnerable configuration beyond these version ranges is documented. The attacker must hold low privileges on the target instance.

Vendor Security History

The most relevant prior AEM issue is Adobe's August 2025 bulletin APSB25-82, which addressed two AEM Forms on JEE vulnerabilities:

  • CVE-2025-54253: an authorization weakness with code execution impact.
  • CVE-2025-54254: an XML external entity issue with file read impact.

Adobe reported public proof of concept code for those issues but said at the time it was not aware of exploitation in the wild. CISA later added CVE-2025-54253 to its Known Exploited Vulnerabilities catalog on October 15, 2025, with a due date of November 5, 2025. That history concerns AEM Forms and different CVEs, not CVE-2026-113580. Its relevance here is narrower. It shows that a vendor's "no known exploitation" statement reflects awareness at a point in time and can change.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization