Skip to content
Log inStart free trial

CWE-648: Incorrect Use of Privileged APIs

BaseLikelihood of exploit: Low

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: ensure that assumptions made by the APIs are valid, such as validity of arguments account for known weaknesses in the design/implementation of the API call the API from a safe context 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.

Consequences

  • Access Control: Gain Privileges or Assume Identity
  • Confidentiality: Read Application Data
  • Integrity, Confidentiality, Availability: Execute Unauthorized Code or Commands

How to prevent it

  • Implementation: Before calling privileged APIs, always ensure that the assumptions made by the privileged code hold true prior to making the call.
  • Architecture and Design: Know architecture and implementation weaknesses of the privileged APIs and make sure to account for these weaknesses before calling the privileged APIs to ensure that they can be called safely.
  • Implementation: If privileged APIs make certain assumptions about data, context or state validity that are passed by the caller, the calling code must ensure that these assumptions have been validated prior to making the call.
  • Implementation: If privileged APIs do not shed their privilege prior to returning to the calling code, then calling code needs to shed these privileges immediately and safely right after the call to the privileged APIs. In particular, the calling code needs to ensure that a privileged thread of execution will never be returned to the user or made available to user-controlled processes.
  • Implementation: Only call privileged APIs from safe, consistent and expected state.
  • Implementation: Ensure that a failure or an error will not leave a system in a state where privileges are not properly shed and privilege escalation is possible (i.e. fail securely with regards to handling of privileges).

Recent advisories

  • CVE-2026-76460 — A vulnerability in an API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication.
  • GHSA-gg9v-mgcp-v6m7 — OpenClaw: Unbound bootstrap setup codes allow privilege escalation during pairing
  • GHSA-g5cg-8x5w-7jpm — OpenClaw: Heartbeat context inheritance bypasses sandbox via senderIsOwner escalation
  • GHSA-h4jx-hjr3-fhgc — OpenClaw: Gateway Plugin Subagent Fallback `deleteSession` Uses Synthetic `operator.admin`
  • GHSA-qm2m-28pf-hgjw — OpenClaw: Gateway Plugin HTTP Auth Grants Unrestricted operator.admin Runtime Scope to All Callers
  • GHSA-fqw4-mph7-2vr8 — OpenClaw: Silent privilege escalation via gateway shared-auth reconnect
  • GHSA-9hjh-fr4f-gxc4 — OpenClaw: Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin
  • GHSA-hf68-49fm-59cq — OpenClaw Gateway: RCE and Privilege Escalation from operator.pairing to operator.admin via device.pair.approve
  • CVE-2026-20122 — A vulnerability in the API of Cisco Catalyst SD-WAN Manager could allow an authenticated, remote attacker to overwrite arbitrary files on the local file system.
  • GHSA-pm44-x5x7-24c4 — Apache Airflow Has an Authorization Bypass That Allows Unauthorized Task Log Access
  • GHSA-pwfv-3cvg-9m4c — org.xwiki.platform:xwiki-platform-oldcore makes Incorrect Use of Privileged APIs with DocumentAuthors
  • GHSA-mq5q-gpgv-pwxw — usememos/memos Incorrect Use of Privileged APIs vulnerability
  • GHSA-ghx2-6v4g-9wmm — usememos/memos makes Incorrect Use of Privileged APIs
  • GHSA-fv6c-rfg3-gvjw — usememos/memos makes Incorrect Use of Privileged APIs

All advisories for CWE-648

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor