Skip to main content

Adobe Commerce CVE-2026-103849

| EUVDEUVD-2026-99219 CRITICAL
Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336)
2026-10-13 adobe GHSA-r2jr-3wj5-6696
10.0
CVSS 3.1 · Vendor: adobe
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach template-processing input surface
  2. Delivery
    Inject template-engine payload
  3. Exploit
    Server evaluates untrusted template
  4. Execution
    Execute arbitrary code on server
  5. Impact
    Escalate scope to host/account control

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V1 - Encoding and Sanitization Template injection prevention
Exploitation Conditions

Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N), this is characterized as remote, unauthenticated exploitation requiring no user interaction against Adobe Commerce, Adobe Commerce B2B, and Magento Open Source. The concrete prerequisite is that attacker-controlled input must reach a feature that passes data through the template engine (CWE-1336), but the advisory snippet does not name the exact template feature, parameter, or storefront/admin surface involved. Limiting factors to assess: the description states execution occurs 'in the context of the current user' and references 'the victim's account or session,' which may imply a session/account dependency not reflected in the PR:N rating; the specific affected version ranges are not provided, so exposure depends on the deployment running an unpatched release listed in APSB26-153.

Impact

This is a genuine top-priority vulnerability. The vendor-supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H = 10.0) describes the worst case: network-reachable, low-complexity, no privileges, no user interaction, with a scope change and full confidentiality/integrity/availability impact. CWE-1336 (server-side template injection) combined with the stated arbitrary code execution means full server compromise is the realistic outcome. However, the exploitation signals are currently thin and should temper 'drop-everything' framing: there is no EPSS score, no CISA KEV listing, and no public POC in the provided data, so this is 'no public exploit identified at time of analysis' rather than confirmed active exploitation. One internal tension to verify with the vendor: the description says code executes 'in the context of the current user' and references 'the victim's account or session,' which reads like a user-context/privilege nuance, yet the CVSS vector asserts PR:N/UI:N (fully unauthenticated, no interaction) - these are not obviously consistent for a template-injection flaw, and historically many Magento/Commerce SSTI issues live behind authenticated admin template-editing features. Treat the unauthenticated-no-interaction characterization as vendor-asserted until the APSB26-153 advisory detail confirms the exact injection surface.

Exploit ScenarioDerived

A remote attacker submits input that reaches a vulnerable template-processing path in Adobe Commerce/Magento and injects template-engine syntax that the server evaluates, achieving server-side code execution. Because scope is changed, the attacker can pivot beyond the application to the underlying host or other hosted components. No public exploit code was identified at time of analysis, but SSTI-to-RCE patterns in this platform are well understood and low-complexity per the CVSS vector.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Unauthenticated remote code execution affects Adobe Commerce, Adobe Commerce B2B, and Magento Open Source through improper neutralization of special elements used in a template engine (CWE-1336, server-side template injection). Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N/S:C), an attacker can reach the vulnerable template-processing surface over the network without credentials and without any victim interaction, and the scope change (S:C) indicates compromise can extend beyond the vulnerable component into the surrounding account or session context. The score is the maximum possible (10.0) and Adobe has published remediation guidance in APSB26-153; no public exploit code or confirmed active exploitation was identified at time of analysis, so the risk is driven by severity and ease of reachability rather than observed attacks.

RemediationAI

Patch status is: Patch available per vendor advisory. Apply the fixed releases specified in Adobe Security Bulletin APSB26-153 (https://www.adobe.com/trust/security/products/commerce/apsb26-153.html), which is the authoritative source for the exact patched version numbers for Adobe Commerce, Adobe Commerce B2B, and Magento Open Source; Adobe Commerce Cloud customers should track Adobe's managed patch deployment rather than self-patching. Because no exact fix version is enumerated in the available input data, verify the applicable version against the bulletin before upgrading, and test the update in a staging environment against custom CMS pages, blocks, and email templates, since template-related fixes can alter how existing content is rendered. If immediate upgrading is not possible, deploy targeted compensating controls and accept their trade-offs: place a WAF or reverse-proxy rule in front of the application that blocks template directive syntax in user-controllable parameters (double-brace and dollar-brace constructs), understanding that aggressive patterns can break legitimate CMS content and generate false positives; restrict network exposure of the admin panel and any template or email-template editing features to trusted networks or VPN, which limits the attack surface but does not eliminate the unauthenticated vector; and restrict who can create or edit CMS pages, blocks, and email templates, since content-authoring privileges may be an alternate path to the template engine - a trade-off that reduces editorial agility. Monitor application and web server logs for anomalous template directive payloads and unexpected PHP process behavior as a detection measure, and re-check the vendor bulletin for updates, as Adobe has historically issued hotfixes and follow-up bulletins for Commerce template issues.

Affected VersionsENISA

Adobe Commerce 0 ≤2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sep, 2.4.6-2026-sep, 2.4.5-2026-sep, 2.4.4-2026-sep
Magento Open Source 0 ≤2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sep
Adobe Commerce B2B 0 ≤1.5.3-2026-sep, 1.5.2-2026-sep, 1.4.2-2026-sep, 1.3.4-2026-sep, 1.3.3-2026-sep

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause class is CWE-1336, Improper Neutralization of Special Elements Used in a Template Engine - commonly called server-side template injection (SSTI). In this class, user-supplied data is concatenated into a template string and then parsed and evaluated by the application's template engine, so template directives supplied by the attacker are executed as code rather than treated as inert data. Adobe Commerce and Magento Open Source are PHP applications whose CMS pages, blocks, transactional emails, and layout rendering pass content through template-processing logic (historically the framework's Template Filter, which evaluates directive syntax such as double-brace variable and block constructs); a successful injection therefore yields arbitrary code execution under the PHP process, consistent with the 'current user' and session/account language in the advisory. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H describes a network-reachable, low-complexity, unauthenticated vector with no user interaction and high confidentiality, integrity, and availability impact, with the scope change reflecting that code execution can affect resources beyond the vulnerable component's own security authority. The supplied CPEs (cpe:2.3:a:adobe:adobe_commerce, cpe:2.3:a:adobe:adobe_commerce_b2b, cpe:2.3:a:adobe:magento_open_source) do not enumerate version ranges, and the advisory excerpt does not identify the exact template feature, parameter, or storefront versus admin surface involved - so the specific injection point, and whether defense in depth such as WAF virtual patching will cover it, is not confirmed from available data.

