CWE · MITRE source
CWE-648Incorrect Use of Privileged APIs
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
When a product contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to: If the caller of the API does not follow these requirements, then it may allow a malicious user or process to elevate their privilege, hijack the process, or steal sensitive data. For instance, it is important to know if privileged APIs do not shed their privileges before returning to the caller or if the privileged function might make certain assumptions about the data, context or state information passed to it by the caller. It is important to always know when and how privileged APIs can be called in order to ensure that their elevated level of privilege cannot be exploited.
Last updated: 15 October 2026 14:21 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-76460 KEV UPD | 10.0 | 10.0 | 0.1403 | 2026-09-16 |
CVE-2019-14813 UPD | 8.2 | 9.8 | 0.1096 | 2019-09-06 |
CVE-2024-8785 UPD | 8.2 | 9.8 | 0.0966 | 2024-12-02 |
CVE-2019-1010178 UPD | 7.9 | 9.8 | 0.0459 | 2019-07-24 |
CVE-2022-2023 UPD | 7.8 | 9.8 | 0.0320 | 2022-06-20 |
CVE-2024-11068 UPD | 7.5 | 9.8 | 0.0117 | 2024-11-11 |
CVE-2026-20122 KEV UPD | 7.5 | 5.4 | 0.2548 | 2026-02-25 |
CVE-2023-4972 UPD | 7.4 | 9.8 | 0.0069 | 2023-09-14 |
CVE-2019-14869 UPD | 7.1 | 8.8 | 0.0343 | 2019-11-15 |
CVE-2025-54769 UPD | 7.1 | 8.8 | 0.0333 | 2025-07-29 |
CVE-2026-41329 | 7.0 | 9.9 | 0.0052 | 2026-04-21 |
CVE-2026-41386 | 6.9 | 9.1 | 0.0057 | 2026-04-28 |
CVE-2024-37018 UPD | 6.8 | 9.1 | 0.0043 | 2024-05-31 |
CVE-2023-28062 UPD | 6.7 | 8.8 | 0.0077 | 2023-04-11 |
CVE-2026-35639 | 6.7 | 8.8 | 0.0084 | 2026-04-09 |
CVE-2023-29507 UPD | 6.6 | 9.1 | 0.0090 | 2023-04-16 |
CVE-2025-7344 UPD | 6.6 | 8.8 | 0.0056 | 2025-07-21 |
CVE-2026-35663 | 6.6 | 8.8 | 0.0052 | 2026-04-10 |
CVE-2026-35669 | 6.6 | 8.8 | 0.0052 | 2026-04-10 |
CVE-2025-5997 UPD | 6.5 | 8.8 | 0.0037 | 2025-07-28 |
CVE-2026-20126 UPD | 6.5 | 8.8 | 0.0031 | 2026-02-25 |
CVE-2026-63727 | 6.5 | 8.8 | 0.0044 | 2026-07-28 |
CVE-2019-14811 UPD | 6.4 | 7.8 | 0.0375 | 2019-09-03 |
CVE-2026-41225 UPD | 6.4 | 9.1 | 0.0046 | 2026-05-13 |
CVE-2019-10216 UPD | 6.3 | 7.8 | 0.0230 | 2019-11-27 |