CVE-2026-34646 — Adobe Commerce | Incorrect Authorization (CWE-863)
Adobe 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 Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could leverage this vulnerability to bypass security measures and gain unauthorized write access. Exploitation of this issue does not require user interaction.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.7% (30-day exploitation probability)+8
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Adobe Commerce, Adobe Commerce B2b, Adobe Magento…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Adobe | Commerce |
< 2.4.4version 2.4.4version 2.4.4-p1version 2.4.4-p10version 2.4.4-p11version 2.4.4-p12version 2.4.4-p13version 2.4.4-p14 and 64 moreversion 2.4.4-p15version 2.4.4-p16version 2.4.4-p17version 2.4.4-p2version 2.4.4-p3version 2.4.4-p4version 2.4.4-p5version 2.4.4-p6version 2.4.4-p7version 2.4.4-p8version 2.4.4-p9version 2.4.5version 2.4.5-p1version 2.4.5-p10version 2.4.5-p11version 2.4.5-p12version 2.4.5-p13version 2.4.5-p14version 2.4.5-p15version 2.4.5-p16version 2.4.5-p2version 2.4.5-p3version 2.4.5-p4version 2.4.5-p5version 2.4.5-p6version 2.4.5-p7version 2.4.5-p8version 2.4.5-p9version 2.4.6version 2.4.6-p1version 2.4.6-p10version 2.4.6-p11version 2.4.6-p12version 2.4.6-p13version 2.4.6-p14version 2.4.6-p2version 2.4.6-p3version 2.4.6-p4version 2.4.6-p5version 2.4.6-p6version 2.4.6-p7version 2.4.6-p8version 2.4.6-p9version 2.4.7version 2.4.7-b1version 2.4.7-b2version 2.4.7-beta3version 2.4.7-p1version 2.4.7-p2version 2.4.7-p3version 2.4.7-p4version 2.4.7-p5version 2.4.7-p6version 2.4.7-p7version 2.4.7-p8version 2.4.7-p9version 2.4.8version 2.4.8-beta1version 2.4.8-beta2version 2.4.8-p1version 2.4.8-p2version 2.4.8-p3version 2.4.8-p4version 2.4.9-beta1 |
Vulnerable | NIST National Vulnerability Database |
| Adobe | Commerce | ≤ 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14, 2.4.5-p16, 2.4.4-p17 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Adobe | Commerce B2b |
< 1.3.3version 1.3.3version 1.3.3-p1version 1.3.3-p10version 1.3.3-p11version 1.3.3-p12version 1.3.3-p13version 1.3.3-p14 and 44 moreversion 1.3.3-p15version 1.3.3-p16version 1.3.3-p17version 1.3.3-p2version 1.3.3-p3version 1.3.3-p4version 1.3.3-p5version 1.3.3-p6version 1.3.3-p7version 1.3.3-p8version 1.3.3-p9version 1.3.4version 1.3.4-p1version 1.3.4-p10version 1.3.4-p11version 1.3.4-p12version 1.3.4-p13version 1.3.4-p14version 1.3.4-p15version 1.3.4-p16version 1.3.4-p2version 1.3.4-p3version 1.3.4-p4version 1.3.4-p5version 1.3.4-p6version 1.3.4-p7version 1.3.4-p8version 1.3.4-p9version 1.4.2version 1.4.2-p1version 1.4.2-p2version 1.4.2-p3version 1.4.2-p4version 1.4.2-p5version 1.4.2-p6version 1.4.2-p7version 1.4.2-p8version 1.4.2-p9version 1.5.2-p1version 1.5.2-p2version 1.5.2-p3version 1.5.2-p4version 1.5.3-beta1version 1.5.2 |
Vulnerable | NIST National Vulnerability Database |
| Adobe | Commerce B2b | ≤ 1.5.3-beta1, 1.5.2-p4, 1.4.2-p9, 1.3.4-p16, 1.3.3-p17 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Adobe | Magento |
version 2.4.7-beta3version 2.4.6-p9version 2.4.7-p1version 2.4.7-p2version 2.4.7-p3version 2.4.7-p4version 2.4.7-p5version 2.4.7-p6 and 29 moreversion 2.4.7-p7version 2.4.7-p8version 2.4.7-p9version 2.4.8version 2.4.8-beta1version 2.4.8-beta2version 2.4.8-p1version 2.4.8-p2version 2.4.8-p3version 2.4.8-p4version 2.4.9-beta1version 2.4.7-b1< 2.4.6version 2.4.6version 2.4.6-p1version 2.4.6-p10version 2.4.6-p11version 2.4.6-p12version 2.4.6-p13version 2.4.6-p14version 2.4.6-p2version 2.4.6-p3version 2.4.6-p4version 2.4.6-p5version 2.4.6-p6version 2.4.6-p7version 2.4.6-p8version 2.4.7version 2.4.7-b2 |
Vulnerable | NIST National Vulnerability Database |
| Adobe | Magento Open Source | ≤ 2.4.9-beta1, 2.4.8-p4, 2.4.7-p9, 2.4.6-p14 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | psirt@adobe.com via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | adobe via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (score shown at the top: psirt@adobe.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.73%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · adobe/adobe commerce, adobe/adobe commerce b2b, adobe/magento open source
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-95630 Adobe Commerce | Improper Input Validation (CWE-20) 2d
- High CVE-2026-95631 Adobe Commerce | Improper Input Validation (CWE-20) 2d
- Critical CVE-2026-92464 Adobe Commerce | Improper Input Validation (CWE-20) 2d
- High CVE-2026-92908 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
- High CVE-2026-92911 Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79) 2d
- High CVE-2026-92910 Adobe Commerce | Incorrect Authorization (CWE-863) 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-34646 is "Adobe Commerce | Incorrect Authorization (CWE-863)", rated High. It affects Commerce (Adobe); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.73% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.