CWE-368: Context Switching Race Condition | Causes and Fixes Skip to content

Security weakness

CWE-368 Context Switching Race Condition

A base-level weakness that can lead to private data exposed, data and pages or code changed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-368?

Context Switching Race Condition: A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product’s behavior during the switch.

Business impact

What CWE-368 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Modify Application Data
  • Read Application Data

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Modify Application Data
  • Read Application Data

Free security check

Is CWE-368 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-368

Context Switching Race Condition

A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product’s behavior during the switch.

This is commonly seen in web browser vulnerabilities in which the attacker can perform certain actions while the browser is transitioning from a trusted to an untrusted domain, or vice versa, and the browser performs the actions on one domain using the trust level and resources of the other domain.

Weakness ID
CWE-368
Type
Base
Status
Draft
Introduced during
Architecture and Design, Implementation

Detection and evidence

How CWE-368 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-2009-1837Chain: race condition (CWE-362) from improper handling of a page transition in web client while an applet is loading (CWE-368) leads to use after free (CWE-416)
  • CVE-2004-2260Browser updates address bar as soon as user clicks on a link instead of when the page has loaded, allowing spoofing by redirecting to another page using onUnload method. ** this is one example of the role of "hooks" and.
  • CVE-2004-0191XSS when web browser executes Javascript events in the context of a new page while it’s being loaded, allowing interaction with previous page in different domain.
  • CVE-2004-2491Web browser fills in address bar of clicked-on link before page has been loaded, and doesn’t update afterward.

How we fix it

From finding to fixed: how Codefreex closes CWE-368

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

FAQ

CWE-368: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-368?

CWE-368, “Context Switching Race Condition”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product’s behavior during the switch.

How serious is CWE-368?

It can affect integrity, confidentiality, with impacts such as modify application data, read application data. The real risk depends on where the weakness sits and what data or functions it exposes.

Can Codefreex check my site for CWE-368?

Yes. A senior engineer reviews your site, store or app for CWE-368 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-368 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.