Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-77774 – Unauthorized Read Access via Incorrect Authorization – Adobe Commerce, Magento Open

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-77774 is an Incorrect Authorization vulnerability (CWE-863) affecting Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The flaw allows an unauthenticated, remote attacker to bypass a security feature and gain unauthorized read access to data, without any user interaction. Adobe rates the issue HIGH severity with a CVSS v3.1 base score of 8.6.

Technical details

  • Root cause: an authorization check within the affected component is incorrectly implemented or missing, allowing access-control logic to be bypassed (CWE-863: Incorrect Authorization).
  • Trigger conditions: no privileges and no user interaction are required to exploit the flaw; the scope is changed (S:C), indicating the vulnerability can affect resources beyond the vulnerable component itself.
  • Attack vector: exploitable remotely over the network (AV:N) with low attack complexity (AC:L).
  • Impact: unauthorized read access to confidential data (C:H); integrity and availability are not affected (I:N/A:N).

Affected software

  • Adobe Commerce: versions 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, and 2.4.4-2026-aug, and earlier
  • Adobe Commerce B2B: versions 1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, and 1.3.3-2026-aug, and earlier
  • Magento Open Source: versions 2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, and 2.4.6-2026-aug, and earlier

Severity

CVSS v3.1 Base Score: 8.6 (High)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to the September 2026 patched releases referenced in Adobe Security Bulletin APSB26-138 (e.g., 2.4.4-2026-sep and later for Adobe Commerce; 1.3.3-2026-sep and later for Adobe Commerce B2B; corresponding September 2026 builds for Magento Open Source).
  • If immediate patching is not possible: restrict network exposure of the storefront/admin interfaces where feasible, monitor for unusual read requests to sensitive endpoints, and follow Adobe’s advisory for any interim configuration guidance.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: agento, type="text/x-magento-init"
  • Rendered page: mage.cookies (or mage/cookies)
  • Loaded script URL: js/mage
  • JavaScript object present at runtime: Mage, VarienForm

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge