dbcve.org
Experience ManagerApplication · Adobe

CVE-2026-48259

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to after 2020.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

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 · unedited
Adobe Experience Manager is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in arbitrary code execution in the context of the current user. A low-privileged attacker could leverage this vulnerability to issue unauthorized server-side requests, 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.

In the news

Third-party coverage
Trending covered by 3 outlets this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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 confidence

Adobe Experience Manager contains a Server-Side Request Forgery (SSRF) vulnerability allowing low-privileged attackers to issue unauthorized server-side requests, potentially achieving arbitrary code execution in the current user's context. The CVSS scope change indicates the vulnerability impacts components beyond the vulnerable service itself, with the critical 9.6 score reflecting the potential for complete system compromise without user interaction.

MitigationApply available Adobe security patches for AEM, restrict outbound network access from the AEM server, implement strict URL allowlist validation on request parameters, and review network segmentation to limit potential SSRF exploitation paths.

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
Experience ManagerApplication
Affected:<= 6.5.25.0<= 2020.5.0= 6.5

CVSS 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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify AEM installation and version
    Locate the AEM instance and retrieve its version number. This can typically be found in the AEM Web Console (https://<host>:<port>/system/console/status-productinfo) or by checking the crx-quickstart folder for version files.
    Affected if The installed version matches <= 6.5.25.0, <= 2020.5.0, or the 6.5.x release line.
  2. Check AEM Oak login token configuration
    Inspect the Apache Jackrabbit Oak token configuration in the OSGi console at /system/console/configMgr/org.apache.jackrabbit.oak.security.authentication.token.TokenConfiguration. Look for any custom token store implementations or non-default settings.
    Affected if A non-standard or custom token configuration is present that allows token manipulation by low-privileged users.
  3. Review Sling authentication settings
    Examine the Sling authentication configuration at /system/console/configMgr/org.apache.sling.security.impl.RefererFilter. Check for overly permissive referrer policies or missing CSRF tokens.
    Affected if Referrer validation is disabled or weak, allowing SSRF vectors to bypass same-origin checks.
  4. Inspect outbound request configurations
    Check the Day CQ Link Checker and any custom HTTP client configurations in /system/console/configMgr for settings that allow server-side outgoing connections to arbitrary URLs.
    Affected if Outbound request filters are not configured or allow connections to internal network resources.
  5. Audit low-privileged user permissions
    Review user/group permissions in AEM CRXDE Lite (https://<host>:<port>/crx/de) focusing on users with read access to /libs, /apps, or content nodes that expose HTTP request capabilities.
    Affected if Low-privileged users have permissions that enable them to trigger server-side requests through exposed AEM APIs or workflows.

The environment is affected if AEM version is 6.5.25.0 or earlier, or 2020.5.0 or earlier, AND low-privileged users have access to features that can trigger outbound server requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 2020.5.0
Interim mitigation

Apply available Adobe security patches for AEM, restrict outbound network access from the AEM server, implement strict URL allowlist validation on request parameters, and review network segmentation to limit potential SSRF exploitation paths.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48259 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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