dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26029

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 versions 6.5.20 and earlier are affected by an Improper Access Control vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain disclose information. Exploitation of this issue does not require user interaction.

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 versions 6.5.20 and earlier contain an Improper Access Control vulnerability allowing attackers to bypass security measures and access sensitive information without any user interaction. The vulnerability has a critical CVSS score of 9.8, indicating severe potential impact on confidentiality through unauthorized access.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to patch the improper access control vulnerability. Prioritize this upgrade given the critical severity and exploitation requiring no user interaction.

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.21< 2024.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Adobe Experience Manager is deployed
    Identify AEM instances in your environment by checking for AEM-related processes, services, or web applications running on common AEM ports (typically 4502, 4503, or port 8080/8443). Look for AEM-specific war files or installations in your application servers.
    Affected if AEM is found running in the environment
  2. Determine the installed AEM version
    Access the AEM Welcome page or the system console (e.g., /crx/packmgr/service.jsp or /system/console/config). Alternatively, check the version.properties file in the crx-quickstart folder, or query the version endpoint if available.
    Affected if The detected version is below 6.5.21 or below the 2024.5 release
  3. Compare version against affected ranges
    Review the version number identified in step 2 against the affected ranges: any version earlier than 6.5.21, or any version earlier than the 2024.5 release, is within the affected range.
    Affected if The version is 6.5.20 or earlier, or falls below the 2024.5 release
  4. Assess network exposure of the AEM instance
    Determine if the AEM instance is accessible from the network, since this vulnerability can be exploited without any user interaction. Check firewall rules, network ACLs, and whether the instance is exposed to internal or external networks.
    Affected if The AEM instance is network-accessible without strong access controls
  5. Review access control configurations
    Inspect the AEM repository permissions, user/group ACLs, and sling-based authorization settings in the CRX Explorer or through the User Management console to verify if default or overly permissive access controls are in place.
    Affected if Weak or default access control configurations are detected

If the installed Adobe Experience Manager version is 6.5.20 or earlier, or is a release predating 2024.5, and the instance is network-accessible, the environment is affected by CVE-2024-26029.

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.

dbcve · scoped
Upgrade available Upgrade to 6.5.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Upgrade Adobe Experience Manager to version 6.5.21 or later to patch the improper access control vulnerability. Prioritize this upgrade given the critical severity and exploitation requiring no user interaction.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 or 2024.5 (depending on your current release branch)

  1. Back up the current Adobe Experience Manager instance and repository
  2. Review the Adobe Experience Manager 6.5.21 or 2024.5 release notes and upgrade documentation on helpx.adobe.com
  3. Test the upgrade in a non-production environment before applying to production
  4. Apply the upgrade to upgrade to version 6.5.21 (for 6.5.x branch) or 2024.5 (for the newer release branch)
  5. Verify the upgrade was successful and that the AEM instance is functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26029 — 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-2024-26029 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