Skip to content

CVE-2026-71362: Adobe Commerce and Magento Session Binding Authorization Bypass

Density:
HERMES

HERMES THREAT SCORE & ENTERPRISE RISK EXPOSURE

Target: Enterprise Commerce Platforms, Payment Gateways & Merchant Infrastructure
Confidence: 95%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 19 / 20
Weaponization 18 / 20
Exposure 19 / 20
Prevalence 17 / 20
Impact 19 / 20
Exploit Maturity 18 / 20
Attack Chain Potential 19 / 20
⚖️ Divergence & Operational Rationale

Adobe assesses CVSS v3.1 at 9.1 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), while CISA assigns a maximum impact rating. Hermes Threat Score evaluates it at 93 (CRITICAL). E-commerce backends handle financial checkout pipelines and customer payment artifacts subject to PCI-DSS compliance. The inability of Magento's GraphQL session resolver to properly bind active sessions to client credentials enables zero-interaction customer hijacking. With confirmed exploitation in the wild (CISA KEV), adversaries actively target checkout pipelines for credit card skimming and automated order manipulation.

HASS

HASS AGENTIC SEVERITY & PERIMETER BOUNDARY IMPACT

Target: Adobe Commerce GraphQL/REST Session Authorization Handler & Customer Binding Engine
Confidence: 90%
65 / 100
HIGH

Measures specific systemic risk arising from autonomy, tool authority, and cascading execution.

Dimension Breakdown
Autonomy 14 / 20
Tool Access 16 / 20
Privilege 13 / 15
Persistence 9 / 15
External Impact 13 / 15
Propagation 0 / 15
⚖️ Divergence & Operational Rationale

Autonomous shopping assistants, customer service LLM agents, and procurement bots interface directly with Magento GraphQL and REST endpoints using delegated session tokens. An unauthenticated session hijacking flaw allows external actors to intercept agent shopping contexts, alter purchase approval thresholds, and spoof high-value commercial accounts without triggering traditional credential authentication alerts.

🕸️ Connected Knowledge Graph & Provenance

CVE-2026-71362: Adobe Commerce and Magento Session Binding Authorization BypassVULNERABILITY

Connected Nodes: 3
Active Relationships (Outgoing)
→ affectsPRODUCTAdobe Commerce & Magento Open Source
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

🔍 Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Adobe Commerce & Magento Open Source documented in Hermes dossier.”

Supporting Verified Evidence:
→ exploitsAGENTIC ATTACK_PATTERNAAP-003: Tool Parameter Tampering & Built-in Bypass
92% VERY_HIGH

Adversarial subversion of structured tool execution arguments (SQL, Shell, Filepath) passed from an LLM agent to host OS tools or MCP endpoints.

🔍 Why is this related? (Evidence & Provenance)

“CVE-2026-71362 weaponizes the agentic attack pattern formalized under AAP-003.”

Supporting Verified Evidence:
→ exploitsAGENTIC ATTACK_PATTERNAAP-007: Autonomous Cascading RCE
92% VERY_HIGH

Cascading multi-stage attack chaining context injection, autonomous loop planning, and un-sandboxed execution sinks to achieve persistent root shell compromise on host machines.

🔍 Why is this related? (Evidence & Provenance)

“CVE-2026-71362 weaponizes the agentic attack pattern formalized under AAP-007.”

Supporting Verified Evidence:

1. Technical Context & Affected Software Matrix

Section titled “1. Technical Context & Affected Software Matrix”

