Automated Threat Modeling

Brief Summary: Adobe Experience Manager 6.5 CVE 2026 119017 Incorrect Authorization Leading to Code Execution

A brief summary of CVE 2026 119017, a critical incorrect authorization flaw (CWE 863) in classic Adobe Experience Manager 6.5 that lets a low-privileged user execute arbitrary code. Includes patch details, a note on conflicting hotfix identifiers, and detection guidance.

CVE Analysis

8 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Experience Manager 6.5 CVE 2026 119017 Incorrect Authorization Leading to Code Execution

Introduction

A critical authorization flaw in classic Adobe Experience Manager 6.5 lets an authenticated user holding only low privileges execute arbitrary code. No user interaction is required, and the impact reaches beyond the vulnerable component. Adobe fixed it in security bulletin APSB26 189 on November 10, 2026. The instances that need attention are on-premises AEM 6.5 deployments at Service Pack 25 or earlier. AEM as a Cloud Service and AEM 6.5 LTS are not affected.

Adobe Experience Manager (AEM) is Adobe's content management product for content across channels, covering digital asset management, content management, digital documents, forms, structured content, and learning management systems. Adobe's annual report for fiscal year 2025 identifies Digital Media and Digital Experience as its reportable segments and lists Experience Manager among its products. AEM commonly sits behind an organization's public web presence and asset pipeline, so a code execution path open to ordinary authenticated accounts matters to more than the CMS team.

Technical information

Root cause

CVE 2026 119017 is classified as CWE 863, Incorrect Authorization. The product performs an authorization check, but performs it incorrectly, so an actor can reach a resource or action their role should not allow. Adobe's description states that a low-privileged attacker can exploit this to execute arbitrary code in the context of the current user, that exploitation does not require user interaction, and that scope is changed.

Adobe has not published the vulnerable endpoint, component, request sequence, detailed root cause, or a proof of concept. AEM is closed source, so there is no public commit, pull request or diff to review. The fix ships as a binary hotfix package. Two observations still narrow things down:

  • Only classic AEM 6.5 carries the vulnerable path. Adobe's bulletin marks AEM 6.5 LTS and AEM as a Cloud Service as not affected by this CVE. That is unusual within APSB26 189. Most other entries, such as CVE 2026 114371, CVE 2026 113580 and CVE 2026 113579, are fixed across all three product lines. Only CVE 2026 119017 and CVE 2026 118482 are limited to classic AEM 6.5, which indicates the flawed authorization logic exists only in the classic 6.5 codebase and not in the LTS or Cloud Service branches.
  • The fix name points at Granite. The hotfix carries a GRANITE prefix. Adobe Granite is the platform layer under AEM that covers request handling, access control and the admin UI. Reading the prefix as the location of the change is our inference, not something Adobe states, but it fits an authorization flaw in which a low-privileged, authenticated user can reach a feature they should not.

CVSS breakdown

Adobe rates the issue 9.9 (Critical) under CVSS 3.1:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS elementValueMeaning
Attack vectorAV:NNetwork
Attack complexityAC:LLow
Privileges requiredPR:LLow
User interactionUI:NNone
ScopeS:CChanged
ConfidentialityC:HHigh impact
IntegrityI:HHigh impact
AvailabilityA:HHigh impact

Attack flow

Based on the published description and vector (no exploit specifics have been released), exploitation follows this general shape:

  1. The attacker holds a valid low-privileged account on an AEM 6.5 instance (PR:L). Unauthenticated access alone is not enough.
  2. The attacker sends requests over the network (AV:N) to functionality guarded by the incorrectly implemented authorization check, reaching an action their role should not permit. No specific endpoint has been published.
  3. The flawed check lets the action proceed, resulting in arbitrary code execution in the context of the current user. Attack complexity is low (AC:L) and no victim interaction is needed (UI:N).
  4. Because scope is changed (S:C), the consequences extend beyond the vulnerable component, with high confidentiality, integrity and availability impact.

Exploitation status

Adobe states it is not aware of any exploits in the wild for the issues addressed by APSB26 189, and Tenable lists the CVE with no known exploits available. No threat actor has been attributed to this vulnerability. This is the status at publication, not a guarantee of ongoing non-exploitation.

Patch information

Adobe fixed CVE 2026 119017 in security bulletin APSB26 189, released November 10, 2026 as a Priority 2 update. The Priority 2 rating applies to the bulletin as a whole, which covers both critical and medium issues. The CVE itself is rated critical at 9.9. The fix for AEM 6.5 is the Cumulative Hotfix for GRANITE 75052.

Which products need the hotfix

Product lineStatus for CVE 2026 119017
AEM 6.5 (Service Pack 25 and earlier)Fixed by Cumulative Hotfix for GRANITE 75052
AEM 6.5 LTSNot affected
AEM as a Cloud ServiceNot affected

How the fix is shipped

The fix is a binary hotfix package installed on top of your Service Pack. According to SmartScope's summary of Adobe's solution table, the GRANITE 75052 cumulative hotfix comes as separate builds for SP23, SP24 and SP25. Install the build that matches your current Service Pack.

"Cumulative" means one package fixes every Granite layer issue in this bulletin at once. Installing it also addresses the critical code injection and authorization bugs CVE 2026 113579, CVE 2026 113580 and CVE 2026 114371, along with most of the stored and DOM-based XSS issues in APSB26 189.

