Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-92909 – Incorrect Authorization leading to RCE – Adobe Commerce, Adobe Commerce B2B and Mag

Be the first to know when new zero-days emerge:

Summary

CVE-2026-92909 is a critical Incorrect Authorization vulnerability (CWE-863) in Adobe Commerce, Adobe Commerce B2B and Magento Open Source. It can result in arbitrary code execution in the context of the current user, and is rated CVSS 9.8 (Critical). Adobe published a fix in security bulletin APSB26-153 on October 13, 2026, and reports no known active exploits at the time of publication.

Technical details

  • Root cause: Incorrect authorization (CWE-863). Adobe has not published further technical detail.
  • Trigger conditions: No authentication and no user interaction are required.
  • Attack vector: Network. Low attack complexity.
  • Impact: Arbitrary code execution, with high impact on confidentiality, integrity and availability.
  • Scope note: The CVE record lists Adobe Commerce, Adobe Commerce B2B and Magento Open Source as affected. The Adobe bulletin text describes this CVE as affecting Adobe Commerce B2B. Treat all three products as in scope until you have reviewed the bulletin.

Affected software

Per the CVE record, the affected releases are the September 2026 releases and earlier of:

  • Adobe Commerce: 2.4.4 through 2.4.9 (up to the 2026-sep releases)
  • Adobe Commerce B2B: 1.3.3 through 1.5.3 (up to the 2026-sep releases)
  • Magento Open Source: 2.4.7 through 2.4.9 (up to the 2026-sep releases)

Severity

CVSS v3.1 base score 9.8 (Critical): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to the October 2026 security release for your product line, as listed in APSB26-153. The CVE record lists these fixed versions:
    • Adobe Commerce: 2.4.4-2026-oct and later, or 2.4.10-alpha1
    • Adobe Commerce B2B: 1.3.3-2026-oct and later, or 1.5.4-alpha1
    • Magento Open Source: 2.4.7-2026-oct and later, or 2.4.10-alpha1
  • The bulletin’s remediation section lists the 2.4.9-2026-oct release for Adobe Commerce and Magento Open Source, and 1.5.3-2026-oct for B2B. Confirm the correct patched version for your branch against the bulletin and release notes.
  • If you cannot patch immediately: No workarounds are published in the sources reviewed. Restrict public network access to Commerce administrative and API endpoints where feasible, and monitor for unexpected code execution or file changes until you can patch.

References

Get a free Attack Surface scan to see if you’re exposed.

Get a free Attack Surface scan to see if you’re exposed.

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge