Security Resilience

CVE-2026-48416

Access Control in Adobe Commerce B2B 1.3.3 … 1.4.2

Published
11 August 2026
Modified
25 September 2026
Patch / advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0083 58th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-48416 is a high-severity Incorrect Authorization (CWE-863) vulnerability in Adobe Commerce B2B. Its CVSS base score is 7.5 (High).

Operationally, ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-25 (Reference Monitor) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Adobe 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. Exploitation of this issue does not require user…

more

interaction.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-71362Same product: Adobe Commerce B2B
CVE-2025-24437Same product: Adobe Commerce B2B
CVE-2026-21286Same product: Adobe Commerce B2B
CVE-2024-45125Same product: Adobe Commerce B2B
CVE-2026-21289Same product: Adobe Commerce B2B
CVE-2025-24421Same product: Adobe Commerce B2B
CVE-2026-48415Same product: Adobe Commerce B2B
CVE-2025-24436Same product: Adobe Commerce B2B
CVE-2025-54265Same product: Adobe Commerce B2B
CVE-2025-27188Same product: Adobe Commerce B2B

Affected Assets

adobe
commerce b2b
1.3.3, 1.3.4, 1.3.5, 1.4.2
adobe
commerce
2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8
adobe
magento
2.4.6, 2.4.7, 2.4.8, 2.4.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

AC-3 directly requires correct enforcement of authorization decisions on every access request, structurally preventing incorrect checks.

AC-24 ensures access-control decisions are made and applied consistently, reducing the chance of an incorrect authorization result.

A reference monitor that is always invoked and tamper-proof forces every authorization decision through a verified, correct path.

Least-privilege assignments shrink the set of authorizations that must be checked correctly, limiting exposure to flawed checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

A.8.3's access restriction mechanisms, including granular per-user and per-identity controls, directly enforce correct authorization checks, preventing exploitation of incorrect authorization flaws.

blocks

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-863, a class-level weakness, and none of its children carries one either.

References