CriticalCVE-2026-71362

    Adobe Commerce | Incorrect Authorization (CWE-863) (CVE-2026-71362)

    Published Last modified In CISA KEV since Sources: CVE.org, Adobe, BSI

    What is affected, what to do

    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.

    The vulnerability is being actively exploited; treat it as a priority. Update commerce to version 2.4.4, commerce_b2b to version 1.3.3, Magento to version 2.4.7-2026-aug. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Adobe Commerce lte 2.4..2.4.9-2026-jul
    • Adobe Commerce lte 2.4..2.4.8-2026-aug
    • Adobe Commerce lte 2.4..2.4.7-2026-aug
    • Adobe Commerce lte 2.4..2.4.6-2026-aug
    • Adobe Commerce lte 2.4..2.4.5-2026-aug
    • Adobe Commerce lte *..2.4.4-2026-aug
    • Adobe Commerce B2B lte 1.5..1.5.3-2026-jul
    • Adobe Commerce B2B lte 1.5..1.5.2-2026-jul
    • Adobe Commerce B2B lte 1.4..1.4.2-2026-jul
    • Adobe Commerce B2B lte 1.3..1.3.4-2026-jul
    • Adobe Commerce B2B lte *..1.3.3-2026-jul
    • Adobe Magento Open Source lte 2.4..2.4.9-2026-jul
    • Adobe Magento Open Source lte 2.4..2.4.8-2026-jul
    • Adobe Magento Open Source lte 2.4..2.4.7-2026-jul
    • Adobe Magento Open Source lte *..2.4.6-2026-jul

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.1

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CVE.org, Adobe, BSI

    87.5 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.76

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    248.99 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    87.5 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.76
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-863

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw is network-reachable without authentication or user interaction, carries high confidentiality and integrity impact, and sits among the CVEs most likely to be exploited. Authorisation bypasses in Adobe Commerce are typically used to obtain admin or API access, harvest customer records and plant payment skimmers in checkout pages. Targets are internet-facing storefronts of every size, especially those on slow patch cycles. CISA does not flag ransomware use, but the exposure of card and personal data (PCI DSS, GDPR) is immediate. Treat every internet-exposed instance as critical and patch or wall it off within 24 hours.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Build an inventory and confirm versions: Enumerate every Adobe Commerce and Magento Open Source instance, including staging, headless backends and forgotten legacy storefronts. Confirm the release with bin/magento --version. Treat 2.4.4 and any other release lines listed in the advisory as affected.
      • Apply the vendor security update: A patch is available from the vendor. Look up the exact version or isolated patch in the Adobe Security Bulletin for Adobe Commerce. Then run bin/magento setup:upgrade, flush caches and verify deployment integrity. Prioritise moving stores on end-of-support lines such as 2.4.4 onto a supported release line.
      • Restrict the admin and API surface now: Limit the custom admin path, plus /rest/ and /graphql for privileged operations, to known source IPs (VPN, office, integration partners) via reverse proxy or WAF until the patch is deployed.
      • Hunt for compromise before closing the ticket: Review admin_user, integration, oauth_consumer and oauth_token for unknown entries. Grep core_config_data (design/head/includes, design/footer/absolute_footer, design/head/scripts) and cms_block/cms_page content for foreign <script> tags, the usual hiding spots for payment skimmers.
      • Rotate credentials: Reset all admin passwords, reissue integration and API tokens, and renew payment gateway API keys and SMTP credentials. Rotate the encryption key in app/etc/env.php if any evidence of unauthorised access turns up.
      • Prepare notifications: If customer or card data may have leaked, engage your DPO (GDPR Art. 33, 72 h), your payment service provider or PCI DSS acquirer, and, for NIS2-scoped entities, the national CSIRT/BSI early.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Run the Commerce backend in a dedicated DMZ zone. Make the database (3306/tcp), Redis (6379/tcp), OpenSearch/Elasticsearch (9200/tcp) and RabbitMQ (5672/tcp) reachable only from the application tier. Enforce an egress allowlist on web nodes covering only payment providers, Adobe repositories and required APIs.
      • WAF/IPS: Block requests to privileged REST routes (/rest/*/V1/integration/, /rest/*/V1/customers, /rest/*/V1/orders, admin-level GraphQL mutations) that arrive without a valid bearer token or from non-approved networks. Rate-limit /rest/ and /graphql per source IP, and alert on abnormal request volumes against customer and order endpoints.
      • IAM / least privilege: Strip admin roles down to the minimum and disable unused accounts and integrations. Enforce 2FA for every admin user and keep Magento_TwoFactorAuth enabled. Issue integration tokens with the narrowest possible resource ACLs.
      • Host hardening: Make the codebase read-only for the web server user, except var/, generated/, pub/media/ and pub/static/. Deny PHP execution under pub/media/ in the web server config. Enable file integrity monitoring on app/, vendor/ and pub/.
      • Content Security Policy: Run Magento_Csp in restrict mode on checkout pages with an explicit script-source allowlist. This limits card-data exfiltration to foreign domains even after a successful privilege escalation.

    3. Runbook step 3

      Detection rules

      • Web server access logs: Detect successful (200/201) privileged REST or GraphQL calls from IPs with no prior admin login or token request. SPL sketch: index=web uri_path="/rest/*" (method=POST OR method=PUT OR method=DELETE) status IN (200,201) NOT src_ip IN (allowlist) | stats count by src_ip, uri_path
      • Database / application audit: Alert on new rows in admin_user, integration or oauth_token, and on changes to core_config_data (design/*, payment/*, web/*) outside change windows. Sources include Adobe Commerce admin action logs, DB audit plugins or scheduled hash diffs.
      • EDR process ancestry: A php-fpm/apache2 → sh/bash → curl/wget/base64/python chain indicates a post-escalation web shell. Sigma shape: ParentImage|endswith: ['/php-fpm','/apache2','/httpd'] AND Image|endswith: ['/sh','/bash','/curl','/wget']
      • Linux auditd / FIM: Watch for writes to *.php under pub/, app/code/ or vendor/ by the web server user, e.g. -w /var/www/magento/pub -p wa -k magento_pub. Any new PHP file in pub/media/ is highly suspicious.
      • Network telemetry (Zeek/Suricata): Flag outbound HTTPS/DNS from web nodes to newly registered or unknown domains. Watch CSP violation reports (report-uri) for new script origins on checkout.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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. Exploitation of this issue does not require user interaction.

    Source: NVD (NIST), CISA KEV Catalog, adobe_bulletin, cvelistv5, BSI WID Portal, BSI CSAF

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    AdobeAdobe Commerce
    • 2.4 – ≤ 2.4.5-2026-aug
    • 2.4 – ≤ 2.4.7-2026-aug
    • ≤ 2.4.4-2026-aug
    • 2.4 – ≤ 2.4.6-2026-aug
    • 2.4 – ≤ 2.4.9-2026-jul
    • 2.4 – ≤ 2.4.8-2026-aug
    • —
    • —
    • —
    • —
    • —
    • —
    AdobeAdobe Commerce B2B
    • 1.3 – ≤ 1.3.4-2026-jul
    • 1.4 – ≤ 1.4.2-2026-jul
    • 1.5 – ≤ 1.5.2-2026-jul
    • 1.5 – ≤ 1.5.3-2026-jul
    • ≤ 1.3.3-2026-jul
    • —
    • —
    • —
    • —
    • —
    AdobeMagento Open Source
    • 2.4 – ≤ 2.4.8-2026-jul
    • 2.4 – ≤ 2.4.9-2026-jul
    • ≤ 2.4.6-2026-jul
    • 2.4 – ≤ 2.4.7-2026-jul
    • —
    • —
    • —
    • —
    adobecommerce
    • 2.4.5
    • 2.4.6
    • 2.4.4
    • 2.4.7
    • 2.4.8
    • 2.4.9
    • < 2.4.4
    • —
    • —
    • —
    • —
    • —
    • —
    • 2.4.4
    adobecommerce_b2b
    • 1.3.4
    • 1.4.2
    • 1.3.3
    • 1.5.2
    • 1.5.3
    • < 1.3.3
    • —
    • —
    • —
    • —
    • —
    • 1.3.3
    adobemagento
    • 2.4.7
    • 2.4.8
    • 2.4.9
    • ≤ 2.4.6
    • —
    • —
    • —
    • —
    AdobeMagento
    • < 2.4.7-2026-aug
    • < 2.4.8-2026-aug
    • < 2.4.6-2026-aug
    • < 2.4.9-2026-aug
    • 2.4.7-2026-aug
    • 2.4.8-2026-aug
    • 2.4.6-2026-aug
    • 2.4.9-2026-aug

    Weakness classes (CWE)

    • CWE-863Incorrect Authorization

      Class

      The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

      Entry at MITRE CWE-863

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    SourceReferenceMaturityPublished
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    PoC-in-GitHub (nomi-sec)cve-2026-71362-magento-lab (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • helpx.adobe.comsecurity/products/magento/apsb26-92.htmlVendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-71362government-resource

    Reanalysis & status changes

    Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.

    1. Modified Analysisnvd@nist.gov

      • Reference Type: after CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-71362 Types: US Government Resource

    2. CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0

      • SSVC: before {"id":"CVE-2026-71362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…
      • SSVC: after {"id":"CVE-2026-71362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…

    3. CVE CISA KEV Update9119a7d8-5eab-497f-8521-727c672e3725

      • Date Added: after 2026-09-24
      • Due Date: after 2026-09-24
      • Required Action: after 2026-09-24
      • Vulnerability Name: after 2026-09-24

    4. CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0

      • Reference: after https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-71362
      • SSVC: before {"id":"CVE-2026-71362","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technical…
      • SSVC: after {"id":"CVE-2026-71362","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…

    5. Initial Analysisnvd@nist.gov

      • CPE Configuration: after OR *cpe:2.3:a:adobe:commerce:2.4.4:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:*:*:*:*:*:*:*:* versions up to (excluding) 2.4.4 *cpe:2.3:a:adobe:commerce:2.4.5:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:b1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:b2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:beta3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:beta1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:beta2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.9:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.6:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.4:p18:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.5:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.7:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce:2.4.8:p5:*:*:*:*:*:*
      • CPE Configuration: after OR *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:*:*:*:*:*:*:*:* versions up to (excluding) 1.3.3 *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p11:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p12:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:-:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p13:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p6:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p1:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p14:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p7:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p2:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p15:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p8:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p3:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p4:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p9:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p16:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.3:p18:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.3.4:p17:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.4.2:p10:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.2:p5:*:*:*:*:*:* *cpe:2.3:a:adobe:commerce_b2b:1.5.3:-:*:*:*:*:*:*
      • CPE Configuration: after OR *cpe:2.3:a:adobe:magento:2.4.7:b1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:b2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:beta3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:beta1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p4:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:beta2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p5:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p6:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p1:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p7:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p2:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p8:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p3:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p9:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p4:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.7:p10:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.8:p5:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:2.4.9:-:*:*:open_source:*:*:* *cpe:2.3:a:adobe:magento:*:*:*:*:open_source:*:*:* versions up to (including) 2.4.6
      • Reference Type: after Adobe Systems Incorporated: https://helpx.adobe.com/security/products/magento/apsb26-92.html Types: Vendor Advisory

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-71362
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-71362"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-71362.svg?lang=en" alt="CVE-2026-71362 – NEOSEC Intel" height="20"></a>