# CVE-2026-92464: Adobe Commerce | Improper Input Validation (CWE-20)

> High-privilege attackers can execute arbitrary code in Adobe Commerce via improper input validation without user interaction.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-3ccv-cmhh-p8rc

## What is CVE-2026-92464?

CVE-2026-92464 is a critical code injection vulnerability in Adobe Commerce, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-92464?


## How do I fix CVE-2026-92464?

No fix has been published for CVE-2026-92464 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92464 being exploited?

There is no known exploitation of CVE-2026-92464 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92464 and fix it if it is affected.

What it is: CVE-2026-92464 is a critical code injection vulnerability in Adobe Commerce, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92464 in the wild and no public exploit code.

Affected product: Adobe Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92464/ (Markdown: https://insights.sbomify.com/CVE-2026-92464/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92464
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92464
- OSV: https://osv.dev/vulnerability/CVE-2026-92464

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92464/
Summaries are generated and may contain mistakes; the official description above is the record.