CVE-2026-47998
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 is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized read access. Exploit depends on conditions beyond the attacker's control. 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 confidenceAdobe Commerce contains an incorrect authorization vulnerability allowing attackers to bypass security measures and achieve unauthorized read access to sensitive data. The exploit requires specific conditions beyond the attacker's control but does not require 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.5= 2.4.6= 2.4.7= 2.4.8= 2.4.9= 1.3.3= 1.3.4= 1.4.2= 1.5.2= 1.5.3= 2.4.6= 2.4.7= 2.4.8= 2.4.9>= 1.6.0, < 1.21.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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.
-
Identify Adobe Commerce versionRun 'php bin/magento --version' from the Magento root directory, or inspect the composer.json file for the 'magento/product-community-edition' or 'magento/product-enterprise-edition' version entryAffected if The installed version is 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, or 2.4.9
-
Identify Adobe Magento versionRun 'php bin/magento --version' or check composer.json for 'magento/magento2-base' version if using Magento Open SourceAffected if The installed version is 2.4.6, 2.4.7, 2.4.8, or 2.4.9
-
Identify Adobe Commerce B2B versionCheck composer.json for 'magento/module-b2b' version entry, or run 'php bin/magento module:status' to list enabled modules and look for B2B-related modulesAffected if The B2B module version is 1.3.3, 1.3.4, 1.4.2, 1.5.2, or 1.5.3 and the B2B module is enabled
-
Identify Adobe I/O Events versionCheck composer.json for 'magento/io-events' or 'adobe/io-events' package version, or run 'composer show magento/io-events' if installedAffected if The installed version is >= 1.6.0 and < 1.21.0
-
Audit read-access authorization configurationReview admin panel ACL settings under Stores > Settings > Configuration > Security, and inspect API endpoint configurations in webapi.xml files for read operations on sensitive data endpointsAffected if Authorization controls on read operations allow access beyond intended ACL boundaries (requires manual code review or penetration testing to confirm)
A user is affected if their Adobe Commerce, Magento, or B2B installation matches one of the listed vulnerable versions, or if Adobe I/O Events version falls between 1.6.0 and 1.20.x, AND the application exposes read-access endpoints that could be accessed without proper authorization.
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 data1.21.0
Apply the vendor-provided patch or update to Adobe Commerce when available. Review and harden authorization controls around read operations and implement additional access validation layers.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47998 — 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-47998 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