Skip to main content

Adobe Experience Manager CVE-2026-110084

| EUVDEUVD-2026-100553 HIGH
XML Injection (aka Blind XPath Injection) (CWE-91)
2026-10-13 psirt@adobe.com GHSA-vc68-3wxr-xhq3
7.1
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate with low-privileged AEM account
  2. Delivery
    Submit crafted XPath/XML injection input
  3. Exploit
    Trigger blind XPath query manipulation
  4. Execution
    Bypass security control
  5. Impact
    Read protected data and perform limited writes

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization XPath query parameterization
Exploitation Conditions

Exploitation requires an authenticated low-privileged account on an Adobe Experience Manager 6.5 instance (versions 6.5.0 through 6.5.25) that is network-reachable, per the CVSS vector (AV:N/PR:L/UI:N). The attacker must reach a feature that passes attacker-controlled input into an XPath/XML query without sufficient sanitization; no user interaction or elevated privileges are needed. The primary limiting factor is the PR:L requirement - the attacker must first obtain valid low-privileged credentials or a session, so purely external unauthenticated attackers cannot exploit this directly; impact is further bounded to unauthorized reads and only limited writes (I:L), with no availability impact (A:N).

Impact

The CVSS 3.1 base score of 7.1 (vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) describes a network-reachable, low-complexity flaw requiring low privileges and no user interaction, with high confidentiality impact, low integrity impact, and no availability impact - consistent with the description of a Blind XPath/XML Injection enabling a security feature bypass yielding unauthorized read and limited write access. The PR:L metric means an attacker must already hold a low-privileged account, which meaningfully lowers real-world risk versus a fully unauthenticated flaw and points toward insider or post-foothold abuse rather than mass opportunistic scanning. No EPSS score, SSVC decision, KEV listing, or POC was supplied in the input, so exploitation likelihood cannot be quantified; there is no public exploit identified at time of analysis and no evidence of active exploitation. The 'Authentication Bypass' tag is slightly imprecise - the vendor and NVD characterize this as a security-feature bypass via XPath injection by an already-authenticated low-privileged user, not a pre-auth authentication bypass; treat the tag as a loose label rather than confirmation of unauthenticated access. Net: a genuine but not top-tier priority - a real high-severity issue gated behind existing low-privilege access, warranting prompt patching on internet-facing AEM instances but not emergency zero-day handling absent exploitation signals.

Exploit ScenarioDerived

An attacker who already possesses a low-privileged Adobe Experience Manager account submits crafted input that is unsafely incorporated into an XPath query, inferring protected data through blind true/false response differences and bypassing an intended security control. No user interaction is needed, and the flaw is reachable over the network, letting the attacker read unauthorized content and make limited unauthorized writes. No public exploit code has been identified, so exploitation would currently require independent development.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Blind XPath/XML injection in Adobe Experience Manager 6.5 (versions 6.5.0 through 6.5.25) allows a low-privileged, authenticated attacker to bypass security controls and read content they should not be able to access, with limited unauthorized write capability. The flaw is network-reachable, requires no user interaction, and carries a CVSS 3.1 base score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N), reflecting high confidentiality impact but only low integrity impact and no availability impact; the CVSS vector confirms the attacker must hold a valid low-privileged account (PR:L), so unauthenticated outsiders cannot exploit it directly. No public exploit code or confirmed active exploitation was identified at time of analysis, and Adobe has published a vendor security bulletin (apsb26-152) covering the issue.

RemediationAI