Conflicting hotfix identifiers

The official CVE record, added to the CVE list in cvelistV5 commit 5f05eb4 and mirrored on NVD, names a different package. Its affected product data marks version 6.5.25 with the Cumulative Hotfix for GRANITE 75398 as unaffected (version type custom), while Adobe's bulletin names GRANITE 75052.

The same GRANITE 75398 label appears in every APSB26 189 CVE record in that commit. That pattern points to a labeling inconsistency in the records rather than a second, separate fix for this CVE. Adobe's bulletin is the authoritative source for which package to install. Teams that match scanner output against CVE or NVD version data should expect this mismatch and confirm against the bulletin before marking an instance fixed.

Mapping the fix to versions

  • Vulnerable: AEM 6.5 up to and including 6.5.25 (SP25) without the hotfix.
  • Fixed: AEM 6.5 SP23, SP24 or SP25 with the matching Cumulative Hotfix for GRANITE 75052 installed.

The sources state no temporary workaround short of the hotfix.

Detection methods

Detection today is limited to version-based exposure checks. No public exploit signature, YARA rule, Sigma rule or IoC exists for CVE 2026 119017, and the community Yara Rules CVE index has no entry for it. For now, detection means finding vulnerable AEM 6.5 instances, not catching attacks in progress.

Tenable Nessus plugin 378188

Tenable published plugin 378188 on November 10, 2026, titled Adobe Experience Manager 2026.0.0 < 2026.10.29251 Multiple Vulnerabilities (APSB26 189), with CVE 2026 119017 among its references. It runs on the Nessus scanner and Nessus Agent (Windows, macOS, Unix) and requires the KB item installed_sw/Adobe Experience Manager, so an earlier detection plugin must identify AEM first. It then compares the version AEM reports about itself against the fixed build.

Tenable notes that Nessus has not tested for these issues and relies only on the application's self-reported version number. The plugin sends no probe that triggers the authorization flaw. A hit means an instance is likely exposed, not that it was attacked, and a modified or hidden version string could mislead it.

Coverage gap: the plugin's version range (2026.0.0 up to but not including 2026.10.29251) matches AEM as a Cloud Service builds, yet Adobe says Cloud Service and AEM 6.5 LTS are not affected by this CVE. In practice:

  • If the plugin flags a Cloud Service instance, the cause is most likely the other APSB26 189 CVEs it covers, not this one.
  • Do not assume the plugin will catch on-premises AEM 6.5 SP25 systems. Check them directly.

Checking AEM 6.5 instances yourself

Since only classic AEM 6.5 is affected, the most reliable check is an inventory of every AEM 6.5 author and publish instance:

  1. Confirm the Service Pack level. SP25 or earlier is in scope.
  2. Confirm whether the cumulative hotfix is installed. Treat an instance at SP25 or earlier without it as vulnerable.

When checking installed packages, look for both GRANITE 75052 (Adobe's bulletin) and GRANITE 75398 (the CNA-supplied data on NVD), and treat Adobe's bulletin as the authority.

Watching for exploitation

No vendor or researcher has published request patterns, log strings or endpoint indicators for this CVE. The following hunting ideas come from the vulnerability class and vector only:

  • Unauthenticated scanning will not catch it. An attacker needs a valid low-privilege account, so reviewing which AEM accounts can authenticate, and from where, is a useful first triage step.
  • Role-exceeding activity. Look for low-privilege AEM accounts making unexpected configuration or code-related changes.
  • Process activity. Watch for new child processes started by the AEM Java process.
  • Lateral reach. Because scope is changed, watch for unusual connections from AEM hosts to other systems.

Recheck Adobe's bulletin and vendor rule feeds for exploit-specific content as research continues.

Affected systems and versions

  • Affected: Adobe Experience Manager 6.5, versions 0 through 6.5.25 (Service Pack 25 and earlier), without the Cumulative Hotfix for GRANITE 75052.
  • Fixed: AEM 6.5 SP23, SP24 or SP25 with the matching Cumulative Hotfix for GRANITE 75052. The CVE record separately lists 6.5.25 with the Cumulative Hotfix for GRANITE 75398 as unaffected. See the identifier discussion above.
  • Not affected: AEM 6.5 LTS and AEM as a Cloud Service.
  • Configuration note: exploitation requires a valid low-privileged account on the instance. Include both author and publish instances running classic AEM 6.5 in scope reviews.

APSB26 189 covers multiple vulnerabilities and lists other AEM release tracks in its product table, but that table alone should not be read as proof that every listed track is affected by this specific CVE.

Vendor security history

APSB26 189 is a multi-issue bulletin. Alongside CVE 2026 119017, it addresses other critical code injection and authorization flaws (CVE 2026 113579, CVE 2026 113580, CVE 2026 114371), another issue limited to classic 6.5 (CVE 2026 118482), and a set of stored and DOM-based XSS issues. Adobe maintains a public security bulletin index with entries spanning multiple years. Its FY2025 annual filing states that maintaining solution security is critical and describes a CSO supported by cybersecurity, information security, information technology, operations and legal professionals. These facts show stated governance and an active public disclosure process. The reviewed sources are not sufficient to score Adobe's overall security performance.

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