Automated Threat Modeling

Brief Summary: Adobe Experience Manager CVE 2026 114371, Incorrect Authorization Leading to Code Execution

A brief summary of CVE 2026 114371, a CVSS 9.9 incorrect authorization flaw in Adobe Experience Manager that lets a low-privileged user execute arbitrary code. Covers affected versions, Adobe's fixed builds and hotfix, a hotfix identifier conflict, and what version-based detection can and cannot tell you.

CVE Analysis

9 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Brief Summary: Adobe Experience Manager CVE 2026 114371, Incorrect Authorization Leading to Code Execution

Introduction

An authorization check in Adobe Experience Manager (AEM) that exists but makes the wrong decision lets a user holding only a low-privileged account execute arbitrary code, and Adobe scores the result 9.9 with a changed scope. For organizations that give many internal or partner users ordinary authoring access to AEM, any one of those logins is a starting point for code execution on the platform.

AEM is Adobe's platform for content management, digital asset management, digital forms and related digital experiences. AEM Sites delivers content across web, mobile and apps, and AEM Assets handles the sourcing, adaptation and delivery of digital assets. AEM ships both as AEM as a Cloud Service and as the classic AEM 6.5 and AEM 6.5 LTS lines, and all three are affected. Adobe reports that AEM was named number one Content Management Software in the 2026 G2 Best Software Awards, which is a product recognition rather than a market share figure.

Technical Information

Root cause: CWE 863, Incorrect Authorization

Adobe classifies CVE 2026 114371 as CWE 863, Incorrect Authorization. MITRE defines this weakness as an authorization check that is present but does not correctly determine whether an actor may access a resource or perform an action. That differs from a missing authentication control. The attacker is identified, but the server grants them an operation their permissions should not allow.

In this AEM case, the published description states that a low-privileged attacker could exploit the incorrect authorization to execute arbitrary code in the context of the current user, without user interaction, and that the scope is changed. Because the end result is code execution, this cannot be treated as a content visibility or permission management issue alone.

The fix necessarily lives in server-side authorization logic, for example tighter permission checks on a servlet, endpoint or repository path. Adobe has not said which component or check changed. AEM is closed source, with no public commit, diff or pull request and no published vulnerable code, so there is no code-level detail to show.

CVSS 3.1 breakdown

Adobe's published vector:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
  • Attack Vector: Network. Exploitation happens through a network-reachable component.
  • Attack Complexity: Low. No specialized access conditions or extenuating circumstances are required.
  • Privileges Required: Low. The attacker needs an account with basic user capabilities. This is not an unauthenticated bug.
  • User Interaction: None. No other user has to do anything.
  • Scope: Changed. Impact extends beyond the security scope of the vulnerable component.
  • Confidentiality, Integrity, Availability: High.

The 9.9 is Adobe's CNA score as displayed by NVD, which notes that a NIST assessment has not yet been provided. As FIRST's specification points out, base metrics describe intrinsic severity, not exploit maturity or likelihood of attack.

Attack flow, as far as the advisories describe it

The public record supports the following sequence, and nothing more granular:

  1. The attacker holds a valid low-privileged account on an affected AEM instance (PR:L).
  2. The attacker sends network requests to a reachable AEM component (AV:N). No other user needs to act (UI:N), and no special conditions are needed (AC:L).
  3. A server-side authorization check that exists but is incorrect or incomplete permits an operation the account should not be able to perform.
  4. That operation leads to arbitrary code execution in the context of the current user.
  5. Because scope is changed, the impact reaches beyond the vulnerable component's own security authority, with high confidentiality, integrity and availability impact.

The affected endpoint, request format, protocol details, payload, and the specific authority affected by the scope change are all undisclosed. Claims of administrator-level outcomes or cross-tenant compromise are not supported by the published material.

The researcher credited for CVE 2026 114371 is edra, who is also credited for CVE 2026 113580 and CVE 2026 113579, two critical code injection bugs (CWE 94) fixed by the same Cloud Service release and the same cumulative hotfix. Adobe has not said whether these are separate root causes or a single exploit chain fixed in several places.

Patch Information

Adobe fixed CVE 2026 114371 in security bulletin APSB26 189, published November 10, 2026 with Priority 2, which Adobe's rating guidance describes as act within 30 days. No workaround is documented, and fixes ship only as vendor builds and hotfix packages.

Fixed builds by deployment type

  • AEM as a Cloud Service: vulnerable at 2026.10.29023 and earlier; fixed in release 2026.10.29251.
  • AEM 6.5: vulnerable at Service Pack 25 and earlier; fixed by the Cumulative Hotfix for GRANITE 75052 (packages listed for Service Packs 23, 24 and 25).
  • AEM 6.5 LTS: vulnerable at Service Pack 3 and earlier; fixed by the Cumulative Hotfix for GRANITE 75052 (packages listed for Service Packs 1, 2 and 3).

How the fix reaches each line

  • Cloud Service: the fix is in maintenance release 29251. Adobe's release notes say it was publicly released on November 3, 2026, one week before the bulletin, and that the previous release was 29023. The notes contain only a general Security Fixes section stating that the release includes 18 security fixes, with no per-CVE detail, so the changelog will not help you map this specific issue. They confirm that the release exists, not that any particular environment has received it.
  • AEM 6.5 and 6.5 LTS: the fix is a cumulative hotfix named after its Granite tracking ticket, not a new service pack. Cumulative means it bundles earlier Granite fixes together with the new ones. You install it on top of your current service pack. Running 6.5 SP25 or 6.5 LTS SP3 alone does not mean you are patched, since both remain in the affected range.