Apply the fix documented in Adobe Security Bulletin apsb26-152 (https://helpx.adobe.com/security/products/experience-manager/apsb26-152.html) - since the affected range terminates at 6.5.25, remediation for the 6.5 line is the cumulative fix pack release that supersedes 6.5.25 as listed in that bulletin; no patch is identified as available from any non-Adobe source, and the exact fixed build number was not supplied in the input data, so confirm it against the advisory before upgrading. Because exploitation is gated by the PR:L vector prerequisite, the single highest-value compensating control is credential hygiene on AEM: audit and disable unnecessary low-privileged author and publish accounts, enforce MFA on the author tier, rotate any credentials that may have been exposed, and remove anonymous/default accounts - the trade-off is added administrative friction and possible disruption of automated service accounts. Restrict network reachability of AEM author and publish instances with firewall rules and Dispatcher configurations so that only trusted networks and integrations can reach query-bearing endpoints such as the QueryBuilder API, accepting that this may break legitimate remote or partner access unless allow-listed. Deploy WAF/edge filtering that rejects requests containing XPath/XML metacharacter patterns (unbalanced quotes, ' or ', ']', '::', boolean-operator sequences) in query parameters; this is detection-friendly but prone to false positives on legitimate search traffic and must be tuned. Enable and monitor AEM audit and request logs for anomalous repetitive query patterns characteristic of blind boolean-based extraction, and apply least-privilege ACLs so that compromised low-privileged accounts have minimal readable content, understanding that logging and ACL tightening add operational overhead but do not eliminate the underlying injection flaw.

Affected VersionsENISA

Adobe Experience Manager 6.5 0 ≤6.5.25

Affected Packages

euvd adobe_experience_manager_6_5 no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is an XML Injection issue in the CWE-91 class, realized here as Blind XPath Injection. Adobe Experience Manager stores and retrieves content in a Java Content Repository (Apache Jackrabbit Oak) and exposes query functionality - notably through the QueryBuilder API and JCR XPath/SQL2 query execution - that ultimately translates application input into XPath expressions evaluated against the content tree. When attacker-controlled input is concatenated into such a query without parameterization or escaping, XPath metacharacters (quotes, brackets, boolean operators) can be injected to alter the query's logic. Because the application does not reflect query results or errors directly, the injection is 'blind': an attacker must infer structure and data through boolean-based or error/behavioural side channels, extracting node properties, user data, or ACL-relevant information one condition at a time. That capability is what produces the 'security feature bypass' - manipulating query predicates can cause the repository layer to return nodes that access-control logic would otherwise withhold, yielding the high confidentiality impact (C:H) observed in the vector, along with a limited ability to influence state (I:L). The assessed vector AV:N/AC:L/PR:L/UI:N/S:U confirms the attack path is over the network with no special complexity, no user interaction, and no scope change, but is gated behind a valid low-privileged session. CWE-91 is the correct root-cause classification: improper neutralization of XML/XPath special elements during query construction.

Know when Adobe gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 7.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
vuln.today AI 7.1 HIGH

Network-reachable AEM feature, low complexity, but requires a low-privileged authenticated account (PR:L); blind XPath injection yields high confidentiality, limited write (I:L), no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

DescriptionCVE.org

Adobe Experience Manager is affected by an XML Injection (aka Blind XPath Injection) vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and limited write access. Exploitation of this issue does not require user interaction.

Executive ViewAI

Why It Matters

Adobe Experience Manager 6.5 (versions 6.5.0 through 6.5.25) is affected by a high-severity vulnerability that allows authenticated low-privileged users to bypass security controls and access confidential content. This could lead to unauthorized exposure of sensitive business information, with limited ability to alter data. Leadership should prioritize mitigation because the flaw has high confidentiality impact and no vendor patch is currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to AEM instances to trusted networks, enforce least privilege and monitor low-privileged accounts, review logs for anomalous XPath queries or content access, and consult Adobe security bulletin apsb26-152 for any vendor-recommended workarounds.

Threat Intelligence Overview

EPSS Score
0.4%
Top 63% exploitable
Prevalence
High
widely deployed enterprise CMS/DAM platform in large organizations
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in Adobe

View all
CVE-2015-5119 CRITICAL POC
9.8 Jul 08

Remote code execution in Adobe Flash Player 11.x through 18.x allows unauthenticated network attackers to execute arbitr

CVE-2016-4117 CRITICAL POC
9.8 May 11

Remote code execution in Adobe Flash Player 21.0.0.226 and earlier allows unauthenticated network attackers to execute a

CVE-2015-3113 CRITICAL POC
9.8 Jun 23

Adobe Flash Player contains a heap-based buffer overflow that allows remote code execution, exploited as a zero-day in J

CVE-2011-2462 CRITICAL POC
9.8 Dec 07

Adobe Reader and Acrobat contain an unspecified U3D component vulnerability causing memory corruption that allows remote

CVE-2011-0611 HIGH POC
8.8 Apr 13

Adobe Flash Player contains a type confusion vulnerability in object handling that allows remote attackers to execute ar

CVE-2009-0927 HIGH POC
8.8 Mar 19

Adobe Reader and Acrobat 9.x, 8.x, and 7.x contain a stack-based buffer overflow in the getIcon method of the Collab obj

CVE-2014-0497 CRITICAL POC
9.8 Feb 05

Integer underflow in Adobe Flash Player before 11.7.700.261 and 11.8.x through 12.0.x before 12.0.0.44 on Windows and Ma

CVE-2009-4324 HIGH POC
7.8 Dec 15

Adobe Reader and Acrobat contain a use-after-free vulnerability in the Doc.media.newPlayer JavaScript method that was ac

CVE-2015-0313 CRITICAL POC
9.8 Feb 02

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.269 and 14.x through 16.x before 16.0.0.305 on Windows

CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2015-0311 CRITICAL POC
9.8 Jan 23

Unspecified vulnerability in Adobe Flash Player through 13.0.0.262 and 14.x, 15.x, and 16.x through 16.0.0.287 on Window

CVE-2013-0632 CRITICAL POC
9.8 Jan 17

administrator.cfc in Adobe ColdFusion 9.0, 9.0.1, 9.0.2, and 10 allows remote attackers to bypass authentication and pos

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy