CVE-2026-95631: Adobe Commerce | Improper Input Validation (CWE-20)
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.88% (FIRST EPSS); higher than 59.6% of all records.
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Adobe Commerce is affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. An attacker with high privileges could exploit this vulnerability to execute arbitrary code. Exploitation of this issue does not require user interaction. Scope is changed.
- Published
- Oct 13, 2026
- Updated
- Nov 10, 2026
- EPSS
- 0.8% · 59th percentile
- CWE
- CWE-20
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.1
- CNA · adobe
- 8.7
- 0.4 point gap
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| adobe | commerce b2b | cpe:2.3:a:adobe:commerce_b2b |
| adobe | commerce | cpe:2.3:a:adobe:commerce |
| adobe | magento | cpe:2.3:a:adobe:magento |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (adobe). Independent of NVD's CPE analysis and usually ahead of it.
Adobe Adobe Commerce
- 2.4.10-alpha1,2.4.9-2026-oct, 2.4.8-2026-oct, 2.4.7-2026-oct, 2.4.6-2026-oct, 2.4.5-2026-oct, 2.4.4-2026-octnot affected
- up to and including 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-sepaffected
Adobe Adobe Commerce B2B
- 1.5.4-alpha1,1.5.3-2026-oct, 1.5.2-2026-oct, 1.4.2-2026-oct, 1.3.4-2026-oct, 1.3.3-2026-octnot affected
- up to and including 1.5.3-2026-sep, 1.5.2-2026-sep, 1.4.2-2026-sep, 1.3.4-2026-sep, 1.3.3-2026-sepaffected
Adobe Magento Open Source
- 2.4.10-alpha1,2.4.9-2026-oct, 2.4.8-2026-oct, 2.4.7-2026-octnot affected
- up to and including 2.4.9-2026-sep, 2.4.8-2026-sep, 2.4.7-2026-sepaffected
Affected versions · NVD (17)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- adobe commercebefore 2.4.4
- adobe commerce2.4.4
- adobe commerce2.4.5
- adobe commerce2.4.6
- adobe commerce2.4.7
- adobe commerce2.4.8
- adobe commerce2.4.9
- adobe commerce b2bbefore 1.3.3
- adobe commerce b2b1.3.3
- adobe commerce b2b1.3.4
- adobe commerce b2b1.4.2
- adobe commerce b2b1.5.2
- adobe commerce b2b1.5.3
- adobe magentobefore 2.4.7
- adobe magento2.4.7
- adobe magento2.4.8
- adobe magento2.4.9
Same product
adobe: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-21290Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)34Monitor
- CVE-2026-21284Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)32Monitor
- CVE-2025-24418Adobe Commerce | Improper Authorization (CWE-285)32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-21289Mar 10, 2026 · Adobe Commerce | Incorrect Authorization (CWE-863)30Monitor
- ← EarlierCVE-2026-21292Mar 10, 2026 · Adobe Commerce | Cross-site Scripting (Stored XSS) (CWE-79)21Monitor
- ← EarlierCVE-2026-48416Aug 11, 2026 · Adobe Commerce | Incorrect Authorization (CWE-863)30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1313 · Oct 14, 2026(Adobe Çoklu Ürün Güvenlik Bildirimi )
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- CVSS8.7 → 9.1
- Severityhigh → critical
- SSVC exploitation— → none
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.