# CVE-2026-128042: OpenMage magento-lts before 20.19.0 Race Condition in Coupon Usage Limits


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-5rg7-22cv-c9q6, GHSA-chw3-wcrj-gqxx

## What is CVE-2026-128042?

CVE-2026-128042 is a medium-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 

### Official description

OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains a race condition in shopping cart price rule usage limits, because Mage_SalesRule_Model_Validator checks coupon limits without locking and the usage counters are later incremented non-atomically. Unauthenticated attackers, including guest shoppers, can submit concurrent checkouts to redeem a limited coupon more times than its cap allows.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2026-128042 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128042 is a medium-severity vulnerability in OpenMage magento-lts, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128042 in the wild and no public exploit code.

Affected product: OpenMage magento-lts. 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-128042/ (Markdown: https://insights.sbomify.com/CVE-2026-128042/index.md)
```

## Sources

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

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