CVE-2026-34653
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 Commerce versions 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could result in arbitrary file system read and write. An authenticated attacker with administrative privileges could exploit this vulnerability to read or write files outside the restricted directory. 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 · high confidencePath traversal vulnerability in Adobe Commerce allowing authenticated administrators to read/write files outside restricted directories due to improper pathname validation. The flaw enables arbitrary file system access without 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< 2.4.4= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9< 1.3.3= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3< 2.4.6= 2.4.6= 2.4.7= 2.4.8= 2.4.9CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Adobe Commerce or Magento installationRun 'composer show magento/product-enterprise-edition 2>/dev/null | grep version' for Commerce or 'composer show magento/product-community-edition 2>/dev/null | grep version' for Magento. Alternatively, check the version file at app/etc/app.php or the admin panel footer.Affected if The installed version matches any of these: less than 2.4.4, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
-
Check for Adobe Commerce B2B extensionRun 'composer show magento/module-b2b 2>/dev/null | grep version' or examine composer.json for 'magento/module-b2b'. If using B2B, note the installed version.Affected if B2B extension is installed with a version matching: less than 1.3.3, 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3
-
Verify administrator access existsConfirm that valid administrator credentials or session tokens exist for the Magento admin panel. Check for admin user records in the admin_user database table or review authentication configuration in env.php.Affected if An authenticated administrator account is present and accessible, as the vulnerability requires admin-level authentication to exploit
-
Identify path traversal attack surfaceReview custom modules or third-party extensions that handle file operations such as import, export, or attachment upload. Examine any custom code using file_get_contents, file_put_contents, or similar file handling functions that accept user-supplied paths.Affected if Custom or third-party modules with file operations exist that do not properly validate file paths before use
Your environment is affected if it runs Adobe Commerce or Magento within the listed version ranges AND has an accessible authenticated administrator account that could trigger the path traversal vulnerability.
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 · scoped1.3.32.4.42.4.6
Apply vendor security patches or upgrade to the latest stable Adobe Commerce version to implement proper path validation and restrict filesystem access to intended directories.
Magento/Adobe Commerce 2.4.9 or later (including 2.4.10)
- 1. Back up your current Adobe Commerce/Magento installation including database and files
- 2. Review the Adobe Commerce upgrade guide at https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/overview.html
- 3. Update Composer to reference the new version: composer require magento/product-community-edition=2.4.9 --no-update
- 4. Run composer update to fetch the new version packages
- 5. After composer update completes, clear the cache: rm -rf var/cache var/page_cache generated/code
- 6. Run the setup upgrade command: bin/magento setup:upgrade
- 7. Compile dependency injection: bin/magento setup:di:compile
- 8. Deploy static content: bin/magento setup:static-content:deploy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34653 — 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-34653 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