# CVE-2026-82543: vastsa FileCodeBox Pickup Limit views.py update_file_usage race condition


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-w3qf-xqhv-qhm8

## What is CVE-2026-82543?

CVE-2026-82543 is a medium-severity vulnerability in vastsa FileCodeBox, published on 30 Aug 2026. 

### Official description

A vulnerability was detected in vastsa FileCodeBox up to 2.3. This vulnerability affects the function update_file_usage of the file apps/base/views.py of the component Pickup Limit Handler. Performing a manipulation results in race condition. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 2.5.0 is able to resolve this issue. The patch is named 8d7d856c62d73badd0797eb4daec8d2ff10a403a. Upgrading the affected component is recommended.

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

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


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

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

## Is CVE-2026-82543 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82543 is a medium-severity vulnerability in vastsa FileCodeBox, published on 30 Aug 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82543 exists.

Affected product: vastsa FileCodeBox. 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-82543/ (Markdown: https://insights.sbomify.com/CVE-2026-82543/index.md)
```

## Sources

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

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