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

New CVE Detected

CVE-2026-77109 – Privilege Escalation via Incorrect Authorization – Adobe Commerce / Magento Open So

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

Summary

CVE-2026-77109 is an Incorrect Authorization vulnerability (CWE-863) affecting Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The flaw allows an attacker to escalate privileges and gain unauthorized access to restricted resources without requiring authentication or any victim interaction. Adobe rates the issue High severity (CVSS 3.1 base score 8.6) and disclosed it alongside a separate, unrelated critical remote code execution flaw in the same product line.

Technical details

  • Root cause: The application fails to correctly enforce authorization checks on certain functionality, allowing a user or unauthenticated actor to access resources or perform actions that should be restricted to higher-privileged roles (CWE-863 – Incorrect Authorization).
  • Trigger conditions: No prior authentication or privileges are required to trigger the flaw (PR:N), and no user interaction is needed (UI:N).
  • Attack vector: Network-based (AV:N) with low attack complexity (AC:L), meaning it can be exploited remotely over the network without special conditions.
  • Impact: The vulnerability results in privilege escalation with a confidentiality impact only under a changed scope (S:C, C:H per CVSS vector), meaning the attacker can gain unauthorized access to data or functionality belonging to another security scope (e.g., beyond the vulnerable component itself), without affecting integrity or availability.
  • The issue was reported to Adobe by the researcher known as 0x0.eth (0x0doteth), alongside two related CVEs (CVE-2026-76200 and CVE-2026-76201) disclosed in the same Adobe security bulletin.

Affected software

  • Adobe Commerce: versions up to 2.4.9-2026-aug (and earlier feature-branch builds) — fixed in 2.4.4-2026-sep and later cumulative updates
  • Adobe Commerce B2B: versions up to 1.5.3-2026-aug — fixed in 1.3.3-2026-sep and later
  • Magento Open Source: versions up to 2.4.9-2026-aug — fixed in 2.4.7-2026-sep and later

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 Adobe Commerce, Adobe Commerce B2B, and Magento Open Source installations to the fixed versions specified in Adobe’s security bulletin (2.4.7-2026-sep, 2.4.4-2026-sep, or 1.3.3-2026-sep as applicable to your product/branch), applying the vendor-provided patch through the standard Composer-based update process.
  • If immediate patching is not possible: Restrict administrative and API endpoint access to trusted networks/IP ranges, enforce strong authentication on admin panels, and closely monitor access and authorization logs for anomalous privilege-related activity until the patch can be applied.
  • Given that this bulletin was released alongside actively exploited vulnerabilities in the same product line, organizations should treat patching as urgent and verify no signs of prior compromise (e.g., unexpected admin accounts, unauthorized configuration changes) exist before and after remediation.

References

Are you exposed?

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

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