Automated Threat Modeling

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

A brief summary of CVE 2026 113579, a CVSS 9.9 code injection flaw in Adobe Experience Manager that lets a low-privileged user execute arbitrary code. Covers the fixed Cloud Service build, the cumulative GRANITE hotfix for AEM 6.5 and 6.5 LTS, and a hotfix identifier mismatch to resolve before patching.

CVE Analysis

7 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

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

Introduction

A code injection flaw in Adobe Experience Manager (AEM) lets an attacker holding only a low-privileged account execute arbitrary code over the network, with no user interaction and a changed scope. Adobe scored it 9.9 under CVSS 3.1 and shipped fixes for AEM as a Cloud Service, AEM 6.5, and AEM 6.5 LTS in security bulletin APSB26 189 on November 10, 2026.

AEM is Adobe's enterprise digital experience platform. It combines content management and digital asset management, and teams use it to create, govern, and publish experiences across web and mobile channels. Adobe states it was named a Leader in the 2025 Gartner Magic Quadrant for Digital Asset Management Platforms. That is a category recognition reported on Adobe's own site, not a measure of overall market share. AEM typically sits behind an organization's public web properties and asset workflows, so a code execution flaw in its core platform layer matters to content teams and to the infrastructure teams that run it.

Technical Information

Root cause class

CVE 2026 113579 is classified as CWE 94, Improper Control of Generation of Code ('Code Injection'). MITRE describes this weakness class as code constructed from externally influenced input that is not correctly neutralized. That definition characterizes the class of bug, not the specific faulty AEM component. Adobe's description states the impact as arbitrary code execution in the context of the current user.

AEM is closed source, and Adobe ships fixes as compiled builds and hotfix packages, so there is no public source diff or commit to inspect. Adobe has not disclosed the vulnerable endpoint, the specific component, a request format, or a payload.

CVSS breakdown

The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, base score 9.9 (Critical). Read against the CVSS 3.1 specification:

  • AV:N: exploitable over the network.
  • AC:L: no specialized access conditions or extenuating circumstances are required.
  • PR:L: the attacker needs low-level privileges, so some authenticated access is assumed.
  • UI:N: no action by another user is needed.
  • S:C: impact can extend beyond the security scope of the vulnerable component.
  • C:H / I:H / A:H: high confidentiality, integrity, and availability impact.

NVD displays the Adobe-supplied score and notes that its own assessment has not yet been provided. The 9.9 should be attributed to Adobe as CNA rather than treated as an independent NIST rating.

Where the bug most likely lives

The packaging of the fix gives one useful signal. For AEM 6.5 and 6.5 LTS, the fix is a cumulative hotfix under the GRANITE name. GRANITE is AEM's core platform layer, covering the Sling, JCR, and OSGi plumbing. A fix delivered as a GRANITE hotfix suggests the vulnerable code is in that shared layer rather than in an add-on such as Forms. The same bulletin ships AEM Forms XSS fixes as separate Forms add-on packages, which supports that reading.

The same researcher, credited as edra, reported two sibling issues in the same bulletin, both also rated 9.9:

  • CVE 2026 113580: code injection (CWE 94)
  • CVE 2026 114371: incorrect authorization (CWE 863)

All three share identical fix notes. Our reading is that pairing an authorization flaw with two code injection flaws hints the fix both tightens who can reach a code-generating feature and controls what input reaches it. That is inference only. Adobe has not published root cause details.

Attack flow as described by the record

The public record supports only the abstract model encoded in the CVSS vector and CWE classification:

  1. The attacker holds a low-privileged account on the target AEM instance (PR:L).
  2. The attacker reaches the affected functionality over the network (AV:N), with no special conditions required (AC:L).
  3. The affected component uses attacker-supplied input to construct code without correct neutralization (the CWE 94 pattern).
  4. The generated code executes in the context of the current user, with no victim interaction (UI:N).
  5. The resulting impact crosses the vulnerable component's security scope (S:C), with high impact to confidentiality, integrity, and availability.

We are deliberately not describing a more specific exploitation method. The reviewed records do not identify the vulnerable code path, request format, payload, or CVE-specific indicators of compromise, and the severity score alone does not support inferring one.

Exploitation status

