Commerce B2b vulnerabilitiesAnd the versions its exploited flaws hit.
Commerce B2b is made by Adobe. We track 66 published vulnerabilities in it, across 14 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 27 October 2026. If you run Commerce B2b, check your version against the exploited flaws below and patch those first.
The most recent Commerce B2b flaw added to the known-exploited list is CVE-2026-48356, on 27 October 2026. We keep watching the known-exploited list.
Which versions of Commerce B2b do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2026-48356Exploited list, 27 Oct 2026
Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type Vulnerability
1.3.31.3.3-p11.3.3-p21.3.3-p31.3.3-p41.3.3-p51.3.3-p61.3.3-p7 - CVE-2025-54236Exploited list, 24 Oct 2025
Adobe Commerce and Magento Improper Input Validation Vulnerability
1.3.31.3.3-p11.3.3-p21.3.3-p31.3.3-p41.3.3-p51.3.3-p61.3.3-p7
Which Commerce B2b vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.3Adobe Commerce and Magento Unrestricted Upload of File with Dangerous Type Vulnerability
Adobe Commerce and Magento contain an unrestricted upload of file with dangerous type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated...
- 9.1Adobe Commerce and Magento Improper Input Validation Vulnerability
Adobe Commerce and Magento Open Source contain an improper input validation vulnerability that could allow an attacker to take over customer accounts through the Commerce REST API.
Which Commerce B2b flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 95%
Adobe Commerce versions 2.4.9-alpha2, 2.4.8-p2, 2.4.7-p7, 2.4.6-p12, 2.4.5-p14, 2.4.4-p15 and earlier are affected by an Improper Input Validation vulnerability.
- 31%
Adobe Commerce is affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or...
- 21%CVE-2026-34648High
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 Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service.
- 17%CVE-2025-24434Critical
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Incorrect Authorization vulnerability that could result in Privilege escalation.
- 15%CVE-2026-34650High
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 Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service.
- 14%CVE-2026-34649High
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 Uncontrolled Resource Consumption vulnerability that could lead to application denial-of-service.
- 1.4%CVE-2025-24406High
Adobe Commerce versions 2.4.8-beta1, 2.4.7-p3, 2.4.6-p8, 2.4.5-p10, 2.4.4-p11 and earlier are affected by an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability that could...
- 1.3%CVE-2024-45115Critical
Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier are affected by an Improper Authentication vulnerability that could result in privilege escalation.
- 1.2%CVE-2026-48358Critical
Adobe Commerce is affected by an Improper Encoding or Escaping of Output vulnerability that could result in arbitrary code execution in the context of the current user.
- 1.0%CVE-2025-27189Medium
Adobe Commerce versions 2.4.7-p4, 2.4.6-p9, 2.4.5-p11, 2.4.4-p12, 2.4.8-beta2 and earlier are affected by a Cross-Site Request Forgery (CSRF) vulnerability that could be exploited to cause a denial-of-service condition.
Running Commerce B2b? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Adobe Commerce and Magento contain an unrestricted upload of file with dangerous type vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or control over the victim's account or session.
- Matched to
- Commerce B2b on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 66 published vulnerabilities listed under the name Commerce B2b, across 14 versions. The most recent Commerce B2b flaw added to the known-exploited list is CVE-2026-48356, on 27 October 2026.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2026-48356 and CVE-2025-54236.
Each flaw names its own versions, usually as ranges. The newest, CVE-2026-48356, affects 1.3.3, 1.3.3-p1, 1.3.3-p2, 1.3.3-p3 and more. The versions for every exploited flaw are listed on this page.
Create a EdgeProtect account and track Commerce B2b. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.