dbcve.org
CommerceApplication · Adobe

CVE-2026-47996

MEDIUM · 6.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.21.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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 Commerce is affected by an Incorrect Authorization vulnerability that could lead to arbitrary file system read. A high-privileged 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 confidence

Adobe Commerce contains an incorrect authorization vulnerability that allows high-privileged attackers to bypass security measures and gain unauthorized read access to sensitive data. The scope is changed, indicating the vulnerability impacts components beyond the originally affected component. This is a security feature bypass that does not require user interaction to exploit.

MitigationApply the official Adobe security patch for CVE-2026-47996 and ensure proper authorization checks are implemented and enforced across all data access points in the Commerce implementation.

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
CommerceApplication
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9
Commerce B2bApplication
Affected:= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3
MagentoCMS
Affected:= 2.4.6= 2.4.7= 2.4.8= 2.4.9
I\/o EventsApplication
Affected:>= 1.6.0, < 1.21.0

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

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

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

  1. Identify Adobe Commerce version
    Run command: php bin/magento --version or check composer.json for "magento/product-community-edition" version
    Affected if Installed version equals 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
  2. Identify Adobe Commerce B2b version
    Run command: composer show magento/module-b2b 2>/dev/null or check composer.json for "magento/module-b2b" version
    Affected if B2b module is installed and version equals 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3
  3. Identify Adobe Magento version
    Run command: php bin/magento --version or check composer.json for "magento/product-magento-base" version if using Magento rather than Commerce
    Affected if Installed version equals 2.4.6, 2.4.7, 2.4.8, or 2.4.9 (Magento only)
  4. Identify Adobe I/O Events version
    Run command: composer show magento/module-io-events 2>/dev/null or check composer.json for "magento/module-io-events" version
    Affected if I/O Events module is installed and version is 1.6.0 through 1.20.x (less than 1.21.0)
  5. Verify if B2b module is enabled
    Run: php bin/magento module:status | grep -i b2b or check app/etc/config.php for B2b module entry
    Affected if B2b module is enabled on affected Commerce versions (2.4.4-2.4.9)

You are affected if any Adobe Commerce, Commerce B2b, Magento, or I/O Events installation matches the specific version numbers listed, particularly with B2b module enabled.

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 1.21.0 or later
Fixed in 1.21.0
Interim mitigation

Apply the official Adobe security patch for CVE-2026-47996 and ensure proper authorization checks are implemented and enforced across all data access points in the Commerce implementation.

Recommended fix Moderate confidence

Upgrade to the latest available Adobe Commerce 2.4.7-patch or 2.4.8-patch (e.g., 2.4.7-p5+/2.4.8-p1+) or the latest 2.4.9 release. For I/O Events, upgrade to >=1.21.0

  1. 1. Identify your current Adobe Commerce/Magento version by running: bin/magento --version
  2. 2. Backup your database and codebase before proceeding with any upgrade
  3. 3. For Adobe Commerce 2.4.7: Upgrade to the latest 2.4.7-patch version (e.g., 2.4.7-p5 or later) using Composer: composer require magento/product-community-edition=2.4.7-p5 --no-update followed by composer update
  4. 4. For Adobe Commerce 2.4.8: Upgrade to the latest 2.4.8-patch version (e.g., 2.4.8-p1 or later) using Composer: composer require magento/product-community-edition=2.4.8-p1 --no-update followed by composer update
  5. 5. For Adobe Commerce 2.4.9: Upgrade to the latest available patch version
  6. 6. For I/O Events: Upgrade to version 1.21.0 or later
  7. 7. Run setup upgrade: bin/magento setup:upgrade
  8. 8. Clear caches: bin/magento cache:flush
Caveat Standard Adobe Commerce upgrade risks apply - test thoroughly in staging first, as custom extensions may require compatibility updates with newer patch releases

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

Fix this in Commerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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