One package, several bugs. The same Cloud Service release and the same GRANITE 75052 hotfix are listed as the fix for most issues in the bulletin. Installing the single package closes all of them, and partial installation is not an option. The bulletin also lists an AEM 6.5 SP25 Forms QuickStart hotfix (version 1.0.12, for instances not running Forms Add On) and an SP25 Forms Add On update. These are separate solution entries, and the bulletin does not establish that every component update is required for this particular CVE.

Ticket number conflict. NVD's affected products data, sourced from the CNA feed, names GRANITE 75398 as the unaffected hotfix for 6.5.25 and 6.5 LTS SP3. Adobe's bulletin names GRANITE 75052 for this CVE and every other Granite fixed issue in the bulletin. The sources do not establish that the two identifiers are equivalent. We treat the vendor bulletin as authoritative and expect the NVD entry to be corrected. If both numbers appear in your internal tickets, check which package is actually installed.

No tracked package version. The GitHub Advisory Database entry for this CVE is unreviewed and lists no affected packages or patched versions. Dependabot and similar dependency scanners will not flag or clear this CVE automatically. Verify manually: Cloud Service environments should run release 29251 or later, and on-premises and managed 6.5 or 6.5 LTS instances should have the GRANITE 75052 cumulative hotfix installed on top of the current service pack.

Detection Methods

Exploitation status

Adobe's bulletin states: "Adobe is not aware of any exploits in the wild for any of the issues addressed in this update." It contains no indicators of compromise, request patterns or log signatures, and neither NVD nor SecurityOnline's CVE Watchtower (which lists "No confirmed exploitation yet") adds any. OffSeq's dated snapshot reports no exploitation evidence, no attack traffic on its Mirage sensors, no public exploit in Metasploit or Exploit DB, no Nuclei template and no CISA KEV entry at the time. No threat actor or campaign has been named. In practice, detection today means finding and checking versions, because there are no known attacks to spot.

Tenable Nessus plugin 378188

Tenable's plugin Adobe Experience Manager 2026.0.0 < 2026.10.29251 Multiple Vulnerabilities covers CVE 2026 114371 along with the other 13 CVEs in the bulletin. The plugin source, mirrored on Vulners, shows how it behaves:

  • Discovery comes first. It depends on adobe_experience_manager_http_detect.nbin and only runs if that plugin has recorded an installed_sw/Adobe Experience Manager entry. If AEM is not fingerprinted, for example behind a reverse proxy or with the version endpoint hidden, the vulnerability check never runs.
  • Default port 4502. It uses HTTP and defaults to port 4502, the usual AEM author instance port. Add any other AEM ports to your scan policy.
  • Simple version comparison. It flags versions from 2026.0.0 up to but not including 2026.10.29251, rated SECURITY_HOLE. It is an ACT_GATHER_INFO remote check usable in both agent and agentless scanning.
  • No vulnerability test. Tenable states Nessus has "not tested for these issues but has instead relied only on the application's self-reported version number." A hit means the version is in range; it neither confirms exploitability nor indicates prior compromise.

The plugin's displayed CVSS score cites a different CVE as its score source. The 9.9 rating for this CVE comes from Adobe's CNA data.

The blind spot: AEM 6.5 and 6.5 LTS

The plugin's only version rule covers the 2026.x numbering used by AEM as a Cloud Service. For AEM 6.5 and 6.5 LTS, the fix is a cumulative hotfix, and installing a hotfix normally does not change the product version number, so a version-only check cannot separate a patched 6.5 SP25 server from an unpatched one. Confirm the hotfix in AEM's package inventory instead. Check against Adobe's GRANITE 75052 identifier, and do not mark a server clean simply because it lacks one of the two conflicting IDs.

Hunting without signatures

With no public signatures, hunting has to follow from what the advisories say:

  • An attacker needs a valid low-privileged login, so author instances and any interface where non-admin users can sign in matter most. Review what low-privileged accounts are doing on those systems.
  • Scope is changed and the outcome is code execution, so on AEM hosts look for unexpected child processes started by the AEM Java process and unusual outbound connections.
  • Treat these as broad hunting leads, not detections. If detection content or a write-up appears later, check it against Adobe's bulletin before relying on it.

A clean scan does not rule out compromise.

Affected Systems and Versions

  • Adobe Experience Manager as a Cloud Service: 2026.10.29023 and earlier. Fixed in 2026.10.29251.
  • Adobe Experience Manager 6.5: Service Pack 25 and earlier. Fixed by the GRANITE 75052 cumulative hotfix (packages for SP23, SP24 and SP25).
  • Adobe Experience Manager 6.5 LTS: Service Pack 3 and earlier. Fixed by the GRANITE 75052 cumulative hotfix (packages for SP1, SP2 and SP3).

Adobe's bulletin covers all platforms for these product families. Exploitation requires a low-privileged account on the target instance.

Vendor Security History

Adobe documents a Secure Product Lifecycle integrated across design, development, QA, testing and deployment, reporting several hundred security activities, automated development tooling and controls aimed at the OWASP Top 10 and CWE/SANS Top 25, with a Cyber Defense Center and PSIRT handling threats. For this CVE, the concrete response is the published bulletin, affected release data, remediation entries and researcher credit to edra.

Two historical data points provide context, though neither relates to this CVE:

  • October 2013 breach. Adobe disclosed illegal access to customer information and source code for numerous products, initially citing information on 2.9M customers (names, encrypted payment card numbers, expiration dates, order information). Reuters later reported that about 38M records from the customer database had been stolen. These figures describe different reporting stages and data categories.
  • CVE 2025 54253. CISA added this AEM Forms code execution vulnerability to its Known Exploited Vulnerabilities Catalog on October 15, 2025, based on evidence of active exploitation. No equivalent confirmation exists for CVE 2026 114371.

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