CVE-2026-71362: Adobe Commerce and Magento Session Binding Authorization Bypass
HERMES THREAT SCORE & ENTERPRISE RISK EXPOSURE
Target:Enterprise Commerce Platforms, Payment Gateways & Merchant Infrastructure 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 AGENTIC SEVERITY & PERIMETER BOUNDARY IMPACT
Target:Adobe Commerce GraphQL/REST Session Authorization Handler & Customer Binding Engine 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.
CVE-2026-71362: Adobe Commerce and Magento Session Binding Authorization BypassVULNERABILITY
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.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: 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.”
- [technical_analysis]Pillar Security demonstrated that executing export BASH_ENV in Auto-Run causes bash to source hostile payloads upon subsequent commands. — Source: Pillar Security Research: Bypassing Cursor Auto-Run: When Shell Built-ins Lead to Host RCE (Reliability: 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.”
- [technical_analysis]Pillar Security demonstrated that executing export BASH_ENV in Auto-Run causes bash to source hostile payloads upon subsequent commands. — Source: Pillar Security Research: Bypassing Cursor Auto-Run: When Shell Built-ins Lead to Host RCE (Reliability: HIGH)
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.
| Parameter | Technical Specification | Operational Impact |
|---|---|---|
| CVE Identifier | CVE-2026-71362 | CISA KEV Exploited Entry / Adobe APSB26-92 |
| Vulnerability Class | Incorrect Authorization (CWE-863) | Broken customer session binding |
| Vulnerable Component | Magento\Customer\Model\Session & GraphQL Customer Resolver | Missing authorization validation on customer tokens |
| Exploitation Vector | Unauthenticated GraphQL query or REST API request with target customer identifier | Remote account hijacking and checkout alteration |
| Privileges Required | None (PR:N) | Completely unauthenticated remote attack |
| Privileges Obtained | Targeted Customer / Commercial Buyer Privileges | Access to PII, saved cards, and active orders |
| Affected Versions | Adobe Commerce 2.4.4 - 2.4.9; Magento Open Source 2.4.6 - 2.4.9 | E-commerce storefronts, B2B wholesale portals |
| Fixed Updates | Adobe Commerce 2.4.9-p1, 2.4.8-p3, 2.4.7-p4 | Session 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:
- PII Exfiltration: The attacker queries the victim’s saved shipping addresses, order histories, and phone numbers.
- Payment Token Extraction: Stored credit card tokens associated with integrated payment gateways (PayPal, Braintree, Stripe) can be inspected or leveraged to place fraudulent purchases.
- 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- Target Identification: The adversary enumerates valid customer IDs or targets high-value corporate buyer accounts on the Magento store.
- Crafted GraphQL Request: The attacker sends an HTTP POST request to
/graphqlspecifying the target customer ID in query parameters or session headers without supplying valid login credentials. - Improper Authorization Trigger: Magento’s resolver bypasses token cryptographic verification and binds the requested customer profile to the execution thread.
- Data Exfiltration: The server responds with complete customer records, including full names, billing details, and recent transaction history.
- 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:
Incident Response Commands
Section titled “Incident Response Commands”# 1. Search access logs for suspicious GraphQL customer queries with unusual parametersgrep -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 IDsawk -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 databasemysql -u magento -p -e "SELECT entity_id, parent_id, city, street, telephone, updated_atFROM customer_address_entityWHERE 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 recentlymysql -u magento -p -e "SELECT user_id, username, email, created, is_activeFROM admin_userORDER BY user_id DESC LIMIT 10;" magento_db
# 5. Review Magento exception and security logs for authorization failurestail -n 100 /var/www/html/var/log/exception.log | grep -i "GraphQlAuthorizationException"5. Threat Hunting & Detection Engineering
Section titled “5. Threat Hunting & Detection Engineering”title: Adobe Commerce Unauthenticated GraphQL Customer Query Spikesid: 71362c01-magento-graphql-auth-bypassstatus: experimentaldescription: Detects unusual volume or unauthorized query patterns targeting customer and cart endpoints in Adobe Commerce GraphQL.author: Hermes Codex Detection Engineeringdate: 2026-09-25logsource: category: webserver product: magentodetection: 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_cookiefalsepositives: - Guest checkout workflows legitimately retrieving public catalog or guest cart states.level: hightags: - attack.initial_access - attack.t1190 - attack.credential_access - attack.t1539 - cve.2026-71362# ModSecurity rule to block direct customer_id manipulation in unauthenticated GraphQL requestsSecRule REQUEST_URI "@streq /graphql" \ "id:202671362,phase:2,deny,status:403,log,msg:'HERMES — Adobe Commerce GraphQL Authorization Bypass Attempt (CVE-2026-71362)',\ chain" SecRule REQUEST_BODY "@rx (?i)customer\s*\(\s*customer_id\s*:\s*\d+" \ "chain" SecRule !REQUEST_COOKIES:PHPSESSID "@rx ^[a-zA-Z0-9_-]{16,}$"6. Remediation & Hardening Roadmap
Section titled “6. Remediation & Hardening Roadmap”Deploy Adobe Security Bulletin APSB26-92
Section titled “Deploy Adobe Security Bulletin APSB26-92”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.
Temporary Defense-in-Depth Mitigations
Section titled “Temporary Defense-in-Depth Mitigations”- Disable Public Introspection on GraphQL: Disable GraphQL schema introspection in production environments to prevent automated field discovery.
- Enforce Two-Factor Authentication: Require 2FA on all merchant administrator accounts and corporate customer portals.
- 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”- CVE-2026-5430: WSO2 API Manager JWT Bypass: Identity brokering and token authorization breakdown on API gateways.
- CVE-2026-82331: Apache BuildStream Link Resolution Vulnerability: Pipeline compromise and arbitrary filesystem writes in build environments.
- CVE-2026-31377: Apache Doris Frontend Meta Service Authentication Flaw: Unauthenticated cluster topology extraction and data spoofing.
- AAP-003: Tool Parameter Tampering: Session context parameter manipulation in automated software workflows.
- AAP-007: Autonomous Cascading RCE: Chaining e-commerce session takeover into secondary code execution.
- AI Agent Misconfigurations Guide: Addressing insecure session delegation in automated agents.
- Security Alert Triage Playbook: Operational playbook for investigating perimeter web application compromises.
Sources & References
Section titled “Sources & References”- CISA Known Exploited Vulnerabilities Catalog: CISA KEV CVE-2026-71362
- Adobe Security Bulletin: APSB26-92 Security Update for Adobe Commerce
- NIST National Vulnerability Database: CVE-2026-71362 Detail