Know when Adobe Commerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (adobe) PRIMARY 10.0 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 10.0 CRITICAL

Adopting the vendor's network, low-complexity, no-privilege, no-interaction SSTI-to-RCE with scope change and full C/I/A impact; PR:N retained per vendor but flagged as needing confirmation given the 'current user' wording.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (adobe).

CVSS VectorVendor: adobe

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Adobe Commerce is affected by an Improper Neutralization of Special Elements Used in a Template Engine vulnerability that could result in arbitrary code execution in the context of the current user, potentially gaining elevated access or control over the victim's account or session. Exploitation of this issue does not require user interaction. Scope is changed.

Executive ViewAI

Why It Matters

Adobe Commerce, Adobe Commerce B2B, and Magento Open Source face a maximum-severity, unauthenticated remote code execution risk through server-side template injection. Because an attacker needs no credentials or user interaction and scope can extend beyond the vulnerable component, internet-facing commerce platforms could be fully compromised, threatening customer data, payment workflows, and brand trust. No public exploit code or confirmed active exploitation was identified at time of analysis, but the severity and reachability warrant immediate leadership attention.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include applying Adobe APSB26-153 remediation guidance, WAF/IPS rules for server-side template injection, restricting public exposure of admin and template-processing endpoints, least privilege, secret rotation, enhanced monitoring, and IOC scanning.

Threat Intelligence Overview

EPSS Score
0.8%
Top 45% exploitable
Prevalence
High
Adobe Commerce/Magento is a widely deployed enterprise e-commerce platform
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.8%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2026-75650 CRITICAL POC
10.0 Sep 07

Server-side template injection in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows remote unauthentica

CVE-2026-48356 CRITICAL
9.3 Jul 14

Arbitrary code execution in Adobe Commerce, Magento Open Source, Adobe Commerce B2B, and the Adobe Commerce Webhooks Plu

CVE-2026-47992 HIGH
7.2 Jul 14

SQL injection in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks Plugin allows

CVE-2026-47996 MEDIUM
6.8 Jul 14

Security feature bypass in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks plug

CVE-2026-92909 CRITICAL
9.8 Oct 13

Remote, low-complexity code execution is possible in Adobe Commerce, Adobe Commerce B2B and Magento Open Source through

CVE-2021-36020 CRITICAL
9.8 Sep 01

Magento Commerce versions 2.4.2 (and earlier), 2.4.2-p1 (and earlier) and 2.3.7 (and earlier) are affected by an XML Inj

CVE-2026-100133 CRITICAL
9.3 Oct 13

Stored cross-site scripting in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows a remote attacker to p

CVE-2026-91013 CRITICAL
9.3 Oct 13

Stored cross-site scripting (XSS) in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows an attacker who

CVE-2026-48358 CRITICAL
9.1 Jul 14

Arbitrary code execution in Adobe Commerce, Adobe Commerce B2B, Magento Open Source, and the Adobe Commerce Webhooks Plu

CVE-2026-92464 CRITICAL
9.1 Oct 13

Arbitrary code execution is achievable in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source by an attacker who

CVE-2026-47994 HIGH
8.7 Jul 14

Stored cross-site scripting in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source lets a low-privileged authent

CVE-2026-92911 HIGH
8.7 Oct 13

Stored cross-site scripting (XSS) in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allows an authenticated

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy