# CVE-2026-16212: awesto django-shop Purchase Stock inventory.py race condition

> A race condition in the Purchase Stock Handler allows remote attackers to manipulate inventory data, requiring high complexity and permissions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-5982-pmj5-rx9v

## What is CVE-2026-16212?

CVE-2026-16212 is a low-severity vulnerability in awesto django-shop, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in awesto django-shop up to 1.2.4. Affected is an unknown function of the file shop/models/inventory.py of the component Purchase Stock Handler. The manipulation leads to race condition. The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitability is told to be difficult. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-16212 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16212 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16212 is a low-severity vulnerability in awesto django-shop, published on 19 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-16212 exists.

Affected product: awesto django-shop. 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-16212/ (Markdown: https://insights.sbomify.com/CVE-2026-16212/index.md)
```

## Sources

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

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