Adobe Commerce exposes both traditional REST endpoints (/rest/V1/*) and headless GraphQL interfaces (/graphql) to support single-page applications and mobile storefronts.

ParameterTechnical SpecificationOperational Impact
CVE IdentifierCVE-2026-71362CISA KEV Exploited Entry / Adobe APSB26-92
Vulnerability ClassIncorrect Authorization (CWE-863)Broken customer session binding
Vulnerable ComponentMagento\Customer\Model\Session & GraphQL Customer ResolverMissing authorization validation on customer tokens
Exploitation VectorUnauthenticated GraphQL query or REST API request with target customer identifierRemote account hijacking and checkout alteration
Privileges RequiredNone (PR:N)Completely unauthenticated remote attack
Privileges ObtainedTargeted Customer / Commercial Buyer PrivilegesAccess to PII, saved cards, and active orders
Affected VersionsAdobe Commerce 2.4.4 - 2.4.9; Magento Open Source 2.4.6 - 2.4.9E-commerce storefronts, B2B wholesale portals
Fixed UpdatesAdobe Commerce 2.4.9-p1, 2.4.8-p3, 2.4.7-p4Session token cryptographic binding enforcement

2. Vulnerability Anatomy & Root Cause Analysis

Section titled “2. Vulnerability Anatomy & Root Cause Analysis”

Session Context Resolution Breakdown in GraphQL

Section titled “Session Context Resolution Breakdown in GraphQL”

When a headless storefront issues a GraphQL request to retrieve customer information (such as customer { orders, addresses, email }), Magento’s GraphQl/Resolver/Customer.php relies on UserContextInterface to determine the caller’s identity:

// Concept of Flawed GraphQL Customer Resolution (Pre-Patch)
public function resolve(Field $field, $context, ResolveInfo $info, array $value = null, array $args = null)
{
// FLAW: If an unauthenticated client supplies a customer identity via context headers
// or specific query variables, the resolver checks if the customer exists in the registry
// but fails to verify that the active session token actually belongs to that customer!
$customerId = $context->getUserId();
if (!$customerId && isset($args['customer_id'])) {
// Insecure fallback: accepts client-provided parameter without credential validation
$customerId = (int)$args['customer_id'];
}
if ($customerId > 0) {
$customer = $this->customerRepository->getById($customerId);
return $this->formatCustomerData($customer);
}
throw new GraphQlAuthorizationException(__('The current customer isn\'t authorized.'));
}

Under unpatched conditions, certain GraphQL endpoints accepted an external parameter or manipulated cookie header that forced the session manager to load the targeted customer object into the active execution context. Because the verification routine failed to validate that an authentic cryptographic HMAC session token bound the client to that customerId, the request proceeded as if the legitimate customer had authenticated.

Session Hijacking & Payment Flow Tampering

Section titled “Session Hijacking & Payment Flow Tampering”

Once the session context is bound to the target customer:

  1. PII Exfiltration: The attacker queries the victim’s saved shipping addresses, order histories, and phone numbers.
  2. Payment Token Extraction: Stored credit card tokens associated with integrated payment gateways (PayPal, Braintree, Stripe) can be inspected or leveraged to place fraudulent purchases.
  3. Cart Manipulation: Active carts can be manipulated by updating the shipping address to an attacker-controlled drop point while retaining the victim’s saved payment methods.

3. Attack Vectors & Forensic Execution Flow

Section titled “3. Attack Vectors & Forensic Execution Flow”
sequenceDiagram
autonumber
actor Attacker as Remote Threat Actor (Internet)
participant Edge as Storefront Reverse Proxy / CDN
participant GraphQL as Magento GraphQL Service (/graphql)
participant Session as Customer Session Resolver
participant DB as MySQL Commerce Database
Attacker->>Edge: POST /graphql (Query: { customer(id: 1042) { email, orders } })
Edge->>GraphQL: Forward GraphQL request
GraphQL->>Session: Resolve user context from request parameters
Session-->>Session: Defect: Assign customerId=1042 without validating token signature
Session->>DB: SELECT * FROM customer_entity WHERE entity_id = 1042
DB-->>Session: Return customer profile, addresses & saved payment tokens
Session-->>GraphQL: Deliver customer data payload
GraphQL-->>Attacker: 200 OK (Full PII & order records returned)
Attacker->>GraphQL: Mutation: setShippingAddressOnCart(cart_id: ..., drop_address)
GraphQL->>DB: Update order delivery target to attacker drop location
  1. Target Identification: The adversary enumerates valid customer IDs or targets high-value corporate buyer accounts on the Magento store.
  2. Crafted GraphQL Request: The attacker sends an HTTP POST request to /graphql specifying the target customer ID in query parameters or session headers without supplying valid login credentials.
  3. Improper Authorization Trigger: Magento’s resolver bypasses token cryptographic verification and binds the requested customer profile to the execution thread.
  4. Data Exfiltration: The server responds with complete customer records, including full names, billing details, and recent transaction history.
  5. Checkout Hijacking: The attacker modifies active checkout carts or triggers order updates, rerouting physical goods or executing unauthorized transactions.

4. Forensic Investigation & Incident Response

Section titled “4. Forensic Investigation & Incident Response”

Security operations and DFIR specialists should audit web server logs and database records for patterns of automated customer session probing:

Terminal window
# 1. Search access logs for suspicious GraphQL customer queries with unusual parameters
grep -E "POST /graphql" /var/log/nginx/access.log | grep -E "(customer|orders|cart)" | awk '{print $1, $4, $7, $9}'
# 2. Check for burst requests targeting sequential customer IDs
awk -F\" '/POST \/graphql/ {print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -nr | head -n 20
# 3. Inspect recent modifications to customer shipping addresses in Magento database
mysql -u magento -p -e "
SELECT entity_id, parent_id, city, street, telephone, updated_at
FROM customer_address_entity
WHERE updated_at >= DATE_SUB(NOW(), INTERVAL 7 DAY)
ORDER BY updated_at DESC LIMIT 50;
" magento_db
# 4. Check for unauthorized administrative users or API integrations created recently
mysql -u magento -p -e "
SELECT user_id, username, email, created, is_active
FROM admin_user
ORDER BY user_id DESC LIMIT 10;
" magento_db
# 5. Review Magento exception and security logs for authorization failures
tail -n 100 /var/www/html/var/log/exception.log | grep -i "GraphQlAuthorizationException"

title: Adobe Commerce Unauthenticated GraphQL Customer Query Spikes
id: 71362c01-magento-graphql-auth-bypass
status: experimental
description: Detects unusual volume or unauthorized query patterns targeting customer and cart endpoints in Adobe Commerce GraphQL.
author: Hermes Codex Detection Engineering
date: 2026-09-25
logsource:
category: webserver
product: magento
detection:
selection_endpoint:
cs-method: 'POST'
cs-uri-stem: '/graphql'
selection_status:
sc-status: 200
filter_authenticated_cookie:
cs-cookie|contains: 'PHPSESSID'
condition: selection_endpoint and selection_status and not filter_authenticated_cookie
falsepositives:
- Guest checkout workflows legitimately retrieving public catalog or guest cart states.
level: high
tags:
- attack.initial_access
- attack.t1190
- attack.credential_access
- attack.t1539
- cve.2026-71362

Apply the official security updates released by Adobe immediately:

  • Adobe Commerce: Upgrade to 2.4.9-p1, 2.4.8-p3, or 2.4.7-p4.
  • Magento Open Source: Apply the corresponding security patch for branch 2.4.6, 2.4.7, 2.4.8, or 2.4.9.
  1. Disable Public Introspection on GraphQL: Disable GraphQL schema introspection in production environments to prevent automated field discovery.
  2. Enforce Two-Factor Authentication: Require 2FA on all merchant administrator accounts and corporate customer portals.
  3. Session Invalidation: Execute a global invalidation of active customer session tokens (php bin/magento cache:clean) following patch application.

7. Correlated Research & Internal References

Section titled “7. Correlated Research & Internal References”