# CWE-203: Observable Discrepancy > As of 2026-10-11, CWE-203 (Observable Discrepancy) underlies 3 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 4 tracked threats. **Last updated:** 2026-10-11 ## What is CWE-203? The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor. CWE-203 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Not Language-Specific; Not Technology-Specific. _Source: [MITRE CWE](https://cwe.mitre.org/data/definitions/203.html) (CWE-203 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data._ ## Consequences - **Confidentiality, Access Control** — Read Application Data, Bypass Protection Mechanism. An attacker can gain access to sensitive information about the system, including authentication information that may allow an attacker to gain access to the system. Other security-relevant information about the operation or internal state of the product may be revealed to an unauthorized actor, such as whether a particular operation was successful or not. - **Confidentiality** — Read Application Data. In some cases, discrepancies can be used by attackers to form a side channel. When cryptographic primitives are vulnerable to side-channel attacks, this could be used to reveal unencrypted plaintext in the worst case. _Source: MITRE CWE, common consequences._ ## How CWE-203 is exploited in the wild Threadlinqs maps 3 CVEs to CWE-203, published between 2026-06-20 and 2026-09-09. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 3 medium. The highest EPSS score in the set is 0.2% (CVE-2026-87518), the modelled probability of exploitation in the next 30 days. 4 tracked threats reference CWE-203 directly or through a CVE it covers; the most recent is “Multiple Vulnerabilities in Microsoft Edge prior to 154.0.4258.53 (HK GovCERT A26-10-03)” (2026-10-02). Affected products concentrate in Capgo (2), Google (1). ## Vulnerabilities (CVEs) All 3 CVEs mapped to CWE-203, CISA KEV first, then by CVSS score. - [CVE-2026-87518](https://intel.threadlinqs.com/cve/CVE-2026-87518) — CVSS 5.3 medium · EPSS 0.2% · published 2026-09-09 - [CVE-2026-56327](https://intel.threadlinqs.com/cve/CVE-2026-56327) — CVSS 5.3 medium · EPSS 0.2% · published 2026-06-30 - [CVE-2026-56319](https://intel.threadlinqs.com/cve/CVE-2026-56319) — CVSS 4.3 medium · published 2026-06-20 ## Affected vendors - [Capgo](https://intel.threadlinqs.com/vendors/capgo) — 2 CVEs - [Google](https://intel.threadlinqs.com/vendors/google) — 1 CVE ## Threat activity 4 tracked threats cite CWE-203: - [Multiple Vulnerabilities in Microsoft Edge prior to 154.0.4258.53 (HK GovCERT A26-10-03)](https://intel.threadlinqs.com/threat/TL-2026-2838) — CRITICAL · 2026-10-02 - [Researcher Demonstrates Full C2 Inside ChatGPT Secure Sandbox via Chained Attack Techniques at Black Hat USA 2026](https://intel.threadlinqs.com/threat/TL-2026-1918) — HIGH · 2026-08-06 - [OAuth Client ID Spoofing Enables Silent Credential Validation Against Microsoft Entra ID — UNK_pyreq2323 & UNK_OutFlareAZ](https://intel.threadlinqs.com/threat/TL-2026-1342) — HIGH · 2026-07-14 - [GitHub Enterprise Server 3.20.3 — Pre-Auth SSRF in Upload Endpoint (CVE-2026-9312) + Bundled "Dirty Frag" Kernel LPEs (CVE-2026-43284, CVE-2026-43500) + Mandatory GPG Signing Key Rotation](https://intel.threadlinqs.com/threat/TL-2026-0605) — CRITICAL · 2026-05-27 ## Mitigations - **Architecture and Design / Separation of Privilege**: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges. - **Implementation**: Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success. If errors must be captured in some detail, record them in log messages, but consider what could occur if the log message _Source: MITRE CWE, potential mitigations._ ## Related weaknesses - [CWE-200 Exposure of Sensitive Information to an Unauthorized Actor](https://intel.threadlinqs.com/cwe/CWE-200) Canonical: https://intel.threadlinqs.com/cwe/CWE-203 Source definition: https://cwe.mitre.org/data/definitions/203.html Detection rules and IOCs for threats exploiting CWE-203 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp