CVE Tools
Track your stack

CVE-2026-48415

Adobe Commerce | Incorrect Authorization (CWE-863)

No known exploitation. EPSS puts it in the 38th percentile. Fixed versions are out.

CVSS 3.17.6HighEPSS percentile38th0.5% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix3 products8 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Adobe CommerceAffected: ≤ 2.4.9-2026-julUpgrade to: after 2.4.9-2026-julAffected: ≤ 2.4.8-2026-augUpgrade to: after 2.4.8-2026-augAffected: ≤ 2.4.7-2026-augUpgrade to: after 2.4.7-2026-augAffected: ≤ 2.4.6-2026-augUpgrade to: after 2.4.6-2026-augFixed builds2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug + 2 more branchesStated by: CVE record
  • Adobe Commerce B2BAffected: ≤ 1.5.3-2026-julUpgrade to: after 1.5.3-2026-julAffected: ≤ 1.5.2-2026-julUpgrade to: after 1.5.2-2026-julAffected: ≤ 1.4.2-2026-julUpgrade to: after 1.4.2-2026-julAffected: ≤ 1.3.4-2026-julUpgrade to: after 1.3.4-2026-julFixed builds1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug + 1 more branchStated by: CVE record
  • Adobe Magento Open SourceAffected: ≤ 2.4.9-2026-julUpgrade to: after 2.4.9-2026-julAffected: ≤ 2.4.8-2026-julUpgrade to: after 2.4.8-2026-julAffected: ≤ 2.4.7-2026-julUpgrade to: after 2.4.7-2026-julAffected: ≤ 2.4.6-2026-julUpgrade to: after 2.4.6-2026-julFixed builds2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-augStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. A low-privileged attacker could leverage this vulnerability to bypass security measures and gain unauthorized read and write access, causing a limited disruption to availability. Exploitation of this issue does not require user interaction.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS38th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.5% chance of exploitation activity in the next 30 days, which ranks it in the 38th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

10 events over 45 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Record updated
  3. OpenVAS check added
  4. Record updated
  5. Record updated
  6. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

Scored 7.6 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Adobe Commerce, not every advisory.