Adobe states it is not aware of exploits in the wild for the issues covered by APSB26 189. The CVE record includes a CISA ADP assessment of Exploitation none, Automatable no, and Technical Impact total. The reviewed sources report no threat actor, public proof of concept, or observed attack traffic. Adobe nonetheless rated the update Priority 2, which it defines as act within 30 days and associates with a high likelihood of exploitation based on the vulnerability, product history, and platform.

Patch Information

Adobe fixed CVE 2026 113579 in APSB26 189, published November 10, 2026. Fixed builds by product line:

  • AEM as a Cloud Service: 2026.10.29023 and earlier are vulnerable. The fix is in release 2026.10.29251.
  • AEM 6.5: Service Pack 25 and earlier are vulnerable. The bulletin names the Cumulative Hotfix for GRANITE 75052 as the fix (the CVE record names GRANITE 75398).
  • AEM 6.5 LTS: Service Pack 3 and earlier are vulnerable. The bulletin names the Cumulative Hotfix for GRANITE 75052 as the fix (the CVE record names GRANITE 75398).

How the fix is delivered

  • Cloud Service: Adobe operates the service and rolls out releases itself, so the fix is a platform release. The CVE record marks 2026.10.29251 as unaffected and everything up to 2026.10.29023 as affected. Any environment on build 29251 or later has the fix.
  • On-premise and AMS, 6.5 and 6.5 LTS: there is no new service pack. The fix is a cumulative hotfix installed on top of the current service pack. The bulletin lists cumulative hotfixes for AEM 6.5 Service Packs 23, 24, and 25, and for AEM 6.5 LTS Service Packs 1, 2, and 3. The CVE record lists the fixed states as 6.5.25 and 6.5 LTS SP3 with the Cumulative Hotfix for GRANITE 75398.

The bulletin also lists separate Forms-related packages for AEM 6.5 Service Pack 25, including a Forms QuickStart hotfix for instances not running the Forms Add On and a Forms Add On package. Apply those only where they match your installed Forms configuration and the package conditions stated in the advisory.

Mismatched hotfix identifier

The two authoritative sources disagree on the package name for 6.5 and 6.5 LTS:

  • Adobe's bulletin names the Cumulative Hotfix for GRANITE 75052.
  • The CNA-published CVE JSON in CVEProject/cvelistV5, which NVD also reflects, names GRANITE 75398.

Adobe is the CNA and authored both, so this is most likely a typo or a later rebuild of the package. Treat the bulletin and Adobe's Software Distribution listing as the authority on which package to install, and verify the installed package version against that listing. If the bulletin's package links do not resolve the discrepancy, confirm with Adobe support.

One hotfix covers three bugs

CVE 2026 113579, CVE 2026 113580, and CVE 2026 114371 have identical fix notes: Cloud Service 2026.10.29251 and the same cumulative GRANITE hotfix for 6.5 and 6.5 LTS. In practice, one package closes all three.

Third-party trackers

The GitHub Advisory Database entry (GHSA 3r46 jjv8 qj62) is unreviewed, with an empty affected package list and no patched version, because AEM is not distributed through a package ecosystem such as Maven or npm. Dependency scanners will not give you reliable version data here, so use Adobe's bulletin and the CVE record.

Affected Systems and Versions

All platforms are listed as affected for each product line:

  • AEM as a Cloud Service: release 2026.10.29023 and earlier. Release 2026.10.29251 and later are unaffected.
  • AEM 6.5: Service Pack 25 and earlier, without the cumulative GRANITE hotfix applied.
  • AEM 6.5 LTS: Service Pack 3 and earlier, without the cumulative GRANITE hotfix applied.

Exploitation requires network reach to the instance and a low-privileged account.

Vendor Security History

Adobe's Product Security Incident Response Team runs its vulnerability disclosure program and accepts private reports at [email protected]. This CVE is credited to edra.

AEM receives regular security bulletins. APSB25 90, published in September 2025, addressed critical and important AEM vulnerabilities, and Adobe stated at the time that it was not aware of exploits in the wild for those issues.

A separate 2025 incident should be kept distinct. Authorities reported CVE 2025 54253 in AEM Forms on JEE as actively exploited, and CISA added it to the Known Exploited Vulnerabilities catalog. The reporting did not identify threat actors. That is a different CVE in a different product configuration and is not evidence that CVE 2026 113579 is being exploited. It is a reminder to evaluate exposure per CVE and per product rather than from vendor-wide labels.

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