Threadlinqs IntelligenceStart free

Weakness · PillarCWE-693

CWE-693: Protection Mechanism Failure

KEV-linkedPillar

As of 2026-11-19, CWE-693 (Protection Mechanism Failure) underlies 51 CVEs tracked by Threadlinqs, 5 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 89 tracked threats.

CVEs
51Mapped to CWE-693
CISA KEV
5Exploited in the wild
Critical
13CVSS v3 critical CVEs
Threats
89Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-693?

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

This weakness covers three distinct situations. A "missing" protection mechanism occurs when the application does not define any mechanism against a certain class of attack. An "insufficient" protection mechanism might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. Finally, an "ignored" mechanism occurs when a mechanism is available and in active use within the product, but the developer has not applied it in some code path.

CWE-693 is a pillar-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Not Language-Specific; Technology: Not Technology-Specific; Technology: ICS/OT.

Source: MITRE CWE (CWE-693 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Access Control — Bypass Protection Mechanism

Source: MITRE CWE, common consequences.

How CWE-693 is exploited in the wild

Threadlinqs maps 51 CVEs to CWE-693, published between 2022-09-29 and 2026-11-17. 5 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 1 is tied to ransomware campaigns. By CVSS v3 severity the set splits into 13 critical, 17 high, 15 medium. The highest EPSS score in the set is 99.4% (CVE-2024-21412), the modelled probability of exploitation in the next 30 days. 89 tracked threats reference CWE-693 directly or through a CVE it covers; the most recent is “Chrome 158 Fixes 204 Vulnerabilities Including Six Critical Code Execution Flaws (CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975)” (2026-11-18). Affected products concentrate in Mozilla (10), Google (9), Microsoft (9), among 23 vendors in total.

Vulnerabilities (CVEs)

Showing 40 of 51 CVEs mapped to CWE-693, CISA KEV first, then by CVSS score.

  • CVE-2026-21510 — CISA KEV · CVSS 8.8 high · EPSS 24.5% · published 2026-02-10
  • CVE-2026-21513 — CISA KEV · CVSS 8.8 high · EPSS 15.8% · published 2026-02-10
  • CVE-2024-21412 — CISA KEV · CVSS 8.1 high · EPSS 99.4% · published 2024-02-13
  • CVE-2025-40536 — CISA KEV · CVSS 8.1 high · EPSS 73.5% · published 2026-01-28
  • CVE-2026-32202 — CISA KEV · CVSS 4.3 medium · EPSS 4.9% · published 2026-04-14
  • CVE-2025-68668 — CVSS 9.9 critical · EPSS 13.1% · published 2025-12-26
  • CVE-2026-25115 — CVSS 9.9 critical · EPSS 0.5% · published 2026-02-04
  • CVE-2026-106016 — CVSS 9.8 critical · EPSS 0.1% · published 2026-10-06
  • CVE-2022-39266 — CVSS 9.7 critical · EPSS 1.2% · published 2022-09-29
  • CVE-2026-81376 — CVSS 9.6 critical · EPSS 0.8% · published 2026-09-08
  • CVE-2026-12295 — CVSS 9.6 critical · EPSS 0.3% · published 2026-06-16
  • CVE-2026-12296 — CVSS 9.6 critical · EPSS 0.3% · published 2026-06-16
  • CVE-2026-12294 — CVSS 9.6 critical · EPSS 0.3% · published 2026-06-16
  • CVE-2026-130910 — CVSS 9.6 critical · published 2026-11-17
  • CVE-2026-16916 — CVSS 9.1 critical · EPSS 0.4% · published 2026-10-08
  • CVE-2026-12315 — CVSS 9.1 critical · EPSS 0.2% · published 2026-06-16
  • CVE-2026-12316 — CVSS 9.1 critical · EPSS 0.2% · published 2026-06-16
  • CVE-2026-74790 — CVSS 9.1 critical · published 2026-08-16
  • CVE-2025-69264 — CVSS 8.8 high · EPSS 1.0% · published 2026-01-07
  • CVE-2026-25056 — CVSS 8.8 high · EPSS 0.7% · published 2026-02-04
  • CVE-2026-97673 — CVSS 8.8 high · EPSS 0.4% · published 2026-10-07
  • CVE-2026-97678 — CVSS 8.8 high · EPSS 0.4% · published 2026-10-06
  • CVE-2026-19150 — CVSS 8.8 high · EPSS 0.4% · published 2026-08-06
  • CVE-2026-19168 — CVSS 8.8 high · EPSS 0.4% · published 2026-08-06
  • CVE-2026-124905 — CVSS 8.3 high · EPSS 0.3% · published 2026-11-10
  • CVE-2026-19152 — CVSS 8.3 high · EPSS 0.3% · published 2026-08-06
  • CVE-2026-12438 — CVSS 8.3 high · EPSS 0.2% · published 2026-06-17
  • CVE-2026-22112 — CVSS 7.8 high · EPSS 43.1% · published 2026-02-20
  • CVE-2026-82474 — CVSS 7.8 high · EPSS 0.1% · published 2026-08-29
  • CVE-2026-76283 — CVSS 7.6 high · EPSS 0.1% · published 2026-10-07
  • CVE-2026-113969 — CVSS 7.5 high · EPSS 0.2% · published 2026-11-09
  • CVE-2026-34348 — CVSS 6.5 medium · EPSS 0.7% · published 2026-07-14
  • CVE-2026-120202 — CVSS 6.5 medium · EPSS 0.2% · published 2026-10-31
  • CVE-2026-12302 — CVSS 6.5 medium · EPSS 0.2% · published 2026-06-16
  • CVE-2024-29510 — CVSS 6.3 medium · EPSS 27.9% · published 2024-07-03
  • CVE-2026-3965 — CVSS 6.3 medium · EPSS 0.4% · published 2026-03-12
  • CVE-2026-124910 — CVSS 6.1 medium · EPSS 0.1% · published 2026-11-10
  • CVE-2026-50661 — CVSS 6.1 medium · published 2026-07-14
  • CVE-2026-47624 — CVSS 6 medium · EPSS 0.1% · published 2026-08-25
  • CVE-2026-124940 — CVSS 5.4 medium · EPSS 0.1% · published 2026-11-10

Affected vendors

Threat activity

89 tracked threats cite CWE-693; the 25 most recent are listed.