CVE-2026-48310
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 is affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could lead to arbitrary file system read. An attacker could exploit this vulnerability to access sensitive files and directories outside the intended access scope. Exploitation of this issue does not require user interaction. 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 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files from the filesystem by manipulating path references in requests. The 'scope changed' designation indicates the vulnerability can escape AEM's sandbox and access files outside the intended restricted directory.
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<= 2020.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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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.
-
Confirm Adobe Experience Manager is installedLocate AEM installation directories (commonly under /opt/aem, /usr/local/aem, or C:\Program Files\Adobe) and identify the crx-quickstart folder which contains the AEM instance.Affected if AEM software is present on the system
-
Identify the installed AEM versionCheck the version.properties file located in the crx-quickstart folder, or access the AEM Welcome page and navigate to Help > About Adobe Experience Manager to view the version number.Affected if The displayed version matches <= 6.5.25.0, <= 2020.5.0, or = 6.5
-
Verify the version is within affected rangesCompare your installed version number against the affected ranges. Note that version 6.5 (without subversion) and any 6.5.x release up to and including 6.5.25.0 are affected, as are any 2020.x releases up to 2020.5.0.Affected if Your version falls within the affected ranges indicating vulnerability to path traversal exploitation
-
Confirm the web interface is accessibleAccess the AEM web interface by reaching the publish or author instance over HTTP/HTTPS. The vulnerability can be exploited without authentication, so check if the port (typically 4502 for author, 4503 for publish) is exposed.Affected if The AEM web interface is reachable over the network, enabling potential path traversal attacks
-
Inspect request logging for path traversal attemptsReview AEM access logs (access.log) and error logs (error.log) in the crx-quickstart/logs directory for patterns containing ../ or encoded path sequences targeting system directories outside the web root.Affected if Suspicious path traversal patterns appear in logs indicating potential exploitation attempts
You are affected if Adobe Experience Manager is installed and the installed version falls within <= 6.5.25.0, <= 2020.5.0, or equals 6.5, making the path traversal vulnerability exploitable on your instance.
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.
From vendor dataApply vendor patches when available; implement strict input validation on all file path parameters and restrict filesystem access to essential directories only.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48310 — 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-48310 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