Privilege Escalation
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
How It Works
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted. The attack exploits the gap between what the system thinks a user can do and what they actually can do through manipulation or exploitation.
Vertical escalation is the classic form—a regular user obtaining administrator rights. This happens through kernel exploits that bypass OS-level security, misconfigurations in role-based access control (RBAC) that fail to enforce boundaries, or direct manipulation of authorization tokens and session data. Horizontal escalation involves accessing resources belonging to users at the same privilege level, typically through insecure direct object references (IDOR) where changing an ID in a request grants access to another user's data.
Context-dependent escalation exploits workflow logic by skipping authorization checkpoints. An attacker might access administrative URLs directly without going through proper authentication flows, manipulate parameters to bypass permission checks, or exploit REST API endpoints that don't validate method permissions—like a read-only GET permission that can be leveraged for write operations through protocol upgrades or alternative endpoints.
Impact
- Full system compromise through kernel-level exploits granting root or SYSTEM privileges
- Administrative control over applications, allowing configuration changes, user management, and deployment of malicious code
- Lateral movement across cloud infrastructure, containers, or network segments using escalated service account permissions
- Data exfiltration by accessing databases, file systems, or API endpoints restricted to higher privilege levels
- Persistence establishment through creation of backdoor accounts or modification of system configurations
Real-World Examples
Kubernetes clusters have been compromised through kubelet API misconfigurations where read-only GET permissions on worker nodes could be escalated to remote code execution. Attackers upgraded HTTP connections to WebSockets to access the /exec endpoint, gaining shell access to all pods on the node. This affected over 69 Helm charts including widely-deployed monitoring tools like Prometheus, Grafana, and Datadog agents.
Windows Print Spooler vulnerabilities (PrintNightmare class) allowed authenticated users to execute arbitrary code with SYSTEM privileges by exploiting improper privilege checks in the print service. Attackers loaded malicious DLLs through carefully crafted print jobs, escalating from low-privilege user accounts to full domain administrator access.
Cloud metadata services have been exploited where SSRF vulnerabilities combined with over-permissioned IAM roles allowed attackers to retrieve temporary credentials with elevated permissions, pivoting from compromised web applications to broader cloud infrastructure access.
Mitigation
- Enforce deny-by-default access control where permissions must be explicitly granted rather than implicitly allowed
- Implement consistent authorization checks at every layer—API gateway, application logic, and data access—never relying on client-side or single-point validation
- Apply principle of least privilege with time-limited, scope-restricted permissions and just-in-time access for administrative functions
- Audit permission inheritance and role assignments regularly to identify overly permissive configurations or privilege creep
- Separate execution contexts using containers, sandboxes, or capability-based security to limit blast radius
- Deploy runtime monitoring for unusual privilege usage patterns and anomalous access to restricted resources
Recent CVEs (14429)
Improper permission controls in the HarmonyOS 6.1.0 clipboard module expose confidential data to local attackers. The flaw, classified under CWE-264 (Permissions, Privileges, and Access Controls), allows a local actor who can induce user interaction to read clipboard contents without appropriate authorization, impacting confidentiality only. No active exploitation is confirmed by CISA KEV, and SSVC rates exploitation status as none with no automation potential.
Permission control failure in HarmonyOS 6.1.0's device key management module allows a local, unprivileged actor to cause a complete availability loss on the vulnerable system. The flaw is classified under CWE-264 (Permissions, Privileges, and Access Controls), indicating improper enforcement of access restrictions within the key management subsystem. SSVC assessment confirms no known exploitation and non-automatable attack, but the local-no-privilege vector lowers the bar for any co-located attacker or malicious app on the device.
Improper privilege management in Bagisto's backend customer management endpoint allows authenticated low-privileged users to access customer behavior data beyond their authorization scope. The vulnerability affects all Bagisto releases from 2.4.0 through 2.4.4 at the /admin/customers endpoint via manipulation of the ID parameter. A publicly available proof-of-concept exploit exists on GitHub; the vendor has acknowledged the issue and confirmed partial internal remediation with remaining fixes planned for upcoming releases.
Improper privilege management in OpenBoxes up to 0.9.7 allows authenticated low-privileged users to escalate their roles by injecting unsanitized role parameters into the UserController's GORM data binding layer. The RoleInterceptor's needManager function additionally failed to enforce manager-level access on the user/show and user/edit endpoints, compounding the access control gap. A public proof-of-concept exploit is available; patched releases 0.9.8-hotfix1 and 0.9.8 are confirmed available from the vendor.
Memory corruption and denial of service in Zephyr RTOS's second-generation delayable work queue (kernel/work.c) arise because the documented safe-cancellation APIs-k_work_cancel_delayable_sync() and k_work_flush_delayable()-fail to block until an in-flight timeout handler completes before returning, allowing callers to free a k_work_delayable object that work_timeout() subsequently dereferences. The race exists exclusively in SMP builds; work_timeout() performs a use-after-free read of the freed object's flags and, if the memory slot has been reused so the bail check passes, a use-after-free write to wp->flags and a submit against a stale dw->queue pointer. No public exploit has been identified and the vulnerability is absent from the CISA KEV catalog; exploitation is probabilistic and gated on kernel-mode code execution with influence over subsystem work-item teardown timing.
Incorrect default file permissions on /etc/vsftpd.conf in TrendNet TEW-813DRU firmware 1.01b01 allow a remote low-privileged attacker to manipulate FTP server configuration, resulting in low-severity integrity compromise. The affected product is end-of-life and will receive no vendor patch. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS 4.0 score of 2.3 reflects the high attack complexity and minimal impact scope.
Improper privilege management in IBM i 7.3, 7.4, 7.5, and 7.6 enables a locally authenticated low-privileged attacker to read sensitive information or alter data beyond their authorized scope. The flaw is rooted in CWE-269 and carries a CVSS 3.1 score of 4.4 (Medium), reflecting its local-only attack vector and limited impact. No public exploit code and no confirmed active exploitation have been identified at time of analysis; a vendor-released patch is available.
Privilege management bypass in IBM i 7.3 through 7.6 permits remote low-privilege authenticated attackers to circumvent security restrictions and achieve limited unauthorized integrity modifications. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N) confirms network reachability but imposes high attack complexity and mandatory prior authentication, significantly constraining the realistic attack surface. No public exploit code and no CISA KEV listing were identified at time of analysis, consistent with the low base score and high complexity requirement.
Privilege escalation in Kibana Fleet allows authenticated low-privileged users to expand the write scope of Elasticsearch API keys issued to Elastic Agents beyond intended boundaries. By declaring extra data streams in an integration policy, an attacker causes Fleet to over-provision the API key given to enrolled agents, granting write-insert and index-mapping-extension privileges on indices outside the legitimate scope of that integration. No public exploit has been identified at time of analysis, and the flaw has not been listed in the CISA KEV catalog, but the network-accessible attack vector and low privilege requirement make this a meaningful integrity risk in multi-tenant or shared Elastic Stack deployments.
Privilege escalation in Gitea Open Source Git Server before 1.25.5 allows an attacker holding a leaked read-only API token to mint a runner registration token and register a malicious Actions runner against the instance. The root cause is that the runner registration-token endpoints - at the user, organization, repository, and admin levels - are classified as read-only by the API scope middleware solely because they use the HTTP GET method, despite creating a token if none exists. With a valid registration token, the attacker can register a self-hosted runner that executes CI/CD workflow jobs, gaining access to repository secrets and source code. No public exploit code has been identified at time of analysis, and the EPSS score of 0.16% (6th percentile) indicates low observed exploitation probability.
Insufficient access separation in HCL AION's shared storage architecture allows processes within the platform to access or modify files outside their intended scope. The CVSS vector (AV:L/AC:H/PR:H/UI:R/S:C) confirms exploitation requires local access with high privileges, high complexity conditions, and user interaction - all of which must align simultaneously. No public exploit code exists, and CISA has not added this to the Known Exploited Vulnerabilities catalog, placing this firmly in the medium-severity tier despite the scope change flag.
Privilege escalation in Teltonika Networks RUTOS (versions 7.07.1-7.24.1) and TSWOS (versions 1.03-1.10) allows an adjacent-network attacker with a low-privileged account to gain full administrative control of the device by exploiting unsafe argument handling in an execl() system call. The vulnerability enables complete integrity compromise of the affected router or switch operating system without requiring elevated privileges at entry. No public exploit code has been identified at time of analysis, and the flaw is not currently listed in the CISA KEV catalog.
Local privilege escalation in Palo Alto Networks GlobalProtect app (Windows, macOS, and Linux) allows any local non-administrative user to gain NT AUTHORITY\SYSTEM on Windows or root on macOS and Linux via CWE-426 (Untrusted Search Path), enabling arbitrary command execution at the highest OS privilege level. The vulnerability is confirmed by Palo Alto Networks in their own advisory and affects desktop platforms only - iOS, Android, and Chrome OS are explicitly excluded. No public exploit code or active exploitation is confirmed at time of analysis; the CVSS 4.0 score of 5.9 Medium reflects the local-only attack vector requirement.
Privilege escalation to root in Palo Alto Networks GlobalProtect App on macOS is enabled by a race condition exploitable by a locally authenticated, low-privileged user. The vulnerability is strictly macOS-specific - GlobalProtect on Linux, Windows, iOS, Android, and Chrome OS is explicitly not affected per vendor advisory. No public exploit has been identified at time of analysis, and the CVSS 4.0 score of 4.1 reflects the local, timing-dependent, and low-privilege-required nature of this attack.
Privilege escalation via an uncontrolled search path (CWE-427) in Palo Alto Networks Prisma Access Agent on Windows and macOS allows a local user to execute arbitrary code with elevated privileges. The vulnerability is platform-specific and explicitly does not affect the Linux, iOS, Android, or ChromeOS versions of the agent. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog; the CVSS 4.0 base score of 6.0 reflects the local-only attack vector, though the high confidentiality and integrity impact to the vulnerable system is significant for enterprise endpoint deployments.
Excessive Kubernetes RBAC privileges in the insights-client ServiceAccount within Red Hat Advanced Cluster Management for Kubernetes 2 expose all cluster Secrets to any attacker who compromises the pod or obtains its token. The ServiceAccount is bound to a ClusterRole granting cluster-wide get, list, and watch on all Secrets, far exceeding the single Secret the component actually requires. If the insights-client pod is breached, an attacker can read every Secret across the hub cluster - including managed-cluster kubeconfigs - enabling lateral movement to downstream managed clusters. No public exploit code has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Security restriction bypass in IBM i 7.3 through 7.6 allows remote authenticated attackers to circumvent access controls by supplying a crafted user profile name that passes improper validation logic. The vulnerability is tagged as a privilege escalation path, meaning successful exploitation likely enables access to resources or operations beyond the attacker's authorized scope. No public exploit code or CISA KEV listing is present at time of analysis, but a vendor patch is available and should be prioritized given the high confidentiality impact indicated by CVSS.
In the Linux kernel, the following vulnerability has been resolved: ovl: check access to copy_file_range source with src mounter creds Commit 5dae222a5ff0c ("vfs: allow copy_file_range to copy across devices") allowed filesystems that implement the copy_file_range() f_op to decide if they want to access cross-sb copy from/to the same fs type. The same commit added checks to verify same sb copy for filesystems that implement ->copy_file_range() and do not support cross-sb copy at the time, namely, to ceph, fuse and nfs. The two remaining fs which implement ->copy_file_range(), cifs and overlayfs started to support cross-sb copy from this time. While overlayfs does support cross-sb copy when the two underlying files are on the same base fs, the copy operation on the two real files from two different overalyfs filesystems is performed with the mounter creds of the destination overlayfs and the read permission access hook for the source file was called with the wrong creds. This could cause either deny of access to copy which would otherwise be allowed (e.g. with splice) or allow read access to file which would otherwise be denied. Fix the latter case by explicitly verifying read access to source file with the source overlayfs mounter creds. The former case remains a quirk of cross-sb overlayfs copy, but userspace could fall back to regular copy so no harm done.
Privilege boundary enforcement failure in MongoDB Server allows an authenticated user holding only database-scoped privileges to modify diagnostic logging parameters at the server-wide level. Affected versions span MongoDB 7.0 (before 7.0.40), 8.0 (before 8.0.29), and 8.3 (before 8.3.8). An attacker with low-privilege credentials can either suppress server-wide diagnostic logging to obscure unauthorized activity or flood logs to degrade operational monitoring - effectively undermining the integrity of the audit and observability layer. No public exploit code exists and CISA has not added this to the KEV catalog.
Privilege escalation in Adobe Commerce and Magento Open Source exposes restricted resources to authenticated high-privilege users through a flawed authorization check (CWE-863). Affected products span the full 2.4.x series of Adobe Commerce and Magento Open Source, plus the 1.3.x-1.5.x Adobe Commerce B2B extension. No public exploits are known, CISA SSVC rates exploitation as none, and vendor-released August 2026 patches are available across all affected release lines per advisory APSB26-92.
Firmware improper input validation in Intel Xeon processors enables a highly privileged local adversary operating within System Management Mode (SMM) or startup code context to alter the integrity of subsequent system components. The CVSS 4.0 vector confirms local-only access (AV:L), high complexity (AC:H), presence-required attack conditions (AT:P), and a high-privilege prerequisite (PR:H), with zero confidentiality or availability impact - only downstream integrity degradation (SI:H). No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV, placing real-world exploitation risk firmly in the advanced persistent threat category rather than opportunistic attack.
SSRF with privilege escalation affects Adobe's Content Credentials SDK and CLI toolchain, enabling a network-based attacker to induce the victim's client to issue server-side requests to unintended internal or external targets. Exploitation requires user interaction - a victim must visit a crafted URL or engage with a compromised web page - but the CVSS scope change (S:C) indicates the vulnerability can reach beyond the directly vulnerable component to affect other systems or services. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Binary hijacking is possible on Windows machines running AMD Vitis Unified due to weak filesystem permissions on the installation directory. A low-privileged local user can write arbitrary executables into paths traversed by higher-privileged processes, causing those processes to load attacker-controlled code when triggered by an interactive user. The CVSS 4.0 score of 1.0 reflects significant limiting prerequisites: local access, low-privilege credentials, specific attack preconditions, and required user interaction are all mandatory for exploitation. No public exploit has been identified at time of analysis.
Privilege escalation in AMD Vitis Unified on Windows enables a low-privileged local user to plant malicious code in the installation directory due to misconfigured filesystem permissions, potentially leading to arbitrary code execution under a more privileged context. Affected installations are the Vitis Unified Installer for FPGAs and Adaptive SoCs on Windows, patched in release 2026.1. No public exploit code and no active exploitation have been identified at time of analysis; CISA SSVC rates exploitation as none and the attack as non-automatable.
Privilege escalation in Intel(R) Transfer Learning Tool before version v0.7 stems from a protection mechanism failure (CWE-693) within the Ring 3 user application layer, enabling unauthenticated remote attackers to elevate privileges under specific attack conditions. The flaw affects confidentiality, integrity, and availability at a low severity each, with no subsequent system-level impact confirmed. No public exploit code or CISA KEV listing exists at time of analysis, and Intel has published advisory INTEL-SA-01499 addressing this issue.
Privilege escalation in Intel Processors operating within Ring 0 environments - kernel, hypervisor, and bare-metal OS - allows an authorized attacker already holding high-privilege access to cross isolation boundaries and achieve high confidentiality and integrity impact on subsequent systems such as hypervisors or co-located virtual machines. The CVSS 4.0 vector (AV:L/AC:H/AT:P/PR:H/SC:H/SI:H) confirms the attack is local, high-complexity, and gated behind existing privileged access plus special internal knowledge of processor internals, significantly limiting the exploitable population. No public exploit code and no CISA KEV listing exist at time of analysis, making current real-world risk primarily theoretical but relevant to hardened multi-tenant and virtualized datacenter environments.
Deserialization of untrusted data in Intel Extension for PyTorch (IPEX) versions before 2.8.0 enables local privilege escalation when a victim user opens a maliciously crafted serialized artifact within an IPEX-dependent application. The vulnerability operates at Ring 3 (user-space) and yields low confidentiality, integrity, and availability impact with no subsequent system-level compromise. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Privilege escalation in Intel's Hardware-Aware-Automated-MachineLearning (NA) software before commit 45cd723 stems from an uncontrolled search path element (CWE-427) in its Ring 3 user-space application layer. An unprivileged local attacker who can write to a directory within the application's library or executable search path can plant a malicious artifact; when a high-privileged user subsequently runs the AutoML tool, the application loads the attacker-controlled file and executes code at the elevated privilege level. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, though the CVSS 4.0 score of 5.4 (Medium) reflects the attack requirements and required user interaction that constrain real-world exploitation.
Privilege escalation in Intel Performance Counter Monitor (PCM) before version tag 202604 allows a local authenticated attacker to gain elevated privileges via an untrusted search path (CWE-426) within Ring 3 user-space applications. The attack requires high complexity and passive interaction from a privileged user, producing full high-impact confidentiality, integrity, and availability compromise of the vulnerable system. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Local privilege escalation via uncontrolled search path (DLL/binary planting) affects Intel's Approximate Bayesian Inference Framework prior to commit #484c949. An attacker operating at Ring 3 (user application space) with high privileges who can manipulate the search path can cause a co-located privileged user to load a malicious binary, resulting in full compromise of confidentiality, integrity, and availability on the vulnerable system. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Path traversal in Intel's gaudi-container-runtime before version 1.24.0 enables privilege escalation for locally authenticated users running workloads on Intel Gaudi AI accelerator hardware. The CWE-22 path traversal flaw resides in the Ring 3 userspace component of the runtime, allowing a low-privileged attacker to traverse directory boundaries and potentially gain elevated access with full confidentiality, integrity, and availability impact on the vulnerable system. No public exploit code or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 score of 5.4 reflects the local attack vector, required attack preconditions (AT:P), and passive user interaction requirement, which substantially reduce real-world exploitability despite the high per-system impact.
Privilege escalation in Intel Xeon 6 processors arises from improper handling of overlapping protected memory ranges when Intel Trust Domain Extensions (TDX) operate within System Management Mode (SMM). An adversary who has already achieved SMM-level access and combines that foothold with a high-complexity, knowledge-intensive attack can break the isolation guarantees that TDX is designed to enforce, achieving unauthorized reads and writes of confidential memory. No public exploit code and no CISA KEV listing are associated with this issue at time of analysis, but the high confidentiality and integrity impact to the vulnerable system makes it significant for confidential-computing deployments.
Privilege escalation in Intel Workload Services Framework software affects the Ring 3 user-application layer, where a protection mechanism failure (CWE-693) allows an unprivileged process to gain elevated privileges when a concurrently active privileged user provides passive interaction. The attack is local, requires attack prerequisites to be met (AT:P per CVSS 4.0), and achieves full compromise of the vulnerable system's confidentiality, integrity, and availability. No public exploit or CISA KEV listing has been identified at time of analysis; this is a vendor-disclosed advisory via INTEL-SA-01467.
Privilege escalation in Intel's LLM-on-Ray framework before version 1.0 stems from a protection mechanism failure (CWE-693) within Ring 3 user-space components, allowing an attacker with high-privileged user access to escalate privileges on the local system. The attack requires local access, passive user interaction from a privileged user, and specific attack requirements (AT:P), but results in high confidentiality, integrity, and availability impact on the vulnerable system with no subsequent system scope change. No public exploit code has been identified at time of analysis, and it is not listed in the CISA KEV catalog.
Privilege escalation in EquiTriton before commit f5ddbb5 arises from an uncontrolled search path element (CWE-427) within Ring 3 user-mode application components, allowing a local attacker operating under a high-privilege user context to substitute a malicious binary or library in a search path directory that EquiTriton resolves ahead of its legitimate target. Successful exploitation yields full confidentiality, integrity, and availability compromise of the vulnerable system while leaving downstream systems unaffected. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog at time of analysis; Intel disclosed the issue under advisory INTEL-SA-01473.
Privilege escalation in Intel(R) oneCCL Bindings for PyTorch before v2.8.0 stems from a protection mechanism failure (CWE-693) in Ring 3 user application space, enabling a local adversary - operating in conjunction with a high-privilege user through passive interaction - to escalate privileges with full confidentiality, integrity, and availability impact on the vulnerable system. The CVSS 4.0 score of 5.4 reflects meaningful exploitation constraints: specific attack requirements must be present (AT:P), high privileges are already required (PR:H), and passive interaction from a privileged user is needed (UI:P). No public exploit code or CISA KEV active exploitation listing has been identified at time of analysis.
Privilege escalation in Intel AI Reference Models before v3.4.1 stems from a protection mechanism failure (CWE-693) within Ring 3 user-space applications, allowing unprivileged software to gain elevated access when a privileged user is passively present under specific deployment conditions. The vulnerability carries full confidentiality, integrity, and availability impact on the vulnerable system, though scope is contained with no subsequent-system impact. No public exploit has been identified at time of analysis; Intel has issued a fix in version v3.4.1 per advisory INTEL-SA-01432.
Privilege escalation affects Intel's LLM Library for PyTorch operating within Ring 3 (user application space) due to a protection mechanism failure (CWE-693). An adversary with access to an unprivileged software context, combined with the presence of a privileged user and passive user interaction, can exploit this flaw locally to gain elevated privileges with high impact on confidentiality, integrity, and availability. No public exploit code or CISA KEV listing exists at time of analysis, and the CVSS 4.0 score of 5.4 reflects the restrictive local access and high-privilege prerequisites that limit real-world exploitability.
Privilege escalation in Intel Neural Compressor software before v3.7 stems from improper input validation within Ring 3 (user application space), allowing a locally authenticated low-privileged user to elevate privileges on the affected host. The CVSS 4.0 vector confirms local access with low complexity, no special attack requirements, and no user interaction needed - meaning exploitation is straightforward once local access is established. No public exploit code or CISA KEV listing has been identified at time of analysis, and impact is bounded to the vulnerable system with no lateral scope change.
Privilege escalation in Intel Neural Compressor software before v3.6 stems from a protection mechanism failure (CWE-693) within the Ring 3 user-application layer. A local attacker operating with high privileges, in conjunction with specific attack requirements and passive user interaction, can exploit this flaw to elevate privileges with high confidentiality, integrity, and availability impact on the vulnerable system. Intel has issued advisory INTEL-SA-01454 and released v3.6 as the remediated version; no public exploit code or active exploitation has been identified at time of analysis.
Privilege escalation in Intel AI Containers before v0.4.0 exposes a protection mechanism failure (CWE-693) within the Ring 3 user application layer, enabling a local attacker already holding high privileges to further escalate privileges with full confidentiality, integrity, and availability impact on the vulnerable system. Exploitation requires passive user interaction and specific attack conditions (AT:P), substantially limiting the realistic attack population to multi-tenant AI container deployments where privileged users must be constrained. No public exploit code has been identified and this vulnerability does not appear in CISA KEV at time of analysis.
Local privilege escalation in Intel PROSet/Wireless WiFi Software for Windows allows unprivileged local code execution by exploiting improper authentication within the device driver layer. An attacker with only local access and no required privileges can bypass authentication checks in the Ring-2 driver tier, ultimately achieving code execution that results in high confidentiality impact on the broader host system alongside low integrity and availability impacts. No public exploit has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Local privilege escalation in Intel Battery Life Diagnostic Tool Software before version 2.9.0 stems from an untrusted search path (CWE-426), enabling a malicious binary or DLL to be loaded in place of a legitimate dependency when the tool executes. An authenticated local attacker with write access to a directory in the application's search path can achieve full system compromise (confidentiality, integrity, and availability all rated High on the vulnerable system) by waiting for a legitimate user to passively trigger the tool. Intel has released a fix in version 2.9.0 via advisory INTEL-SA-01453; no public exploit or CISA KEV listing is present at time of analysis.
Privilege escalation in Intel's Cluster Management Toolkit for Kubernetes (CMK) before v0.8.5 allows a privileged local adversary to fully compromise the confidentiality, integrity, and availability of the affected system by exploiting a protection mechanism failure (CWE-693) within the Ring 3 user-application boundary. Exploitation requires a pre-established privileged local account, specific attack prerequisites (AT:P), and the occurrence of passive user interaction - a combination that substantially limits the exploitable population but results in complete system-level impact when conditions align. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Privilege escalation in Intel TDX Guest software before version 0.3.1 stems from an incorrect comparison (CWE-697) within Ring 3 user application space, exploitable by a local attacker who already holds high system privileges. Impact is limited - low confidentiality, integrity, and availability degradation on the vulnerable guest system with no subsequent system impact - aligning with the CVSS 4.0 score of 4.6. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; Intel has released a fix at version 0.3.1 via advisory INTEL-SA-01462.
Privilege escalation in Intel TDX Guest software before version 0.3.1 stems from an incorrect calculation (CWE-682) within Ring 3 user application code, enabling a local, high-privilege adversary to elevate privileges within a Trust Domain. The CVSS 4.0 vector confirms local access with high privileges required and low C/I/A impact on the vulnerable system, with no subsequent-system (host/hypervisor) impact. No public exploit exists and the vulnerability is absent from CISA KEV, placing real-world risk squarely in multi-tenant confidential computing scenarios where intra-guest privilege containment is a security objective.
Privilege escalation in Intel processor microcode stems from improper handling of overlap between protected memory ranges at the Ring 0 hypervisor privilege level, tracked as CVE-2026-20760 and EUVD-2026-56489. Exploitation requires local, low-privilege access to a system running an affected Intel processor, allowing an authorized adversary to escalate privileges or disrupt hypervisor availability without user interaction. Intel has published advisory INTEL-SA-01441 covering this issue; no active exploitation (CISA KEV) or public proof-of-concept has been identified at time of analysis, though the hypervisor-level attack surface warrants priority treatment in virtualized environments.
Privilege escalation in Intel's LLM Scaler software exposes systems to full compromise of confidentiality, integrity, and availability within the affected host. The flaw stems from a protection mechanism failure (CWE-693) operating in Ring 3 (user-space applications), where an unprivileged software component can leverage a co-present privileged user session to bypass access controls and elevate privileges. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog; however, the high impact triad (C:H/I:H/A:H) warrants prompt patching on any system running Intel's LLM Scaler where privileged users operate.
Local privilege escalation and code execution in Intel PROSet/Wireless WiFi Software for Windows arises from an information disclosure flaw (CWE-200) within the Ring 2 device driver layer, exploitable by an unprivileged local user without authentication or user interaction. The vulnerable system itself suffers only low confidentiality impact, but a scope change into the driver subsystem produces high subsequent-system confidentiality impact alongside low integrity and availability impacts - consistent with a privilege escalation chain from user space into driver-controlled memory. No public exploit has been identified at time of analysis and the vulnerability has not been listed in the CISA KEV catalog.
Privilege escalation in Intel Extension for TensorFlow software before version 2.15.0.3 stems from a protection mechanism failure (CWE-693) operating at Ring 3 - the CPU user-application privilege boundary. A system software adversary holding high privileges can exploit this failure under specific local attack conditions with passive user interaction to achieve full confidentiality, integrity, and availability compromise of the vulnerable system. No active exploitation has been confirmed by CISA KEV and no public exploit code has been identified at time of analysis.
Privilege escalation in Intel Xeon processor firmware stems from an always-incorrect control flow implementation (CWE-670) that allows a privileged system software adversary to escalate privileges under high-complexity local attack conditions. Exploitation yields subsequent-system impacts - high confidentiality and high integrity compromise - while leaving the vulnerable system itself unimpacted, consistent with a scope change into a higher-privilege domain such as an OS kernel or hypervisor. No active exploitation is confirmed by CISA KEV, and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in ElkArte Forum 2.0 Beta 1 enables any registered member to persist malicious JavaScript in the cust_blurb and cust_locate profile fields, which render unescaped when administrators view affected profiles. The scope-changing nature of the flaw (CVSS S:C) means the payload executes within an administrator's browser session, creating a realistic path to session hijacking or privilege escalation. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low barrier to exploitation - any registered account suffices - makes this a meaningful risk for forums with open registration.
Privilege escalation in the Axis Camera Application Platform (ACAP) framework on Axis OS exploits a Time-of-Check to Time-of-Use (TOCTOU) race condition during ACAP application installation. Exploitation is gated behind two explicit non-default conditions: the target device must have unsigned ACAP application installation enabled, and a high-privileged victim must be socially engineered into installing a malicious package. No public exploit code has been identified at time of analysis, and the vendor-assigned CVSS score of 5.1 (Medium) accurately reflects the high attack complexity and privilege prerequisites that substantially constrain real-world impact.
Privilege escalation in Axis OS affects all Axis network devices where unsigned ACAP application installation is permitted, allowing an attacker who tricks an administrator into installing a malicious ACAP app to gain elevated privileges on the device. The vulnerability stems from missing input validation in an ACAP configuration file (CWE-1287), enabling crafted configuration values to bypass intended privilege boundaries. No public exploit code has been identified at time of analysis, and the CVE is not listed in the CISA KEV catalog.
Privilege escalation in the Axis Camera Application Platform (ACAP) framework within Axis OS exploits a Time-of-Check to Time-of-Use race condition during application installation, allowing a malicious ACAP package to bypass integrity verification and gain elevated privileges on the device. Affected are Axis network cameras and IoT surveillance devices running all versions of Axis OS where unsigned ACAP application installation has been explicitly enabled. No public exploit code exists and the vulnerability is not listed in CISA KEV; the combination of high attack complexity, administrative victim interaction, and a non-default prerequisite configuration materially limits real-world risk.
Privilege escalation in SAP S/4HANA's Reprocess Bank Statement Items component allows authenticated users to invoke processing rules that have not been explicitly shared with them, circumventing intended access controls. Affected versions span S4CORE releases 104 through 109, covering a broad swath of actively supported SAP S/4HANA deployments. The impact is confined to low-severity information disclosure - unauthorized rule access reveals restricted bank statement logic - with no integrity or availability consequences; no public exploit or active exploitation has been identified at the time of analysis.
CyberChef's client-side pretty-recipe parser freezes victim browser tabs via a crafted URL fragment containing large numbers of unmatched quote characters, triggering catastrophic backtracking in a synchronous global regular expression. Any user of CyberChef prior to 11.3.0 who opens a malicious #recipe= URL - whether shared in phishing, chat, or embedded in a page - is subject to a temporary denial-of-service condition. No code execution, data exfiltration, or privilege escalation is possible; impact is confined to browser tab availability. No public exploit identified at time of analysis, and this vulnerability is not listed in CISA KEV.
Local privilege escalation in systemd-homed enables a low-privileged, locally logged-in user whose account is managed by homed to be arbitrarily added to system groups they are not authorized to join. Successful exploitation, constrained by high attack complexity and a required user interaction step per the CVSS vector, can yield full confidentiality, integrity, and availability compromise of the local system. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in the CISA KEV catalog.
Privilege escalation in Red Hat Advanced Cluster Security 4 (StackRox Central) allows authenticated OIDC token holders to gain unauthorized role assignments through unanchored regular expression matching in the Machine-to-Machine token exchange subsystem. When administrators configure M2M role mappings, RHACS matches incoming OIDC claim values against configured patterns without regex anchors, meaning an attacker whose claim value is a superstring of a mapped pattern - for example, 'superadmin' matching a pattern intended only for 'admin' - receives elevated roles unintentionally. No public exploit code or active exploitation has been identified at this time; the CVSS AC:H rating reflects a genuine complexity barrier requiring attacker knowledge of the target's role mapping configuration.
Traefik's BasicAuth middleware in versions 3.6.11-3.6.24 and 3.7.0-3.7.9 permits an authenticated low-privilege user to forge arbitrary backend identities via a singleflight key collision race condition. By concatenating their known valid password with a retrieved stored bcrypt hash, an attacker crafts a singleflight deduplication key identical to a legitimate in-flight request's key; the middleware returns the legitimate request's successful authentication result to the attacker's request, then propagates the attacker's chosen unconfigured username to the backend as a trusted identity. A fully working proof-of-concept achieving 25-of-25 successful identity forgeries under default bcrypt cost is publicly available in the GitHub security advisory; no CISA KEV listing has been identified at time of analysis.
Privilege escalation in openclaw-cn (all versions up to 0.2.1) allows a remote attacker with low-level authentication to bypass the `isApprovedElevatedSender` privilege check in the auto-reply module and assume elevated sender permissions. A publicly disclosed proof-of-concept exploit exists on GitHub issue #564, and the project maintainer has not responded to the responsible disclosure report. No CISA KEV listing exists, but the low attack complexity combined with POC availability makes this a credible risk for any active deployment of the affected application.
Improper privilege management in NanoClaw (versions up to 2.0.64) allows authenticated remote attackers to abuse the `handleCreateAgent` function within the agent-to-agent creation module to escalate privileges beyond their authorization level. A public proof-of-concept exploit is available via a GitHub issue report, and the vendor has not responded to the coordinated disclosure, leaving deployments unpatched. No public exploit identified as actively exploited in CISA KEV, but the public POC and absence of a vendor patch materially elevate near-term exploitation risk.
Denial-of-service in Cisco IOS XE Software's web-based management interface (WebUI) allows an authenticated remote attacker holding only low-privilege credentials to render the management interface unresponsive by sending crafted input that bypasses input validation. The vulnerability spans an exceptionally broad version footprint - from 16.9.x through the 26.x release train - making patching scope significant for organizations running Cisco enterprise routing and switching infrastructure. No public exploit has been identified at time of analysis and this CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, placing real-world urgency below its broad scope might suggest.
Stored cross-site scripting in Ghost CMS feature image captions enables any authenticated staff user to inject unsanitized HTML into the post revision history modal, hijacking the Ghost Admin session of another staff or administrator user who views that revision. Affects Ghost npm package versions v4.9.0 through v6.54.0. No public exploit identified at time of analysis and not listed in CISA KEV, but the privilege escalation potential - a lower-privileged staff member compromising a full administrator session - makes this higher-impact than the CVSS 4.3 score implies for multi-tenant or shared Ghost Admin environments.
CVE-2026-70443 is part of the Jenkins August 5, 2026 batch security advisory covering Jenkins core and multiple plugins. The provided source data does not include the specific vulnerability description for CVE-2026-70443 - the advisory text is truncated before reaching this CVE identifier (described CVEs end around CVE-2026-70435). The full advisory at https://www.jenkins.io/security/advisory/2026-08-05/ contains authoritative details. No active exploitation is confirmed (not listed in CISA KEV), and no EPSS or CVSS data was provided in the source intelligence.
Keycloak's LDAP storage provider allows delegated administrators to bypass configured search boundaries by supplying a crafted Distinguished Name (DN), exposing account information from unauthorized directory subtrees and triggering unintended user imports into Keycloak local storage. Affected deployments include Red Hat Build of Keycloak, Red Hat Single Sign-On 7, Red Hat Data Grid 8, and the JBoss EAP Expansion Pack. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; exploitation is constrained to authenticated delegated administrators with access to the LDAP federation interface.
GNU tar's incremental restore path contains a TOCTOU race condition in dumpdir 'X' rename handling, allowing a local attacker with write access to a backed-up directory to redirect file operations outside the intended extraction root during a privileged restore. Successful exploitation can result in arbitrary file creation, rename, or overwrite - enabling privilege escalation on systems running Red Hat Enterprise Linux 6 through 10 and Red Hat Hardened Images. No public exploit is identified at time of analysis, and no CISA KEV listing exists; the CVSS score of 4.4 reflects the constrained attack prerequisites including a required race window and administrator-initiated restore.
Privilege escalation to NT AUTHORITY\SYSTEM is achievable by any local, unprivileged user via Wellbia XIGNCODE3's kernel driver xhunter2.sys version 2026.6.1.192, due to missing access control on the IRP_MJ_WRITE command interface. Beyond SYSTEM-level execution, the flaw enables extraction of credentials from PPL-protected lsass.exe and termination of PPL-protected security processes such as EDR/AV agents, effectively disabling host defenses. No active exploitation is confirmed by CISA KEV, though the primary reference is a researcher blog post (blacksnufkin's 'Hunting the Hunter II') that strongly suggests PoC-grade research material exists.
Privilege escalation in MediaTek's geniezone component affects ten specific chipset models (MT8792, MT8883, MT8873, MT8893, MT8768, MT8796, MT8799, MT6991, MT8791T, MT8910) due to a missing permission check classified under CWE-1287. An attacker who has already obtained System-level privileges on an affected device can exploit this flaw to escalate further - potentially reaching kernel or TEE-adjacent privilege boundaries - without requiring any user interaction. No public exploit code exists and no active exploitation has been confirmed (EPSS 0.13%, 3rd percentile), positioning this as a chaining vulnerability relevant to targeted attacks rather than opportunistic mass exploitation.
Incorrect error handling in the MediaTek imgsensor (camera/image sensor) kernel driver across multiple MediaTek chipsets allows a local attacker who already holds System-level privilege to crash an application and potentially escalate to a higher privilege tier. Affected chipsets span eleven models including MT8395, MT8799, MT6895, MT6991, and MT8910, covering a broad range of mid-to-high-end Android-targeted SoCs. No public exploit is identified at time of analysis and the EPSS score of 0.13% (3rd percentile) reflects low observed exploitation interest, though the post-exploitation utility of this flaw makes it relevant in chained attack scenarios.
Out-of-bounds write in MediaTek's HFRP component on the MT6993 chipset enables local privilege escalation beyond System-level access, confirmed via MediaTek's August 2026 security bulletin. The flaw stems from a missing bounds check (CWE-787), requiring an attacker who has already achieved System privilege to trigger further escalation - a post-compromise lateral movement primitive rather than an initial access vector. No public exploit code and no KEV listing have been identified; EPSS sits at the 3rd percentile, consistent with SSVC's 'exploitation: none' finding.
Out-of-bounds write in MediaTek's GeniZone Trusted Execution Environment (TEE) component enables local privilege escalation across 14 distinct MediaTek chipsets. An attacker who has already achieved System-level privilege on an affected Android device can exploit a missing bounds check to write outside intended memory boundaries within the secure enclave, gaining confidentiality and integrity access beyond what System privilege normally permits. No public exploit has been identified at time of analysis, and the EPSS score of 0.13% (3rd percentile) reflects low observed exploitation probability; however, the pre-existing System privilege prerequisite substantially narrows the realistic attack surface.
Out-of-bounds write in MediaTek's GenieZone hypervisor component enables local privilege escalation beyond System-level access on a wide range of MediaTek mobile chipsets. Exploitation is constrained to attackers who have already obtained System privileges, making this a secondary step in a multi-stage attack chain rather than an initial foothold technique. No public exploit code exists and EPSS of 0.13% (3rd percentile) confirms negligible real-world exploitation activity; no CISA KEV listing at time of analysis.
Out-of-bounds write in the MediaTek display driver allows a local attacker who has already obtained System-level privilege to further escalate privileges on affected Android devices. The vulnerability stems from a missing bounds check (CWE-787) in display subsystem code across at least ten MediaTek chipsets, including MT8910, MT8188, MT8799, and MT6991 among others. No public exploit or active exploitation (CISA KEV) is identified at time of analysis; EPSS score of 0.14% (4th percentile) and SSVC exploitation rating of 'none' both confirm this remains an undemonstrated threat as of the August 2026 advisory.
Local privilege escalation in MediaTek's display subsystem affects 17 chipset variants used in Android devices, allowing an attacker who has already obtained System-level privilege to exploit a missing bounds check (CWE-787) and write out of bounds in display memory, achieving high confidentiality and integrity impact. The CVSS vector (PR:H/AV:L) confirms this is not an initial-access vector - it is a post-compromise escalation step requiring pre-existing System privilege. No public exploit has been identified, EPSS stands at 0.14% (4th percentile), and the vulnerability is not listed in CISA KEV, consistent with SSVC's exploitation status of 'none.'
Local privilege escalation in the MediaTek display subsystem affects 17 distinct chipsets including MT6991, MT8768, MT8678, and MT8799, among others. An attacker who has already obtained System-level privilege can exploit a race condition (CWE-367) in the display driver to achieve further privilege escalation, resulting in high confidentiality and integrity impact on the device. No public exploit has been identified at time of analysis, and the EPSS score of 0.11% (2nd percentile) reflects minimal observed exploitation probability; MediaTek has released patch ALPS11019183 via its August 2026 Product Security Bulletin.
Local privilege escalation in the MediaTek display driver allows an attacker who already holds System-level privileges to further escalate via a use-after-free memory corruption condition, potentially achieving kernel-level access. Seventeen MediaTek SoC models used across Android devices are affected, disclosed in MediaTek's August 2026 security bulletin with Patch ID ALPS11019722. No public exploit code exists and EPSS at 0.14% (4th percentile) confirms negligible current exploitation probability; this vulnerability is not in the CISA KEV catalog.
Privilege escalation in MediaTek's trusted_mem subsystem affects nine specific chipset models (MT8365, MT8186, MT8188, MT8195, MT8370, MT8371, MT8390, MT8391, MT8395) through a write-what-where condition caused by improper input validation. An attacker who has already obtained System-level privilege can leverage this flaw to escalate further, potentially compromising the trusted memory environment. No public exploit code has been identified and EPSS places exploitation probability at 0.14% (4th percentile), indicating this is currently a low-exploitation-pressure issue despite its local privilege escalation potential.
Local privilege escalation in MediaTek's apusys AI Processing Unit subsystem on MT8196 and MT8366 chipsets allows an attacker already holding System-level privileges to further escalate by exploiting a confused deputy flaw - likely realized through an out-of-bounds write (CWE-787) - achieving high confidentiality and integrity impact on the vulnerable system. Disclosed by MediaTek in their August 2026 Product Security Bulletin, a vendor patch is available under Patch ID AUTO00833804. No public exploit has been identified at time of analysis, and an EPSS of 0.14% at the 4th percentile reflects negligible probability of widespread exploitation.
Privilege escalation in MediaTek's AI Processing Unit Subsystem (apusys) driver allows a local attacker already holding System-level privileges on devices equipped with MT8366, MT8196, or MT8195 chipsets to escalate further, achieving high-impact access to confidential data and system integrity. The root cause is a missing bounds check (CWE-749) in an exposed driver function, patched under MediaTek ID AUTO00837766 in the August 2026 security bulletin. No public exploit code has been identified, and the EPSS score of 0.14% (4th percentile) confirms very low current exploitation probability.
Secure boot heap buffer overflow in MediaTek chipsets MT2737, MT6880, MT6890, and MT6990 enables local privilege escalation by an attacker with physical device access. The vulnerability exists at the pre-OS firmware layer, where a write beyond allocated heap boundaries can corrupt boot verification logic and permit execution of unsigned or attacker-controlled code. No active exploitation has been confirmed - the vulnerability is absent from CISA KEV, and the EPSS score of 0.16% (6th percentile) is consistent with the hard physical access prerequisite sharply limiting opportunistic exploitation.
Out-of-bounds write in the MediaTek HEVC video decoder enables further privilege escalation on devices running MT6761, MT8766, and MT8768 chipsets. The flaw, rooted in an integer overflow during HEVC bitstream processing, can be triggered without user interaction but only by an actor who already holds System-level privilege on the device. No public exploit code has been identified at time of analysis, and EPSS sits at 0.18% (8th percentile), consistent with SSVC's 'Exploitation: none' assessment - though SSVC rates Technical Impact as total, reflecting the severity of what a successful second-stage exploit could achieve.
Privilege escalation in Capsule (Kubernetes multi-tenancy framework) versions 0.13.0-0.13.7 allows authenticated Tenant Owners to break out of tenant isolation and create cluster-scoped Kubernetes resources - including ClusterRole, ClusterRoleBinding, and ValidatingWebhookConfiguration - through the cluster-admin controller client. This is an incomplete fix of CVE-2026-22872: the TenantResource RawItems and Generators code paths (handleRawItem, handleGeneratorItem) were never updated to enforce the same cluster-scoped resource rejection guards applied to NamespacedItems. No public exploit or CISA KEV listing has been identified at time of analysis; vendor-released patch v0.13.8 is available.
Privilege escalation in Google Chrome Enterprise on macOS allows a local attacker with physical device access to bypass enterprise policy controls and gain elevated privileges. Affected are all Chrome versions prior to 151.0.7922.72 in managed Enterprise deployments on Mac. The attack requires physical presence at the target device, substantially limiting the threat surface, though the confidentiality, integrity, and availability impact is rated high once exploited. No public exploit identified at time of analysis.
Privilege escalation in Quick.Cart via hard-coded, plaintext admin credentials stored in a configuration file allows local attackers with file system access to retrieve authentication details and gain administrative control. The vendor considers exploitation unlikely and has not released a fix; all versions are believed vulnerable, with version 6.7 confirmed. No public exploit or active exploitation has been reported.
Local information disclosure in accountsservice on Red Hat Enterprise Linux allows systemd-homed users to read arbitrary files via the SetIconFile handler. A proof-of-concept exists, but exploitation requires a local account managed by systemd-homed, limiting impact
Privilege escalation in OWASP DefectDojo 2.59.0 exposes authenticated non-superusers to flip the is_staff flag on any account - including their own - through the UserSerializer in the v2 API, bypassing DefectDojo's role-based access controls and granting Django admin access. Version 2.59.0 was an accidental release and has been pulled; patched releases 2.58.3 and 3.0.0 exist. Publicly available exploit code is acknowledged (CVSS 4.0 E:P), and no special preconditions beyond a valid authenticated session with delegated user-management permissions are required.
Symlink following in HuggingFace Datasets through version 5.00 allows local low-privileged attackers to redirect archive extraction to arbitrary filesystem locations by pre-planting symlinks at predictable output paths in the shared cache directory. When a higher-privileged user or automated service subsequently triggers Extractor.extract(), the library writes archive contents through the attacker-controlled symlink, enabling overwrite of sensitive system files and potential privilege escalation or code execution. A publicly available exploit exists and an upstream fix is available via commit ad2d853, though no confirmed tagged release version has been independently verified.
Privilege escalation in Hikvision DS-2CD series IP cameras allows an SSH-authenticated attacker to gain full administrative control of the device by exploiting incorrect permission allocation in the device firmware. The vulnerability requires prior SSH authentication, making it an insider or credential-theft-dependent threat rather than an unauthenticated remote attack. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but successful exploitation delivers complete confidentiality, integrity, and availability compromise of the affected camera.
Oracle Lease and Finance Management within Oracle E-Business Suite (versions 12.2.3-12.2.15) exposes its Lease Authoring component to exploitation by low-privileged, network-accessible attackers over HTTP, resulting in partial confidentiality loss, unauthorized data manipulation, and a partial denial of service. The vulnerability is classified as easily exploitable with no user interaction required, making it accessible to any authenticated low-privilege user who can reach the application over the network. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Quick Facts
- Typical Severity
- HIGH
- Category
- auth
- Total CVEs
- 14429