What CVEs are caused by CWE-1259?

14 recorded CVEs are attributed to CWE-1259, including CVE-2024-36533, CVE-2024-29371, CVE-2026-25700.

Is CWE-1259 actively exploited?

14 recorded CVEs are caused by CWE-1259; none are currently in CISA's KEV catalog of actively exploited flaws.

Base weakness

Incomplete

CWE-1259: Improper Restriction of Security Token Assignment

The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.

Last updated May 1, 2026

Recorded CVEs

With this primary weakness

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Base

Abstraction

MITRE classification

Overview

Systems-On-A-Chip (Integrated circuits and hardware engines) implement Security Tokens to differentiate and identify which actions originated from which agent. These actions may be one of the directives: 'read', 'write', 'program', 'reset', 'fetch', 'compute', etc. Security Tokens are assigned to every agent in the System that is capable of generating an action or receiving an action from another agent. Multiple Security Tokens may be assigned to an agent and may be unique based on the agent's trust level or allowed privileges. Since the Security Tokens are integral for the maintenance of security in an SoC, they need to be protected properly. A common weakness afflicting Security Tokens is improperly restricting the assignment to trusted components.

Real-world CVEs

14 recorded CVEs are caused by CWE-1259 (Improper Restriction of Security Token Assignment). The highest-severity and most recent are shown first. 2 new CWE-1259 CVEs have been recorded so far in 2026 (7 in 2025).

Showing 12 of 14 recorded CWE-1259 CVEs. Track new ones as they are published and get AI-written analysis and fixes.

Monitor CWE-1259 vulnerabilities

Common consequences

What can happen when CWE-1259 is exploited.

Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Modify Memory, Modify Memory, DoS: Crash, Exit, or Restart

Affects: Confidentiality, Integrity, Availability, Access Control

An improperly protected Security Token may be able to be programmed by a malicious agent (i.e., the Security Token is mutable) to spoof the action as if it originated from a trusted agent.

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Implementation

Applies to

Technologies

Processor Hardware

System on Chip

How to prevent it

Practical mitigations for CWE-1259, grouped by where in the lifecycle they apply.

Architecture and Design

Implementation

Security Token assignment review checks for design inconsistency and common weaknesses.
Security-Token definition and programming flow is tested in both pre-silicon and post-silicon testing.

Code examples

Illustrative examples from MITRE showing how the weakness appears in code.

For example, consider a system with a register for storing an AES key for encryption and decryption. The key is of 128 bits implemented as a set of four 32-bit registers. The key register assets have an associated control register, AES_KEY_ACCESS_POLICY, which provides the necessary access controls. This access-policy register defines which agents may engage in a transaction, and the type of transaction, with the AES-key registers. Each bit in this 32-bit register defines a security Token. There could be a maximum of 32 security Tokens that are allowed access to the AES-key registers. The number of the bit when set (i.e., "1") allows respective action from an agent whose identity matches the number of the bit and, if "0" (i.e., Clear), disallows the respective action to that corresponding agent.

Attack patterns

CAPEC attack patterns that exploit this weakness.

Frequently asked questions

Common questions about CWE-1259.

What is CWE-1259?: The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.
What CVEs are caused by CWE-1259?: 14 recorded CVEs are attributed to CWE-1259, including CVE-2024-36533, CVE-2024-29371, CVE-2026-25700.
What are the consequences of CWE-1259?: Exploiting CWE-1259 can lead to: Modify Files or Directories, Execute Unauthorized Code or Commands, Bypass Protection Mechanism, Gain Privileges or Assume Identity, Modify Memory, DoS: Crash, Exit, or Restart.
Is CWE-1259 actively exploited?: 14 recorded CVEs are caused by CWE-1259; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.

Stay ahead of CWE-1259

Get alerted the moment a new CWE-1259 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing