# Race condition in a security-sensitive transition

Concurrent operations violate a rule that holds when the same actions run serially.

**Candidate CWE:** [CWE-362](https://cwe.mitre.org/data/definitions/362.html)

## Test hypothesis

Use a fresh nonfinancial fixture. Complete a normal serial/replay control, reset it, then submit two bounded simultaneous operations. Inspect durable state after both requests and workers finish.

## Evidence required

A duplicate membership, resource, or synthetic state transition persists. Include the invariant, initial state, serial control, concurrency mechanism, and committed result.

## Rule out false positives

Two 200 responses, transient UI counters, expected retries, or no verified timing overlap do not prove or disprove a race.

## Playbook and command references

- [Workflow invariants, replay, idempotency, and races](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/modules/state-business-logic.html) — Find security consequences in workflow ordering and concurrency, with serial controls and durable-state evidence.

[Find the associated command snippets](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/commands.html?q=Workflow%20invariants%2C%20replay%2C%20idempotency%2C%20and%20races)

## Referenced by these target playbooks

[Web & API](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web-api.html) · [OSS & self-hosted](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/oss.html) · [Mobile](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/mobile.html) · [Desktop & extensions](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/desktop.html) · [Cloud & containers](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/cloud.html) · [Web3 & protocols](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/web3.html)

## Report checklist

- [ ] Capture the affected version, configuration, identities, and object ownership.
- [ ] Preserve a valid baseline and a negative control.
- [ ] Reproduce the forbidden data access, action, or state change on controlled fixtures.
- [ ] Explain the intended security rule and why the observed behavior violates it.
- [ ] State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.

## Conditional ATT&CK mapping

No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the [mapping guide](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/attack.html).

## Primary references

- [PortSwigger race conditions](https://portswigger.net/web-security/race-conditions)

[Back to the complete vulnerability catalog](https://bug-bounty-field-manual.kmahshooq.chatgpt.site/vulnerabilities.html)