On this page (7 sections)
Adobe Experience Manager (AEM) is affected by an Incorrect Authorization vulnerability, tracked as CVE-2026-119017, that could lead to arbitrary code execution in the context of the current user. A second entry, CVE-2026-114371, carries an identical description and score and points to the same Adobe bulletin.
If you run AEM yourself or manage it for a client, treat this as a priority item to review. The public records are short, so this article separates what is confirmed from what you will need to read in Adobe's bulletin.
What was published
Both CVE records were published on 2026-11-10 and reference a single Adobe security bulletin, APSB26-189. The NVD entries for CVE-2026-119017 and CVE-2026-114371 describe the problem in the same words: an Incorrect Authorization flaw in Adobe Experience Manager that could result in arbitrary code execution in the context of the current user.
According to the description, a low-privileged attacker could exploit it, no user interaction is required, and the scope is changed. Both records list a CVSS score of 9.9.
What the weakness means in plain terms
CWE-863 describes a system that checks whether a user is allowed to do something, but performs that check incorrectly. The user is logged in, yet the application lets them reach an action or resource that their role should not permit. In a content platform like AEM, where many people hold accounts with different rights (authors, reviewers, contributors), that gap matters because those accounts are the low-privileged starting point.
The phrase 'scope is changed' in the description means the impact can extend beyond the component that has the flaw. Combined with code execution and no user interaction, that is consistent with the 9.9 score. The records do not say which AEM feature, endpoint or deployment type is involved, and we do not guess at that here.
Who is realistically exposed
- Organizations that run AEM on their own servers or in a private cloud, where you control patching.
- Agencies and hosting teams that operate AEM author or publish instances for clients.
- Any AEM environment where many people or external contributors hold low-privileged accounts, since the description says the attacker is low-privileged.
- Instances where author systems are reachable from the internet or from broad internal networks.
The records do not say whether managed or Adobe-hosted AEM deployments are affected or already updated. Check with Adobe or your account contact rather than assuming either way.
How to check your exposure
Start with an inventory. You need to know which AEM instances you run, which version and service pack each one is on, and who can log in to them.
- List every AEM author and publish instance, including staging and test systems that may have been forgotten.
- Record the installed version and any service pack or cumulative fix pack on each one.
- Open Adobe bulletin APSB26-189 and compare your versions with the affected and fixed versions it lists.
- Review accounts on author instances: remove unused users and check which groups and permissions low-privileged accounts hold.
- Note which instances are reachable from the internet and which only from internal networks.
What to do now
- Read Adobe bulletin APSB26-189 and confirm whether your AEM versions are affected.
- Apply the update or fix that Adobe lists for your version, testing on staging first.
- Treat both CVE-2026-119017 and CVE-2026-114371 as covered by your review, since the records point to the same bulletin.
- Restrict network access to author instances so they are not exposed more widely than needed.
- Audit low-privileged accounts and remove any that are unused or unexpected.
- Review logs on author instances for unusual activity from low-privileged users, such as unexpected content or configuration changes.
- Check the CISA Known Exploited Vulnerabilities catalog and Adobe's bulletin yourself for any exploitation updates.
- Record the patch date for each instance so you can show it was done.
Detection and monitoring afterwards
The research contains no report of active exploitation and no CISA KEV data for these CVEs, so exploitation status is unconfirmed rather than ruled out. Check the CISA KEV catalog, Adobe's bulletin and your vendor channels again after patching, since the picture can change.
- Watch authentication and audit logs on author instances for low-privileged accounts doing things outside their normal role.
- Alert on new or modified code, packages or scheduled jobs on the server.
- Keep an eye on public-facing pages for unexpected scripts or content changes. The free website malware scanner gives an outside-in view, and what outside-in detection can and cannot see explains its limits: it cannot confirm that a server-side flaw is patched.
- Use certificate, DNS and header-change monitoring to notice unplanned changes on the sites your AEM instances serve.
If you suspect an instance was abused before patching, follow a structured response such as website hacked: what to do. For a broader routine around patching and account hygiene, see small business website security.
What we do not know yet
- Which AEM versions are affected and which contain the fix.
- Which component or feature the incorrect authorization lies in.
- Why two CVE identifiers share one description and bulletin, and whether they are two distinct flaws or two records of the same behavior.
- Whether anyone is exploiting the issue in the wild.
Adobe's bulletin is the authority for these points. We will not fill the gaps with assumptions.
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.
- CVE-2026-119017: Adobe Experience Manager is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current…
- CVE-2026-114371: Adobe Experience Manager is affected by an Incorrect Authorization vulnerability that could result in arbitrary code execution in the context of the current…
