CVE-2026-47986
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. An attacker could exploit this issue by manipulating the DOM environment to execute malicious JavaScript within the context of the victim's browser. Exploitation of this issue requires user interaction in that a victim must visit a crafted webpage. Scope is changed.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAdobe Experience Manager versions 6.5.24, LTS SP1, 2026.04 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. Attackers can manipulate the DOM environment through a crafted webpage, causing the victim's browser to execute malicious JavaScript. This is a client-side vulnerability where user interaction is required (victim must visit the malicious page), and the scope change indicates the attack can impact resources beyond the vulnerable component.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.5.25.0< 2026.5.0= 6.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed AEM versionNavigate to AEM Welcome page > Help > About Adobe Experience Manager, or locate the version.properties file in the crx-quickstart folder. Alternatively, access the System Information console at /system/console/systeminfo.Affected if The version displayed is 6.5.24, 6.5 LTS SP1, 2026.04, or any version below 6.5.25.0 or below 2026.5.0
-
Confirm AEM edition typeCheck if the installation is the standard AEM 6.5 (not a later service pack release). Review the version string for '6.5' as the base release.Affected if The base version is exactly 6.5 regardless of installed service packs, or falls within the < 6.5.25.0 range
-
Identify DOM-handling componentsReview custom components, HTL (HTML Template Language) templates, or client-side JavaScript that directly manipulate the DOM using innerHTML, document.write, or similar methods without server-side encoding.Affected if Custom or third-party components exist that perform direct DOM manipulation on user-supplied content without sanitization
-
Check for user input endpointsExamine form components, search functionality, or any URL parameters that reflect input back into the page HTML. Look for patterns in /apps or /libs where request parameters are rendered without proper encoding.Affected if Any AEM components accept and render user input directly into the DOM without contextual encoding
Your AEM instance is affected if it runs version 6.5.24 or earlier (including 6.5 LTS SP1), any version below 6.5.25.0 or below 2026.5.0, AND contains components that render user input into the DOM without sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.5.25.02026.5.0
Apply the vendor-provided patch for Adobe Experience Manager to the latest supported version. Additionally, implement Content Security Policy (CSP) headers to mitigate XSS execution, and validate that all client-side code properly sanitizes DOM inputs before rendering.
6.5.25.0 (LTS) or 2026.5.0 (2026 release train)
- 1. Review Adobe Experience Manager release notes for version 6.5.25.0 (LTS) or 2026.5.0 (2026 release train) to understand changes and prerequisites.
- 2. Perform a full backup of the AEM repository (Oak repository), database, and configuration files.
- 3. Set up a staging/development environment that mirrors production to test the upgrade.
- 4. Stop the AEM instance and all related services before beginning the upgrade process.
- 5. Download the appropriate service pack or release package from Adobe Software Distribution (experience.adobe.com) - either 6.5.25.0 or 2026.5.0 depending on your current release train.
- 6. Install the service pack using the AEM Package Manager or command line (e.g., via curl POST to package manager), following Adobe's documented installation procedure.
- 7. After installation, clear the AEM caches and OSGi component cache by removing files under /system/console/branding and crx-quickstart/repository/cache.
- 8. Restart the AEM instance and verify all bundles are in active state via the OSGi Console (/system/console/bundles).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data