CVE-2026-48359 experience manager vulnerability
Adobe Experience Manager is affected by an Improper Restriction of XML External Entity Reference ('XXE') vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could exploit this vulnerability to read sensitive files, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue does not require user interaction. Scope is changed.
Browse Remote Code Execution security risksQuick answer
adobe experience manager should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- AEM Cloud Service 2026.5.0 and earlier
- AEM 6.5 LTS SP2 and earlier
- AEM 6.5 SP25 and earlier
Fixed versions
- AEM Cloud Service 2026.6.0
- AEM 6.5 LTS SP2 + Hotfix NPR-43972
- AEM 6.5 SP25 + Hotfix NPR-43971
How to fix it
Adobe Experience Manager is affected by CVE-2026-48359, an XML external entity injection flaw that can lead to file read and code execution. A low-privileged attacker can make the server process unsafe XML, read sensitive files, and gain broader control without user interaction. Confirm AEM Cloud Service has received 2026.6.0; update AEM 6.5 LTS to SP2 and then apply Hotfix NPR-43972; or update AEM 6.5 to SP25 and then apply Hotfix NPR-43971, as applicable. Treat exposed production systems as an urgent patch and incident-review priority.
- Inventory every Adobe Experience Manager deployment, version, exposed endpoint, environment, and owner.
- Inventory AEM Cloud Service, AEM 6.5 LTS, and AEM 6.5 deployments, then match each one to the affected products in APSB26-74.
- Confirm AEM Cloud Service has received 2026.6.0; update AEM 6.5 LTS to SP2 and then apply Hotfix NPR-43972; or update AEM 6.5 to SP25 and then apply Hotfix NPR-43971, as applicable.
- Adobe lists no workaround in APSB26-74. Until the update is complete, block untrusted XML input at exposed AEM endpoints, disable external entity resolution where supported, and restrict low-privileged author access.
- Review XML requests, external entity declarations, file-read errors, new processes, content changes, and outbound connections.
- If exploitation is suspected, isolate the instance, preserve evidence, rebuild from a known-good source, and rotate credentials and secrets stored on the server.
- Restart or redeploy affected AEM services as required by Adobe, clear AEM and CDN caches, and keep temporary controls until validation is complete.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm AEM Cloud Service is on 2026.6.0 or later, or verify both AEM 6.5 LTS SP2 plus Hotfix NPR-43972, or both AEM 6.5 SP25 plus Hotfix NPR-43971, on every applicable deployment.
- Confirm a safe XXE regression payload cannot resolve an external entity, read a local file, or make an outbound request.
- Confirm AEM Author and Publish exposure, Dispatcher and CDN/WAF rules, outbound access, and service-account permissions follow the deployment's approved security baseline.
- Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
- Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-48359.
Related categories
Related security risks
More published guidance from the same primary category.
Trusted references
FAQ
What is affected by CVE-2026-48359?
adobe experience manager versions listed as affected should be reviewed: AEM Cloud Service 2026.5.0 and earlier, AEM 6.5 LTS SP2 and earlier, AEM 6.5 SP25 and earlier.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.