Privilege Escalation
Monthly
Local code execution on iOS and iPadOS (before 26.7 and the 27 line), macOS Golden Gate (before 27), and visionOS (before 27) can let an attacker-controlled app process overwrite restricted files, breaking file-system integrity protections. The issue is an improper privilege-management and permissions-validation weakness (CWE-269) scored 6.2 with a local-only vector (AV:L/AC:L/PR:N/UI:N), so it is unauthenticated once code is running but cannot be reached remotely - a malicious or sideloaded app must first execute on the device. No public exploit identified at time of analysis and no KEV confirmation; Apple has released vendor patches in iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, macOS Golden Gate 27, and visionOS 27.
Local privilege escalation in Red Hat rhc's rhc-canonical-facts.service lets an attacker who has already compromised the privileged yggdrasil service account pre-plant a symbolic link so the root-run unit follows it and changes ownership of an arbitrary file, enabling escalation to root. The flaw is CWE-59 link following and affects rhc installations on Red Hat Enterprise Linux 7, 8, 9, and 10 per CPE data; exploitation is local-only and requires high privileges (CVSS PR:H), so risk is confined to systems where the yggdrasil account is already reachable. No public exploit code was identified in the provided sources at time of analysis, and no CISA KEV or EPSS signal was supplied.
The FileBasedKeyLifecycleManager in Apache Camel's PQC (post-quantum cryptography) component writes generated private key material to disk using whatever permissions the process umask produces instead of restricting the file to its owner, so on hosts with a permissive umask such as 022 the unencrypted private key is group- and world-readable. Affected are Apache Camel 4.12.0 through 4.18.4 and 4.19.0 through 4.22.0 that use this component to persist key material; an attacker who already holds a separate local account on the same host can read the key file and then forge signatures or break key exchanges performed by that deployment. The CVSS 3.1 vector (AV:L/PR:L/C:H) confines this to a local, authenticated party - no public exploit code has been identified at time of analysis and there is no CISA KEV listing - and the vendor assesses severity as low because the remote sender that Camel's threat model targets is not the exposure path.
Privilege escalation in Essential Addons for Elementor through 6.8.5 allows a high-privilege authenticated WordPress user to gain greater capabilities when required user interaction occurs and additional attack conditions are satisfied. The flaw is a CWE-266 incorrect privilege assignment issue rated CVSS 6.4, reported by Patchstack; exploitation is constrained by PR:H, UI:R, and AC:H, so it is not remotely reachable by an unauthenticated attacker and reliable opportunistic exploitation is difficult. No public exploit identified at time of analysis, and no CISA KEV active-exploitation status was provided.
Vikunja 2.6.0 allows an authenticated collaborator who holds a higher permission on a parent project to override an explicitly set read-only share on a nested child project, enabling modification of that child's tasks and content. This broken access control is a permission-resolution regression introduced in 2.6.0 and only affects users who already have access to the project tree; no public exploit was identified at time of analysis. The issue is limited to integrity impact and is a low-to-moderate priority rather than a critical remote threat.
IBM i releases 7.3, 7.4, 7.5 and 7.6 can allow a remote authenticated attacker to slip past the ChrootDirectory confinement that is supposed to isolate SSH/SFTP users, exposing files and data outside the directory they were meant to be restricted to. The weakness is entirely dependent on configuration: it only affects systems that explicitly set ChrootDirectory in sshd_config and rely on it as an isolation boundary, while default deployments without chroot confinement are not impacted. No public exploit code has been identified at time of analysis, and because a valid restricted-account credential is mandatory and the assessed impact is bounded to low confidentiality and integrity loss with no availability effect, this rates as a moderate, operator-dependent issue rather than an emergency.
Unauthenticated privilege escalation in the WP Compress - Instant Performance & Speed Optimization plugin for WordPress (all versions up to and including 7.25.00) allows remote attackers with no WordPress account to gain plugin-administrator-equivalent control over the plugin's optimization, CDN and critical-CSS settings. The chain is two-stage: the stored plugin API key is first leaked by the unauthenticated `wpc_send_critical_remote` nopriv AJAX action, but only when the external critical-CSS service returns an `apiResults` field that causes `initCritical()` to echo the key via `wp_send_json_success`; the harvested key is then replayed as the `apikey` parameter to the `start_comms` dispatcher, which performs no capability check and no nonce verification before passing attacker-controlled `group`, `setting` and `value` parameters into `change_setting()`, writing them into the `WPS_IC_SETTINGS` option without an allow-list and causing `checkAndAddCaps()` to grant the `manage_wpc_settings` capability to arbitrary roles, including Subscriber. The assessed severity is moderate - CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N) - unauthenticated per the vector (PR:N) but rated high complexity because the API-key disclosure depends on the external critical-CSS service response; impact is scoped to the plugin's settings surfaces rather than full WordPress site administration, and no public exploit code and no confirmed active exploitation (not in CISA KEV) were identified at time of analysis.
The WholesaleX B2B/wholesale plugin for WooCommerce (up to and including 3.0.8) fails to validate the 'wholesalex_registration_role' parameter handled by 'process_registration', letting an attacker submit a registration with a role of their choosing and thereby self-assign any already-existing WholesaleX wholesale/B2B role. Impact is bounded - the escalation is limited to the plugin's own role tiers and does not reach arbitrary WordPress roles such as administrator - and the independent assessment rates it a moderate, not top-tier, priority (reassessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). Authentication requirements are not fully resolved from the available data: the vendor description and the independent reassessment treat the attacker as unauthenticated, while the originally published CVSS vector carries PR:L. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Local privilege escalation in FreeBSD's sound(4) driver stems from a time-of-check/time-of-use race in audio-buffer resizing: a local, authenticated user with sound-device access can race an mmap(2) call against a buffer reallocation to cause a kernel use-after-free. Affected releases are FreeBSD 15.1-RELEASE before p5, 14.4-RELEASE before p11, and 14.5-RELEASE before p2; the independent assessment rates exploitation as local, authenticated, high-complexity, and requiring a non-deterministic timing win, with high confidentiality, integrity, and availability impact if successful. EPSS is 0.11% (1st percentile) and no public exploit identified at time of analysis, making this a genuine but lower-tier priority compared with remotely exploitable or actively exploited issues.
Local privilege escalation in Palo Alto Networks GlobalProtect App versions 6.3.0 before 6.3.3-h16 and 6.2.0 before 6.2.8-h15 on macOS allows an authenticated local non-administrative user to obtain root privileges and execute arbitrary commands. The vulnerability is due to an untrusted search path (CWE-426) and requires a local foothold; no public exploit has been identified at time of analysis. Other platforms (Linux, Windows, iOS, Android, Chrome OS) are not affected.
Local privilege escalation in TSplus Remote Access allows an authenticated low-privilege user to modify writable autostart1.tscr login scripts in the shared themes directory, then wait for another user-including a higher-privileged one-to log in with the same theme or operating mode, at which point the injected commands execute in that victim's security context. Exploitation requires three conditions: a valid interactive session on the terminal/remote desktop server, misconfigured permissions on the shared script files (CWE-276), and a subsequent victim login; no public exploit has been identified at time of analysis. The vendor rates this CVSS 4.0 5.4 (Medium) with high confidentiality, integrity, and availability impact on the vulnerable system.
Local privilege escalation in Akamai Guardicore Platform Agent (GPA) on macOS before version 7.4 allows an attacker with administrative privileges to execute arbitrary commands as root by exploiting a command injection in the wapptunneld component. The vulnerability requires local access and high privileges (PR:H), and exploitation necessitates that the 'Log out from your IdP' action is triggered after a malicious network interface name is set. No public exploit code or active exploitation has been identified; this is a genuine but bounded risk limited to unpatched macOS deployments.
Local privilege escalation in HYPR Passwordless on Windows (all releases before 11.3.3) allows an attacker holding existing low-privileged local access to manipulate a user-controlled key used in an authorization decision, bypassing access checks and reaching resources belonging to other or higher-privileged principals. The vulnerability is an insecure direct object reference (CWE-639) rated CVSS:4.0 base 6.9 (Medium) with a local vector (AV:L, PR:L, UI:N) and high confidentiality impact but only limited integrity and availability impact, meaning the practical worst case is unauthorized disclosure rather than full host takeover. No public exploit code has been identified at time of analysis, and HYPR has addressed the issue in version 11.3.3, so only unpatched installations remain exposed.
Local information disclosure in Google Chrome's installer component on Windows (versions prior to 155.0.8059.79) allows an attacker who can already run a local program to obtain sensitive information via the installer path, though user interaction is required to trigger the vulnerable flow. Rooted in execution with unnecessary privileges (CWE-250) and rated 5.5 (moderate), the issue carries an EPSS score of 0.11% (1st percentile) and no public exploit identified at time of analysis; CISA KEV does not list it and the SSVC decision framework rates exploitation as none. Google has released a vendor patch in Chrome 155.0.8059.79.
Privilege escalation in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.9) allows an authenticated low-privileged user to bypass authorization checks and carry out management operations beyond their assigned role, but only on servers where the optional restConnector-2.0 feature has been explicitly enabled. It carries a medium CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) as a CWE-863 improper authorization flaw, meaning credentials are required, no user interaction is needed, and impact is limited to low confidentiality and integrity loss with no availability impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the exposure is meaningfully limited because a bare default server.xml does not enable this connector.
Tampering of Windows Host Guardian Service (HGS) configuration and attestation-related data is possible for an authenticated local attacker on hosts where the HGS role is deployed, yielding high integrity impact with no loss of confidentiality or availability. Rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) under CWE-250, this is a moderate-severity, low-priority issue rather than an urgent threat: Microsoft has released patched builds, no public exploit code has been identified at time of analysis, and CISA's SSVC decision framework records Exploitation: none and Automatable: no. Exposure is narrow, confined to guarded-fabric/shielded-VM environments where the HGS server role is installed rather than to general Windows installations.
Privilege escalation in Microsoft's Windows HID class driver lets an attacker who already has physical access to a machine elevate to kernel-level privileges by attaching a crafted USB/HID peripheral and winning a race condition in the driver's object lifetime handling. Because the vector is physical (CVSS:3.1/AV:P) and attack complexity is high (AC:H), the flaw is not remotely exploitable and is non-deterministic in practice; it is limited to shared, kiosk, unattended, or otherwise physically reachable endpoints. No authentication (PR:N) and no user interaction (UI:N) are required once physical access is obtained, and no public exploit identified at time of analysis; vendor patches are available. Impact is high for confidentiality, integrity, and availability on the compromised host (CVSS 6.4).
FortiSandbox and FortiSandbox Cloud ship with a hard-coded cryptographic key that is used to validate or sign trusted HTTP requests, allowing an unauthenticated remote attacker who knows that static key to craft requests the appliance treats as legitimate and thereby escalate privileges. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, official score 5.3), no valid credentials or user interaction are required once the embedded key is known, though exploitation is limited to deployments that expose the HTTP/management interface to the attacker's network. Affected versions are FortiSandbox 5.2.0-5.2.1, 5.0.0-5.0.6 and all 4.4 releases, plus the corresponding FortiSandbox Cloud versions; there is no public exploit identified at time of analysis, but the issue is authoritative-moderate severity and should be remediated rather than treated as an emergency.
OS command injection in Fortinet FortiManager (8.0.0 and 7.6.0-7.6.6) and FortiManager Cloud (7.6.2-7.6.6) allows a high-privileged authenticated attacker on an adjacent network to execute arbitrary operating system commands, enabling privilege escalation and potential full compromise of the management appliance. The vulnerability requires an existing administrative account (CVSS PR:H) and network adjacency (AV:A), and no public exploit identified at time of analysis. Despite the high-value nature of the target, these prerequisites substantially narrow realistic risk to post-compromise or malicious insider scenarios, consistent with the moderate-risk assessment.
InstallShield 2025 R2 and earlier can resolve bundled prerequisite installers from an unsecured, attacker-writable location when a compressed Basic MSI Setup.exe is launched from that directory, allowing a local attacker who pre-plants a malicious prerequisite to escalate privileges once an administrator runs the installer. This is a medium-severity local privilege escalation in the CWE-426 untrusted search path class (CVSS 4.0 base 5.4; independent CVSS 3.1 assessment AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H), and no public exploit code or confirmed active exploitation was identified at the time of analysis. Only compressed Basic MSI setups that include Prerequisites are affected, and exploitation requires both local write access to the setup location and an administrator-driven launch.
Local information disclosure in AMI Aptio V BIOS/UEFI firmware allows low-privileged local attackers to access sensitive data, with potential follow-on privilege escalation and limited integrity/availability impact. The issue is medium-severity, requires pre-existing local access and high attack complexity, is not remotely reachable, and has no public exploit identified at time of analysis; AMI advisory AMI-SA-2026002 should be reviewed for affected versions and fixes.
Authorization bypass in Wazuh Manager 4.0.0 through 4.14.7 lets an authenticated low-privileged API user read the RBAC catalog by calling the GET /security/actions and /security/resources endpoints, which omit the caller's RBAC policy checks. The exposure is read-only: an attacker learns which privileged actions and endpoints exist, giving them a map to plan lateral movement or privilege escalation within the platform, but cannot modify data or disrupt the service. Authentication with a valid API account is mandatory (CVSS vector PR:L), the assigned score is 5.3, and no public exploit code has been identified at time of analysis; this is a medium-severity information-disclosure issue rather than an emergency, and vendor-released patch version 4.14.8 is available.
Improper privilege management in cal.com and its cal.diy fork up to version 6.2.0 lets an authenticated low-privilege user delete credential objects belonging to teams they are not authorized to manage. By calling the credentials.delete tRPC procedure with a teamId outside their scope, an attacker can remove scheduling/calendar integration credentials, causing a limited integrity and availability impact on the targeted team; no data is disclosed and no victim interaction is required. Publicly available exploit code exists (a proof-of-concept gist is referenced), and the vendor did not respond to the disclosure, so no fixed version has been identified; the assessed CVSS 3.1 vector is 6.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, making this a low-priority issue that still requires a valid account to abuse.
Local users on IBM i 7.3, 7.4, 7.5, and 7.6 can modify the system BOOTP table because the operating system fails to enforce a proper authority check on that configuration function, a case of improper privilege management (CWE-269). Exploitation requires an interactive or authenticated local presence on the host with at least low-level privileges (CVSS vector AV:L/PR:L), so neither a remote nor a fully unauthenticated attacker can trigger it, and the resulting impact is capped at low confidentiality and low integrity with no availability effect (CVSS 4.4). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, though IBM has published a vendor fix; this is a low-to-moderate priority issue rather than a top-tier emergency, with exposure scaling with the number of local accounts permitted on the partition.
Local information disclosure in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 allows an attacker who already has access to the host to read sensitive data by abusing a service account that was configured with excessive permissions. The flaw is a privilege-assignment problem (CWE-250) rather than a memory-safety or injection bug: because the service account holds rights beyond what it needs, anything reachable by that account - files, directories, or configuration - becomes reachable to a local user. Impact is confidentiality-only (C:H with I:N/A:N on CVSS 3.1, base 6.2, AV:L/AC:L/PR:N/UI:N), so no tampering or denial of service is involved, there is no network attack path, and there is no public exploit identified at time of analysis; IBM has published a fix referenced in advisory node/7291755.
Local privilege escalation in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.5 allows an authenticated low-privileged user on the database host to abuse the db2pd monitoring and diagnostic utility to gain privileges beyond those they legitimately hold. Exploitation requires pre-existing local shell access and the ability to run db2pd, so the flaw is not reachable remotely or by unauthenticated actors; it matters most on shared, multi-tenant, or otherwise privileged-access Db2 servers. Our independent assessment rates the true impact higher than IBM's published CVSS 6.5, scoring it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though a vendor patch is available and should be applied to remove the condition.
Privilege escalation in ZITADEL 3.0.0 through 4.19.1 lets accounts that already hold the IAM_END_USER_IMPERSONATOR or ORG_END_USER_IMPERSONATOR role obtain tokens for administrators, including IAM_OWNER, and sign in to relying applications carrying those administrators' roles and claims, because the OIDC token-exchange flow fails to enforce the admin.impersonation check (CWE-863). Exploitation requires the high-privilege prerequisite that an end-user impersonator role has been deliberately granted (CVSS PR:H), so arbitrary authenticated users and unauthenticated attackers cannot trigger it, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. The vendor fixed the bypass in ZITADEL 4.19.2.
Local privilege escalation in Yun Jia Security Guard up to 2.7.1.9 allows an authenticated local attacker to manipulate the Pid argument to function sub_14000885C in the kgameprotect.sys kernel driver, resulting in improper privilege management. The vulnerability requires the product to be installed with the driver loaded and a low-privileged local account; it cannot be exploited remotely. No public exploit code has been identified, and the vendor has not responded to disclosure attempts.
Improper privilege management in RuoYi up to 4.8.3 allows an authenticated low-privileged attacker to modify role authorization data via the roleKey parameter at the /system/role/authDataScope endpoint, enabling privilege escalation within the management console. Publicly available exploit code exists, and the vendor did not respond to disclosure; no vendor-released patch has been identified at time of analysis. The vulnerability has a CVSS 4.0 base score of 5.3 (medium) with low integrity and availability impact and no confidentiality impact.
Agno's Team Delegation Feature runs member agents without a confirmation gate, allowing an actor who can influence delegated task content to cause team agents to execute actions with unnecessary, unscoped privileges. The flaw resides in the delegate_task_to_member / delegate_task_to_members tooling in libs/agno/agno/team/_default_tools.py and affects agno versions up to 3.0.6 and 3.1.1. Publicly available exploit code exists (no CISA KEV listing), and the upstream fix - PR #10124, which sets delegate_func.requires_confirmation = True - still awaits acceptance, so no released patched version is independently confirmed.
Launching an arbitrary activity with Samsung Flow's own privileges is possible for a local attacker on a device running Samsung Flow prior to version 4.9.22.4, because the app ships with an incorrect default permission setting that exposes the capability to other local code on the device. Only users of the affected Samsung Flow builds on devices that are actually paired/connected to a counterpart device are exposed, and the resulting impact is bounded to the connected system with low confidentiality and integrity effect (vendor CVSS 4.0 base 2.1; our assessment CVSS 3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N). There is no indication of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the presence of the AT:P attack-requirement in the vendor vector means a specific pairing/connection state must exist before exploitation is even feasible.
Local information disclosure in Samsung Locksettings (prior to SMR Oct-2026 Release 1) allows an attacker who already possesses root privilege on the device to read data belonging to a tied profile while the device is in the Before First Unlock (BFU) state. Exploitation is local-only (AV:L) and requires high privileges (PR:H), with no remote path; it does not enable privilege escalation, code execution, or data modification. No public exploit code exists, and the vulnerability is not listed in CISA KEV; EPSS data was not provided at time of analysis.
Local authenticated attackers with low privileges can bypass or break the Sandbox component in deepseek-harness up to 0.1.1-rc.2 by manipulating the 'Profile' argument to the spawn function, resulting in a sandbox issue that may lead to limited privilege escalation. Publicly available exploit code exists, but the impact is capped at Low for confidentiality, integrity, and availability with no scope change, making this a low-priority issue. The vendor did not respond to disclosure, and no patch has been identified.
Information disclosure in ZTE Z80 Ultra allows a malicious or compromised third-party app installed on the device to invoke system interfaces through reflection and retrieve sensitive information, because those interfaces lack robust invocation authentication and access control. Exploitation is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), with confidentiality impact only and no integrity or availability effect. No public exploit identified at time of analysis; the issue is classified under CWE-269 and tagged as privilege escalation, but the assessed impact is a moderate, local-only information-disclosure flaw rather than a high-priority remote threat.
Local information disclosure in ZTE Z80 Ultra devices allows an installed third-party application to capture device-related data returned by system interfaces that do not adequately restrict access. The issue requires local execution and user interaction to install or run the hostile app, and it needs no elevated privileges (PR:N), resulting in a low CVSS score of 3.3 with only confidentiality impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the risk is best treated as low priority.
Information disclosure in ZTE Z80 Ultra allows a locally installed application to read device-related information by invoking framework methods that have insufficient access control. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 5.5) means an attacker needs local access and must persuade or trick the user into installing or interacting with a malicious app, with impact limited to confidentiality; there is no integrity or availability impact and no privilege gain, despite the 'Privilege Escalation' tag. No public exploit code is identified at time of analysis, and the issue is assessed as moderate and locally scoped.
Information disclosure in ZTE Z80 Ultra devices lets a locally installed malicious application read information through system callable functions that lack sufficient access control. This is a low-severity, low-priority local issue (CVSS 3.3) requiring user interaction, typically installing or launching the attacker's app, with only confidentiality impact and no integrity or availability effect. No public exploit identified at time of analysis.
ZTE Z80 Ultra allows a malicious third-party application installed on the device to hook exposed system APIs and read limited sensitive information, resulting in a low-severity information disclosure (CVSS 3.1 base score 3.3). The attack is local-only, requires user interaction to install the attacking app, and requires no special privileges (PR:N), with only a low confidentiality impact and no integrity or availability impact; no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Information disclosure in ZTE Z80 Ultra (nubia Z80 Ultra) smartphones allows a local app to reflectively invoke a system interface that lacks the necessary access-control check and read otherwise-protected information, with no integrity or availability impact. The vendor rates this CVE-2026-108501 at CVSS 5.7 (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), while the independent assessment treats it as a local, unauthenticated information-disclosure issue (CVSS 3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) that requires code execution on the device via an attacker-controlled app. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is confined to the ZTE Z80 Ultra model.
Authenticated privilege escalation in the Academy LMS WordPress plugin through version 4.0.3 lets a user with the academy_guardian role or higher assign the academy_student role to any existing WordPress account, including their own, via the guardian add_child REST API. The flaw stems from add_role('academy_student') executing before Store::link() validates the guardian-ward relationship and not rolling back on WP_Error, so even self-links rejected by Store::link() leave the role grant in place. This yields Contributor-equivalent edit_posts unconditionally and Author-equivalent upload_files only when the student file-upload setting is enabled; CVSS is 5.4 and no public exploit has been identified at time of analysis.
Local privilege escalation and arbitrary code execution in the BusyBox tar applet (CVE-2026-108119) allow an attacker who supplies a crafted tar archive to create or replace files outside the extraction directory when the archive is extracted with elevated privileges. The flaw is a CWE-59 link-following issue in the applet's deferred symlink/hardlink creation path, with a CVSS 3.1 base score of 6.3 (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), affecting BusyBox as shipped in Red Hat Enterprise Linux 6 and Red Hat Hardened Images. No public exploit identified at time of analysis; exploitation requires a privileged user or process to actively extract the malicious archive, and the specific archive construction plus directory-reuse timing makes this high-complexity and local-only.
Privilege escalation in the Ultimate Member WordPress plugin (all versions through 2.13.1) arises from an incorrect privilege assignment that lets a user reach permissions beyond those they should legitimately hold. The assessed vector - CVSS 5.6 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L) - combines high attack complexity with low-privileged access, meaning exploitation depends on specific conditions rather than a single trivial request, and the resulting confidentiality, integrity, and availability impact is limited rather than site-takeover grade. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV), so this should be treated as a moderate-priority patch item for any WordPress site running the plugin at or below 2.13.1.
Privilege escalation in the Redux Framework WordPress plugin through version 4.5.11 lets an authenticated attacker with only Subscriber-level access escalate to any role, including Administrator, by writing an arbitrary role value during a profile update. The flaw is conditionally exploitable: it only triggers on sites where an active plugin or theme has integrated Redux user-profile fields via Redux_Users::set_profile/set_section/set_field, which is a non-default integration requirement, so having the plugin installed alone is not sufficient. Wordfence rates this 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), the attack requires no victim interaction and is network-reachable, and no public exploit code has been identified at time of analysis; the practical limiting factor is the required third-party profile-field integration.
World-readable CodeCatalyst token cache files in AWS Toolkit for VS Code versions before 4.10.0 let any other local user on the same host recover bearer tokens for a victim who has connected the CodeCatalyst integration. The flaw is a local information-disclosure and privilege-escalation concern (CWE-276, CVSS 6.8) rather than a remote attack: it requires a shared multi-user system, an ordinary local login, no user interaction, and no elevated privileges, and yields only read impact (confidentiality) with no integrity or availability loss. No public exploit code has been identified at time of analysis and the issue is not reported as actively exploited; the vendor has released a fix in version 4.10.0.
A kernel-mode heap buffer overflow (CWE-122) in HP Sure Click and the related HP Wolf Security product family at versions below 4.4.33 allows a local attacker who already holds elevated privileges to corrupt kernel memory and potentially escalate to full system-level code execution. The flaw is reachable only from a local context on a Windows host running the affected endpoint security agent, requires a non-trivial triggering condition such as precise heap state or a memory-corruption race, and exposes no network or remote attack path. HP has released version 4.4.33 as the vendor-released fix, and no public exploit code has been identified at time of analysis.
Local privilege escalation in Checkmk 2.5.0 (before 2.5.0p10) requires the non-default 'mk-oracle' agent plugin and local write access to the Oracle Instant Client path, enabling an authenticated local attacker to escalate privileges (CWE-426). The vendor has released a patch in 2.5.0p10, and no public exploit identified at time of analysis; the CVSS 4.0 score is 5.2, but exploitation is constrained by multiple preconditions that substantially limit real-world risk, making this a low-to-moderate priority issue.
Privilege escalation in Brocade Fabric OS (versions before 9.2.2d and 10.0.0 through 10.0.0a1) allows an authenticated low-privileged user on the adjacent management network to bypass authorization controls in the account management interface and assign administrative roles to other accounts. Exploitation requires specific conditions and high attack complexity (AC:H), but successful attacks can yield high integrity and availability impact. No public exploit identified at time of analysis; vendor advisory and fixed versions are available.
The cluster-samples-operator in Red Hat OpenShift Container Platform 4 assigns an overly permissive RBAC Role (coreos-pull-secret-reader) that grants get/list/watch on all Secrets in the openshift-config namespace, exceeding the operator's requirement for only the pull-secret Secret. This excessive-privilege weakness (CWE-250) does not provide initial access; an attacker must first compromise the operator pod or its service-account token through a separate vulnerability, after which they can read sensitive cluster secrets such as OAuth identity provider credentials and cloud provider credentials. No public exploit code is identified, and the issue is a defense-in-depth concern rather than a directly exploitable flaw (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Sensitive-file disclosure in the export policies feature of Cisco Application Policy Infrastructure Controller (APIC) allows an authenticated remote administrator to submit crafted values in specific UI fields and read files from the device's underlying filesystem, including cryptographic key material. The flaw carries a moderate CVSS score of 6.5 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and is not remotely exploitable without credentials: valid administrative access is mandatory, and the CVSS vector confirms the high privilege requirement (PR:H) with no user interaction. Because the exposed key material may be usable to escalate to root on the affected APIC and on managed switches in the ACI fabric, the fallout of a successful attack can extend well beyond a single controller; no public exploit code or confirmed active exploitation was identified at time of analysis, and there is no CISA KEV listing.
Local privilege escalation in the Aruba/HPE ClearPass client software lets a low-privileged local user execute commands with elevated privileges on the affected host, but only when a specific environmental precondition that the vendor describes as being outside the attacker's control is satisfied. The assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, score 6.7) confirms that exploitation requires an interactive local session with an existing low-privileged account plus user interaction, meaning there is no remote or unauthenticated attack path and the attacker cannot deterministically force the triggering condition. There is no public exploit identified at time of analysis, no CISA KEV listing, and no evidence of active exploitation; the practical risk is moderate and bounded by these prerequisites rather than by remote reachability.
CRI-O instances explicitly configured with a non-empty bind_mount_prefix can be induced to resolve a container's CRI hostPath bind-mount source outside the intended prefixed root, giving an attacker with the ability to define such mounts read and write access to host files and a route to privilege escalation. The flaw is conditional rather than broadly exploitable: it requires the non-default bind_mount_prefix setting, high privileges to specify hostPath mounts (PR:H), and a carefully arranged intermediate absolute symlink in the requested path (AC:H), and default-configured CRI-O deployments are not exposed. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a moderate, conditional risk rather than an urgent priority.
Improper privilege management in the Chrome UI on macOS allows a remote attacker to bypass system access restrictions by socially engineering a victim into visiting and interacting with a crafted HTML page. Only Chrome for macOS builds prior to 155.0.8059.39 are affected; no authentication is required (PR:N), but the attack cannot succeed without the victim actively engaging with the malicious page (UI:R). Google rates the Chromium security severity as Low, EPSS is just 0.18% (7th percentile), SSVC records no exploitation and no automatable path, and no public exploit code has been identified at the time of analysis. Impact is limited to partial confidentiality and integrity loss with no availability effect.
Local privilege escalation in Google Android's platform message handler lets an actor who already holds System-level execution privileges bypass a missing permission check in platform_msg_handler_init (default_msg_handlers.c) and obtain high-impact control over confidentiality, integrity, and availability on the device. Rated CVSS 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the issue requires local access and a pre-existing high privilege level, making it an authorization-boundary bypass for an already-privileged local actor rather than a path to initial device compromise. There is no public exploit identified at time of analysis and CISA's SSVC assessment records Exploitation: none and Automatable: no, while a vendor fix is published in the October 2026 Android Security Bulletin.
An out-of-bounds write in the Android kernel's Wacom HID driver (wacom_hid_set_device_mode in wacom_sys.c) lets an attacker who can physically attach or emulate a malicious Wacom HID peripheral corrupt kernel memory and escalate privileges on the affected device. No authentication or user interaction is required once the peripheral is connected, because the crafted report reaches the driver's missing bounds check directly; the CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms a physical-access-only attack path with high confidentiality, integrity, and availability impact. Only Pixel/Android kernel builds that include and exercise the Wacom HID driver are affected, and there is no public exploit identified at time of analysis; CISA SSVC rates exploitation as none and automatable as no, so the practical risk is bounded by the strict physical-access requirement and the inability to exploit this remotely or at scale.
A logic error in the Android kernel hardware-crypto driver routine kdn_set_sysregs_prot (hwcrypto-kdn.c) causes an information disclosure, but only for an attacker who already executes code with System-level privileges directly on the affected Pixel/Tensor device. The CVSS base score is 4.4 (Medium) with vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, reflecting a local-only, high-privilege, confidentiality-only impact with no integrity or availability effect; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV (SSVC: Exploitation none). In practice this is a genuine-but-low-priority weakness that hardens an already-compromised or highly privileged execution context rather than a remotely reachable or pre-auth escalation path.
apko truncates out-of-range UID and GID values that it parses from package-supplied /etc/passwd and /etc/group entries, so a crafted package can make an account that appears unprivileged be written into the resulting image as UID 0 / GID 0 (root). An attacker must first control a package installed into the image being built - a supply-chain foothold rather than arbitrary remote access - and the impact is confined to the produced image's file ownership and its resolved run-as user, not the build host itself. The flaw affects apko versions 0.2.0 up to but not including 1.4.5 on 64-bit platforms; it is rated 6.3 under CVSS 4.0 (independently assessed as AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N on CVSS 3.1), and no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patch: 1.4.5.
Read-only administrative users on Red Hat Quay can retrieve repository write (delegate) tokens through the build trigger API, then use those tokens to push arbitrary container images into private repositories despite their restricted role. Exploitation requires an account already holding global read-only administrative privileges (CVSS vector PR:H) plus repositories that have build triggers configured with embedded delegate tokens, so realistic risk is confined to malicious insiders or attackers who have already compromised a read-only admin credential. The flaw is rated moderate at CVSS 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N), and no public exploit identified at time of analysis.
Privilege escalation in Penpot before 2.18.0 lets a non-owner team administrator promote themselves to team owner by creating or modifying team invitations with the :owner role, since the invitation code path lacked the role-ceiling check that guards update-team-member-role. Exploitation requires the attacker to already hold the team-level 'administrator' role (authenticated, PR:H), and the resulting access is confined to that team's owner-only controls; no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied. It is a moderate-priority, within-tenant integrity issue rather than an internet-facing emergency.
Penpot versions prior to 2.18.0 fail to protect a team owner from removal by another administrator: a non-owner team admin can call the delete-team-member RPC to strip the owner's team-profile membership, locking the owner out of the team and its projects, files, fonts, and media. The flaw is an authenticated, high-privilege availability issue (CVSS 4.9, AV:N/PR:H, availability-only), not a remotely exploitable unauthenticated attack, and no public exploit code was identified at time of analysis. The issue is fixed in 2.18.0.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Privilege-model bypass in Rapid7 Velociraptor's Windows.Sysinternals.SysmonLogForward artifact allows an authenticated operator who holds only the COLLECT_CLIENT permission (typically the built-in 'Investigator' role) to launch an arbitrary, attacker-chosen binary on monitored Windows endpoints instead of the installed Sysmon binary. Because the artifact exposes a user-controllable binary-path parameter and fails to enforce the additional EXECVE permission that gates comparable dangerous artifacts, successful collection results in code execution on the endpoint under the elevated privileges the artifact normally runs with, yielding high confidentiality, integrity, and availability impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Exploitation is not anonymous: the attacker must already be a trusted Velociraptor operator with artifact-collection rights, and the chosen binary must be reachable or placeable on the target endpoint, which narrows realistic exposure to insiders or compromised operator accounts. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is a moderate, privilege-escalation class flaw rather than a mass-exploitation threat.
An authenticated Project Member (role 15) in Plane can escalate a Project Guest (role 5) to the Member role without Project Admin approval by sending a PATCH request to the project-member update endpoint at /api/workspaces/{workspace_slug}/projects/{project_id}/members/{member_pk}/. The role-update logic only rejected assignments where the new role exceeded the requester's own role, so submitting a role equal to the attacker's Member role slipped past the check and granted the guest Member-level project capabilities, bypassing project governance controls. This is a moderate-severity, authenticated privilege-escalation flaw (CWE-269) affecting Plane deployments prior to 1.4.0; no public exploit code was identified and the issue is not confirmed as actively exploited (CISA KEV).
Local privilege escalation in MediaTek venc on multiple chipsets allows an attacker who already possesses System-level privileges to escalate to kernel-level code execution via a type confusion that leads to an out-of-bounds write. The vulnerability requires local access and high privileges (PR:H) with no user interaction, and no public exploit has been identified at the time of analysis. This is a post-compromise escalation step, not a remote or initial-access vector.
Local privilege escalation in MediaTek's mtee (MediaTek TEE) allows an attacker who already holds System privilege to exploit a missing bounds check, causing an out-of-bounds write that can elevate privileges on affected MediaTek chipsets. The vulnerability requires local access and high privileges (PR:H) with no user interaction, and affects 25 listed MediaTek chipset models including MT8196, MT6768, MT6769, MT6833, MT6877, MT8186, and MT8188. No public exploit code or active exploitation has been identified at time of analysis.
Local privilege escalation in MediaTek mtee allows a local attacker who already holds Android System privilege to exploit a CWE-843 type confusion and elevate code execution on affected MediaTek chipsets; user interaction is not required. The flaw is local-only (AV:L) and requires high privileges (PR:H), so it cannot be used for initial access or remote compromise and is primarily useful as a chain component after an attacker has already obtained a System-level foothold. MediaTek has published Patch ID ALPS11383899 in its October 2026 bulletin, and no public exploit identified at time of analysis.
Local privilege escalation in MediaTek's vdec (video decoder) component allows an attacker who already holds System privilege on an affected chipset to supply crafted input that triggers a type-confusion-driven out-of-bounds write, corrupting memory and achieving high confidentiality, integrity, and availability impact at a higher privilege level. The issue affects 24 MediaTek SoCs including MT8395, MT6833, MT6789, MT8195, MT6877, MT8189, MT8391, MT8676, MT8678, MT8793, MT8799, MT6855, MT8367, MT8781, MT8196, MT8910, MT8668, MT8188, MT8792, MT6769, MT6768, MT8186, MT8788E, and MT2718, across mobile, tablet, and embedded platforms. Exploitation is local only, requires the System-privilege prerequisite, and needs no user interaction; the CVSS 3.1 base score is 6.7 (MEDIUM) and no public exploit was identified at time of analysis, so the practical risk is a post-compromise escalation primitive rather than a remote entry point.
Local privilege escalation in MediaTek's meta component affects numerous MediaTek chipsets (including MT6789, MT6895, MT6985, MT8195, and others listed in EUVD-2026-92196) and allows an attacker with physical access to the device to trigger an out-of-bounds write due to a missing bounds check, achieving high confidentiality and integrity impact. No authentication, existing execution privileges, or user interaction are required once physical access is obtained. No public exploit has been identified at time of analysis; the physical access prerequisite limits remote exploitation and confines realistic abuse to scenarios such as lost or stolen devices, border inspection, or supply-chain tampering.
Use-after-free memory corruption in MediaTek's apusys driver allows a local attacker who has already obtained Android System privilege (uid system) to escalate to kernel-level code execution on affected devices, with no user interaction required once that foothold exists. The flaw affects firmware running on a broad set of MediaTek SoCs - including MT6897, MT6899, MT6989, MT6991, MT8196, MT8678 and the other MT-series chipsets listed in MediaTek's October 2026 bulletin - and is addressed by Patch ID ALPS11076799 (Issue ID MSV-8143). Because the CVSS vector carries PR:H and AV:L, this is a second-stage privilege-escalation link that presupposes a prior System-level compromise rather than a standalone remotely reachable bug; no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in MediaTek AIDL on affected chipsets is possible via a use-after-free memory corruption, but only after an attacker has already obtained Android System privilege and local access. Successful exploitation requires no user interaction and can yield high confidentiality, integrity, and availability impact within that privileged context. No public exploit identified at time of analysis; the vendor patch ID ALPS11185225 and the October 2026 MediaTek security bulletin address the issue.
Local privilege escalation in the aidl component shipped on a defined set of MediaTek chipsets (MT6899, MT6991, MT8910, MT8781, MT6881, MT8668, MT6989, MT8188, MT6878, MT6993, MT8695, MT8189, MT8696) allows a process that already holds Android System privilege to trigger a use-after-free, corrupt memory, and gain higher-integrity code execution with high confidentiality, integrity, and availability impact. The attack is local (AV:L) and needs no user interaction, but the PR:H prerequisite means it cannot be used for initial access and only functions as a follow-on escalation from an already-compromised privileged context. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; EPSS data was not supplied for this CVE. MediaTek has published a fix under Patch ID ALPS11242428 in its October 2026 Product Security Bulletin.
A missing permission check in the MediaTek AIDL (Android Interface Definition Language) component allows an attacker who already holds the Android System privilege to escalate to higher privileges locally, with no user interaction required. The expected impact is high across confidentiality, integrity, and availability (CVSS 3.1 base 6.7, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), but the local-only vector and the PR:H precondition mean an ordinary unprivileged app cannot trigger it directly - it is only useful as a second-stage step in an existing exploit chain or for already-privileged malware. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); this is a moderate, defense-in-depth issue rather than a top-tier emergency.
Local privilege escalation in the MediaTek display component could allow an attacker who already holds Android System-level privilege to gain elevated code execution through an integer overflow (CWE-190), with no user interaction required. The flaw affects a broad set of MediaTek chipsets (including MT6893, MT6895, MT6983, MT6991, and MT8188) running unpatched firmware and is rated CVSS 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, but MediaTek has published patch ID ALPS11296678 in its October 2026 security bulletin.
Local privilege escalation in the MediaTek display component lets a process that already holds System privilege trigger an out-of-bounds write in a display-path buffer, corrupting memory and potentially escalating to higher-level code execution with high impact to confidentiality, integrity, and availability. The defect is a missing bounds check (CWE-787) reachable without user interaction and with low attack complexity, but only from an existing System-privileged, on-device context (CVSS 3.1 6.7 Medium, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), so it functions as a second-stage escalation primitive rather than an initial-access or remote vector. Affected hardware spans a broad set of MediaTek chipsets including MT6991, MT6993, MT2718, MT8168-class MT8668/MT8678, MT8171, MT8188, MT8189, MT8196, MT8793, and MT8126; MediaTek has issued Patch ID ALPS11292777 (issue MSV-9195) and no public exploit code has been identified at time of analysis.
Local privilege escalation in the battery component shipped with a wide range of MediaTek chipsets (including MT6765, MT6768, MT6853, MT6893, MT6991, MT8186, MT8188 and MT8196) allows an attacker who already holds System privilege to trigger an out-of-bounds write through a missing bounds check, yielding high impact to confidentiality, integrity and availability. No user interaction is required once System access is held, and the flaw is reachable in default configurations of the listed chipsets, making it a post-compromise escalation rather than an initial foothold; the CVSS 6.7 score is dominated by the PR:H prerequisite. A vendor patch is available under MediaTek's October 2026 Product Security Bulletin (patch ID ALPS11276677, issue MSV-9217), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
An out-of-bounds read/write flaw in MediaTek's ccci (cross-core/modem control) component allows an authenticated local attacker who already holds System privilege to corrupt memory, potentially leading to information disclosure, crashes, or further privilege escalation. Exploitation requires local access and, per the vendor description, user interaction - though the vendor CVSS vector omits UI:R - and is limited to specific MediaTek chipsets (MT6880, MT6890, MT6980D, MT6990, MT6986, MT6986D, MT6813, MT6988, MT2735, MT2737). No public exploit code has been identified, SSVC reports exploitation: none and not automatable, making this a high-severity but low-urgency issue due to its high-privilege prerequisite.
Privilege escalation in ezBookkeeping 1.2.0 through 2.0.0 lets an attacker who already holds a short-lived and/or IP-restricted API token exchange it for a full 30-day normal session token by calling POST /api/v1/tokens/refresh.json, because TokenRefreshHandler never verifies the token type before minting a replacement. The resulting session token outlives the original API token's expiry and its IP allowlist, though impact stays within the compromised account's own scope (low confidentiality and integrity impact). Rated CVSS 5.3 (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N), it requires a prior valid API token (authenticated) and is fully remediated in v2.0.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in OpenLiteSpeed before 1.9.3 lets an attacker who already controls the low-privileged 'nobody' web-server process escalate to root by exploiting a time-of-check/time-of-use race in the admin/misc/lsup.sh auto-update script, which fetches, extracts and executes update packages as root from the nobody-writable /usr/local/lsws/autoupdate/ directory with no integrity verification. Realistic exploitation requires three preconditions together - existing code execution as 'nobody', an administrator-triggered update, and winning the race to replace the package before root runs its install.sh - so the flaw is genuine but conditional rather than remotely weaponizable; no public exploit code has been identified at time of analysis (no CISA KEV entry). The vendor fix in 1.9.3 adds SHA-256 checksum verification of downloaded packages, a mode-0700 update directory that refuses symlinks, HTTPS-only downloads with redirects refused, and a proper lock file.
Privilege escalation in Ghost CMS (TryGhost Ghost) versions 0.5.0 through before 6.64.0 allows an authenticated Editor or Super Editor to assign their own elevated role to other staff accounts, promoting existing Author and Contributor users to Editor or Super Editor without holding the authority to do so. Exploitation is gated by the attacker already holding an Editor or Super Editor account (PR:L in the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, vendor CVSS 4.0 score 5.3), so anonymous outsiders cannot abuse it, and the effect is limited to integrity rather than confidentiality or availability. A vendor-supplied patch is available and no public exploit code has been identified at time of analysis.
Local privilege escalation in Johnson Controls Easy IO FG controllers prior to version 2.0b52 allows an authenticated attacker with low-privileged local access to brute-force privilege management controls, potentially leading to high integrity and availability impact. Exploitation is complex and requires a specific attack precondition, and no public exploit code has been identified at the time of analysis. This is a medium-severity, operator-dependent flaw in a niche building-automation controller, not a high-priority mass-exploitation risk.
Privilege escalation in JetBrains YouTrack before 2026.2.19422 allows an authenticated attacker with pre-existing elevated privileges (CVSS PR:H) to abuse user-group membership changes and gain higher privileges, though success requires a specific group-configuration state (AC:H). The flaw is network-reachable (AV:N) and needs no user interaction (UI:N), but the high privilege and configuration prerequisites sharply narrow realistic risk to insiders or holders of a compromised privileged account; no public exploit identified at time of analysis. Vendor CVSS 6.6 Medium and CWE-266 (Incorrect Privilege Assignment) match the assessed vector and the need to manipulate group membership under constrained conditions.
Subscriber privilege escalation in FluentBoards WordPress plugin versions up to 2.0.12 lets an authenticated low-privilege user elevate privileges within the plugin. Exploitation requires a valid Subscriber-level account, is remote and low-complexity, and can result in low confidentiality, integrity, and availability impact; sites with open registration are most exposed. No public exploit or CISA KEV active-exploitation confirmation was identified at time of analysis, making this a genuine but moderate-priority issue rather than a high-urgency one.
Information disclosure in ZTE U30 Air devices allows remote, unauthenticated attackers to read limited sensitive information from the affected interface, owing to improper permission control in the product's access management. The issue is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), meaning no authentication or user interaction is required but the impact ceiling is low confidentiality only - there is no integrity or availability effect and therefore no route to device takeover from this flaw alone. Exploitation requires network reachability to the vulnerable service, and attack surface is further constrained by the device's niche deployment; no public exploit identified at time of analysis and no evidence of active exploitation.
Local privilege escalation in HPE Networking Instant On firmware 3.4.1.0 and earlier allows an attacker who already holds high-privilege local access to the affected daemon to achieve arbitrary code execution as root. The CVSS 3.1 vector (AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H, score 6.4 Medium) shows the barriers are steep: the attacker must be local and already privileged, and exploitation is further gated by 'certain preconditions outside of the attacker's control,' consistent with a high-complexity trigger such as timing or transient system state. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authentication bypass in the captive portal of HPE Networking Instant On (all versions up to and including 3.4.1.0) lets a network-reachable, unauthenticated remote attacker circumvent the portal's authentication controls and obtain limited read access to data plus the ability to make limited changes inside that component. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, base 6.5 Medium) confirms a low-friction attack path requiring no credentials and no user interaction, although the impact is bounded to the captive-portal component with no availability effect. No public exploit code or confirmed in-the-wild exploitation has been identified - no public exploit identified at time of analysis - and no EPSS score was supplied with the source data.
Sandbox containment failure in the deepseek-ai deepseek-harness Code Mode Sandbox (up to and including 0.1.0-rc.7) allows remote, low-privileged attackers who can submit code through the run_code function to escape the worker's intended containment. The vendor's own SAFETY.md and design notes state the worker is "containment, not a security boundary," so the flaw primarily harms deployments that mistakenly rely on it for isolation; there is no public exploit identified at time of analysis and the pre-release, niche nature of the library keeps real-world risk low-to-moderate. Impact is limited to low confidentiality, integrity, and availability effects on the harness itself, with no downstream-scope compromise.
Authenticated contributors can bypass publishing permissions and spoof post authorship in WordPress sites running WPeMatico RSS Feed Fetcher before 2.8.27. By running a feed campaign, a user with contributor-level access or above can publish posts live without editorial review and set any registered user, including an administrator, as the author. Publicly available exploit code exists, but no active exploitation has been reported, and the EPSS score is low at 0.13% (percentile 2%). The independent assessment rates this as a moderate-severity, low-priority authorization flaw.
Capgo CLI's Android onboarding flow silently grants the Google Play service account it generates the account-wide Play Console permission CAN_MANAGE_DRAFT_APPS_GLOBAL, so anyone who obtains the resulting PLAY_CONFIG_JSON key can create, edit, and delete draft apps across the entire Google Play developer account rather than only the single confirmed package the UI claims was shared. The issue affects the npm package @capgo/cli through 7.98.2 and is present in default onboarding, but exploitation is entirely conditional on key exposure - a leaked key in a public repository, CI log, or compromised secrets store - and impact is confined to draft apps with no effect on already-published releases and no confidentiality impact. No vendor-released patch was identified at time of analysis, and no public exploit code has been identified.
Authenticated GLPI users who lack configuration-update privileges can enable the application's debug mode on versions 0.72 through 10.0.25 and 11.0.0 through 11.0.7 by injecting a use_mode parameter into the user-setting update endpoint, which pre-patch code failed to gate behind the Config::canUpdate() check. Successful abuse exposes debug-level diagnostic output that a legitimate low-privilege account should not be able to trigger, resulting in limited confidentiality impact; the flaw does not allow data modification or code execution. No public exploit code has been identified at time of analysis and there is no indication of active exploitation, though a vendor fix is available in GLPI 10.0.26 and 11.0.8. NVD rates the issue 5.3 (CVSS 4.0), and the independent assessment concurs that this is a low-to-moderate authorization weakness given the mandatory authentication prerequisite and confined information-exposure impact.
Improper privilege management in Krayin laravel-crm up to and including 2.2.5 lets an authenticated back-office user who can reach the Settings > Users/Roles area escalate their own privileges by manipulating the role_id argument handled in packages/Webkul/Admin/src/Http/Controllers/Settings/UserController.php. The pre-patch code applies no canManageRole() authorization check and does not block a user from editing the role assigned to their own account or from creating/updating a role carrying permissions broader than their own, so a low-privileged account can grant itself full administrative rights. Publicly available exploit code exists (a proof-of-concept advisory has been published and the issue is tracked on GitHub), while the vendor assigns a modest CVSS 4.0 score of 2.1; exploitation still requires valid credentials for a settings-capable account, so this is a targeted, post-authentication privilege-escalation risk rather than an unauthenticated compromise.
In the Linux kernel, the following vulnerability has been resolved: xfs: initialise args->total for parent pointer updates xfs_parent_da_args_init() builds an xfs_da_args from a zeroed xfs_parent_args (kmem_cache_zalloc), leaving args->total == 0. xfs_da_grow_inode_int() treats that field as a running block reservation and subtracts from it; because it is an xfs_extlen_t (uint32_t), the first attr-fork growth wraps it to ~0U. That defeats the free-space check in xfs_alloc_space_available(), and when it coincides with an AG that has exactly zero available blocks the allocation is clamped to maxlen 0 and returns -ENOSPC, which xfs_defer_finish_noroll() escalates to a filesystem shutdown. Set args->total the way the log recovery path does (xfs_attri_recover_work(), xfs_attr_item.c:706), in the add and replace paths that can grow the fork. Removals and lookups never grow it, so they leave the field alone, matching that switch.
Local code execution on iOS and iPadOS (before 26.7 and the 27 line), macOS Golden Gate (before 27), and visionOS (before 27) can let an attacker-controlled app process overwrite restricted files, breaking file-system integrity protections. The issue is an improper privilege-management and permissions-validation weakness (CWE-269) scored 6.2 with a local-only vector (AV:L/AC:L/PR:N/UI:N), so it is unauthenticated once code is running but cannot be reached remotely - a malicious or sideloaded app must first execute on the device. No public exploit identified at time of analysis and no KEV confirmation; Apple has released vendor patches in iOS 26.7/iPadOS 26.7, iOS 27/iPadOS 27, macOS Golden Gate 27, and visionOS 27.
Local privilege escalation in Red Hat rhc's rhc-canonical-facts.service lets an attacker who has already compromised the privileged yggdrasil service account pre-plant a symbolic link so the root-run unit follows it and changes ownership of an arbitrary file, enabling escalation to root. The flaw is CWE-59 link following and affects rhc installations on Red Hat Enterprise Linux 7, 8, 9, and 10 per CPE data; exploitation is local-only and requires high privileges (CVSS PR:H), so risk is confined to systems where the yggdrasil account is already reachable. No public exploit code was identified in the provided sources at time of analysis, and no CISA KEV or EPSS signal was supplied.
The FileBasedKeyLifecycleManager in Apache Camel's PQC (post-quantum cryptography) component writes generated private key material to disk using whatever permissions the process umask produces instead of restricting the file to its owner, so on hosts with a permissive umask such as 022 the unencrypted private key is group- and world-readable. Affected are Apache Camel 4.12.0 through 4.18.4 and 4.19.0 through 4.22.0 that use this component to persist key material; an attacker who already holds a separate local account on the same host can read the key file and then forge signatures or break key exchanges performed by that deployment. The CVSS 3.1 vector (AV:L/PR:L/C:H) confines this to a local, authenticated party - no public exploit code has been identified at time of analysis and there is no CISA KEV listing - and the vendor assesses severity as low because the remote sender that Camel's threat model targets is not the exposure path.
Privilege escalation in Essential Addons for Elementor through 6.8.5 allows a high-privilege authenticated WordPress user to gain greater capabilities when required user interaction occurs and additional attack conditions are satisfied. The flaw is a CWE-266 incorrect privilege assignment issue rated CVSS 6.4, reported by Patchstack; exploitation is constrained by PR:H, UI:R, and AC:H, so it is not remotely reachable by an unauthenticated attacker and reliable opportunistic exploitation is difficult. No public exploit identified at time of analysis, and no CISA KEV active-exploitation status was provided.
Vikunja 2.6.0 allows an authenticated collaborator who holds a higher permission on a parent project to override an explicitly set read-only share on a nested child project, enabling modification of that child's tasks and content. This broken access control is a permission-resolution regression introduced in 2.6.0 and only affects users who already have access to the project tree; no public exploit was identified at time of analysis. The issue is limited to integrity impact and is a low-to-moderate priority rather than a critical remote threat.
IBM i releases 7.3, 7.4, 7.5 and 7.6 can allow a remote authenticated attacker to slip past the ChrootDirectory confinement that is supposed to isolate SSH/SFTP users, exposing files and data outside the directory they were meant to be restricted to. The weakness is entirely dependent on configuration: it only affects systems that explicitly set ChrootDirectory in sshd_config and rely on it as an isolation boundary, while default deployments without chroot confinement are not impacted. No public exploit code has been identified at time of analysis, and because a valid restricted-account credential is mandatory and the assessed impact is bounded to low confidentiality and integrity loss with no availability effect, this rates as a moderate, operator-dependent issue rather than an emergency.
Unauthenticated privilege escalation in the WP Compress - Instant Performance & Speed Optimization plugin for WordPress (all versions up to and including 7.25.00) allows remote attackers with no WordPress account to gain plugin-administrator-equivalent control over the plugin's optimization, CDN and critical-CSS settings. The chain is two-stage: the stored plugin API key is first leaked by the unauthenticated `wpc_send_critical_remote` nopriv AJAX action, but only when the external critical-CSS service returns an `apiResults` field that causes `initCritical()` to echo the key via `wp_send_json_success`; the harvested key is then replayed as the `apikey` parameter to the `start_comms` dispatcher, which performs no capability check and no nonce verification before passing attacker-controlled `group`, `setting` and `value` parameters into `change_setting()`, writing them into the `WPS_IC_SETTINGS` option without an allow-list and causing `checkAndAddCaps()` to grant the `manage_wpc_settings` capability to arbitrary roles, including Subscriber. The assessed severity is moderate - CVSS 4.8 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N) - unauthenticated per the vector (PR:N) but rated high complexity because the API-key disclosure depends on the external critical-CSS service response; impact is scoped to the plugin's settings surfaces rather than full WordPress site administration, and no public exploit code and no confirmed active exploitation (not in CISA KEV) were identified at time of analysis.
The WholesaleX B2B/wholesale plugin for WooCommerce (up to and including 3.0.8) fails to validate the 'wholesalex_registration_role' parameter handled by 'process_registration', letting an attacker submit a registration with a role of their choosing and thereby self-assign any already-existing WholesaleX wholesale/B2B role. Impact is bounded - the escalation is limited to the plugin's own role tiers and does not reach arbitrary WordPress roles such as administrator - and the independent assessment rates it a moderate, not top-tier, priority (reassessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N). Authentication requirements are not fully resolved from the available data: the vendor description and the independent reassessment treat the attacker as unauthenticated, while the originally published CVSS vector carries PR:L. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
Local privilege escalation in FreeBSD's sound(4) driver stems from a time-of-check/time-of-use race in audio-buffer resizing: a local, authenticated user with sound-device access can race an mmap(2) call against a buffer reallocation to cause a kernel use-after-free. Affected releases are FreeBSD 15.1-RELEASE before p5, 14.4-RELEASE before p11, and 14.5-RELEASE before p2; the independent assessment rates exploitation as local, authenticated, high-complexity, and requiring a non-deterministic timing win, with high confidentiality, integrity, and availability impact if successful. EPSS is 0.11% (1st percentile) and no public exploit identified at time of analysis, making this a genuine but lower-tier priority compared with remotely exploitable or actively exploited issues.
Local privilege escalation in Palo Alto Networks GlobalProtect App versions 6.3.0 before 6.3.3-h16 and 6.2.0 before 6.2.8-h15 on macOS allows an authenticated local non-administrative user to obtain root privileges and execute arbitrary commands. The vulnerability is due to an untrusted search path (CWE-426) and requires a local foothold; no public exploit has been identified at time of analysis. Other platforms (Linux, Windows, iOS, Android, Chrome OS) are not affected.
Local privilege escalation in TSplus Remote Access allows an authenticated low-privilege user to modify writable autostart1.tscr login scripts in the shared themes directory, then wait for another user-including a higher-privileged one-to log in with the same theme or operating mode, at which point the injected commands execute in that victim's security context. Exploitation requires three conditions: a valid interactive session on the terminal/remote desktop server, misconfigured permissions on the shared script files (CWE-276), and a subsequent victim login; no public exploit has been identified at time of analysis. The vendor rates this CVSS 4.0 5.4 (Medium) with high confidentiality, integrity, and availability impact on the vulnerable system.
Local privilege escalation in Akamai Guardicore Platform Agent (GPA) on macOS before version 7.4 allows an attacker with administrative privileges to execute arbitrary commands as root by exploiting a command injection in the wapptunneld component. The vulnerability requires local access and high privileges (PR:H), and exploitation necessitates that the 'Log out from your IdP' action is triggered after a malicious network interface name is set. No public exploit code or active exploitation has been identified; this is a genuine but bounded risk limited to unpatched macOS deployments.
Local privilege escalation in HYPR Passwordless on Windows (all releases before 11.3.3) allows an attacker holding existing low-privileged local access to manipulate a user-controlled key used in an authorization decision, bypassing access checks and reaching resources belonging to other or higher-privileged principals. The vulnerability is an insecure direct object reference (CWE-639) rated CVSS:4.0 base 6.9 (Medium) with a local vector (AV:L, PR:L, UI:N) and high confidentiality impact but only limited integrity and availability impact, meaning the practical worst case is unauthorized disclosure rather than full host takeover. No public exploit code has been identified at time of analysis, and HYPR has addressed the issue in version 11.3.3, so only unpatched installations remain exposed.
Local information disclosure in Google Chrome's installer component on Windows (versions prior to 155.0.8059.79) allows an attacker who can already run a local program to obtain sensitive information via the installer path, though user interaction is required to trigger the vulnerable flow. Rooted in execution with unnecessary privileges (CWE-250) and rated 5.5 (moderate), the issue carries an EPSS score of 0.11% (1st percentile) and no public exploit identified at time of analysis; CISA KEV does not list it and the SSVC decision framework rates exploitation as none. Google has released a vendor patch in Chrome 155.0.8059.79.
Privilege escalation in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.9) allows an authenticated low-privileged user to bypass authorization checks and carry out management operations beyond their assigned role, but only on servers where the optional restConnector-2.0 feature has been explicitly enabled. It carries a medium CVSS 3.1 score of 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) as a CWE-863 improper authorization flaw, meaning credentials are required, no user interaction is needed, and impact is limited to low confidentiality and integrity loss with no availability impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and the exposure is meaningfully limited because a bare default server.xml does not enable this connector.
Tampering of Windows Host Guardian Service (HGS) configuration and attestation-related data is possible for an authenticated local attacker on hosts where the HGS role is deployed, yielding high integrity impact with no loss of confidentiality or availability. Rated CVSS 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) under CWE-250, this is a moderate-severity, low-priority issue rather than an urgent threat: Microsoft has released patched builds, no public exploit code has been identified at time of analysis, and CISA's SSVC decision framework records Exploitation: none and Automatable: no. Exposure is narrow, confined to guarded-fabric/shielded-VM environments where the HGS server role is installed rather than to general Windows installations.
Privilege escalation in Microsoft's Windows HID class driver lets an attacker who already has physical access to a machine elevate to kernel-level privileges by attaching a crafted USB/HID peripheral and winning a race condition in the driver's object lifetime handling. Because the vector is physical (CVSS:3.1/AV:P) and attack complexity is high (AC:H), the flaw is not remotely exploitable and is non-deterministic in practice; it is limited to shared, kiosk, unattended, or otherwise physically reachable endpoints. No authentication (PR:N) and no user interaction (UI:N) are required once physical access is obtained, and no public exploit identified at time of analysis; vendor patches are available. Impact is high for confidentiality, integrity, and availability on the compromised host (CVSS 6.4).
FortiSandbox and FortiSandbox Cloud ship with a hard-coded cryptographic key that is used to validate or sign trusted HTTP requests, allowing an unauthenticated remote attacker who knows that static key to craft requests the appliance treats as legitimate and thereby escalate privileges. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N, official score 5.3), no valid credentials or user interaction are required once the embedded key is known, though exploitation is limited to deployments that expose the HTTP/management interface to the attacker's network. Affected versions are FortiSandbox 5.2.0-5.2.1, 5.0.0-5.0.6 and all 4.4 releases, plus the corresponding FortiSandbox Cloud versions; there is no public exploit identified at time of analysis, but the issue is authoritative-moderate severity and should be remediated rather than treated as an emergency.
OS command injection in Fortinet FortiManager (8.0.0 and 7.6.0-7.6.6) and FortiManager Cloud (7.6.2-7.6.6) allows a high-privileged authenticated attacker on an adjacent network to execute arbitrary operating system commands, enabling privilege escalation and potential full compromise of the management appliance. The vulnerability requires an existing administrative account (CVSS PR:H) and network adjacency (AV:A), and no public exploit identified at time of analysis. Despite the high-value nature of the target, these prerequisites substantially narrow realistic risk to post-compromise or malicious insider scenarios, consistent with the moderate-risk assessment.
InstallShield 2025 R2 and earlier can resolve bundled prerequisite installers from an unsecured, attacker-writable location when a compressed Basic MSI Setup.exe is launched from that directory, allowing a local attacker who pre-plants a malicious prerequisite to escalate privileges once an administrator runs the installer. This is a medium-severity local privilege escalation in the CWE-426 untrusted search path class (CVSS 4.0 base 5.4; independent CVSS 3.1 assessment AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H), and no public exploit code or confirmed active exploitation was identified at the time of analysis. Only compressed Basic MSI setups that include Prerequisites are affected, and exploitation requires both local write access to the setup location and an administrator-driven launch.
Local information disclosure in AMI Aptio V BIOS/UEFI firmware allows low-privileged local attackers to access sensitive data, with potential follow-on privilege escalation and limited integrity/availability impact. The issue is medium-severity, requires pre-existing local access and high attack complexity, is not remotely reachable, and has no public exploit identified at time of analysis; AMI advisory AMI-SA-2026002 should be reviewed for affected versions and fixes.
Authorization bypass in Wazuh Manager 4.0.0 through 4.14.7 lets an authenticated low-privileged API user read the RBAC catalog by calling the GET /security/actions and /security/resources endpoints, which omit the caller's RBAC policy checks. The exposure is read-only: an attacker learns which privileged actions and endpoints exist, giving them a map to plan lateral movement or privilege escalation within the platform, but cannot modify data or disrupt the service. Authentication with a valid API account is mandatory (CVSS vector PR:L), the assigned score is 5.3, and no public exploit code has been identified at time of analysis; this is a medium-severity information-disclosure issue rather than an emergency, and vendor-released patch version 4.14.8 is available.
Improper privilege management in cal.com and its cal.diy fork up to version 6.2.0 lets an authenticated low-privilege user delete credential objects belonging to teams they are not authorized to manage. By calling the credentials.delete tRPC procedure with a teamId outside their scope, an attacker can remove scheduling/calendar integration credentials, causing a limited integrity and availability impact on the targeted team; no data is disclosed and no victim interaction is required. Publicly available exploit code exists (a proof-of-concept gist is referenced), and the vendor did not respond to the disclosure, so no fixed version has been identified; the assessed CVSS 3.1 vector is 6.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L, making this a low-priority issue that still requires a valid account to abuse.
Local users on IBM i 7.3, 7.4, 7.5, and 7.6 can modify the system BOOTP table because the operating system fails to enforce a proper authority check on that configuration function, a case of improper privilege management (CWE-269). Exploitation requires an interactive or authenticated local presence on the host with at least low-level privileges (CVSS vector AV:L/PR:L), so neither a remote nor a fully unauthenticated attacker can trigger it, and the resulting impact is capped at low confidentiality and low integrity with no availability effect (CVSS 4.4). No public exploit code has been identified at time of analysis and there is no evidence of active exploitation, though IBM has published a vendor fix; this is a low-to-moderate priority issue rather than a top-tier emergency, with exposure scaling with the number of local accounts permitted on the partition.
Local information disclosure in IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 allows an attacker who already has access to the host to read sensitive data by abusing a service account that was configured with excessive permissions. The flaw is a privilege-assignment problem (CWE-250) rather than a memory-safety or injection bug: because the service account holds rights beyond what it needs, anything reachable by that account - files, directories, or configuration - becomes reachable to a local user. Impact is confidentiality-only (C:H with I:N/A:N on CVSS 3.1, base 6.2, AV:L/AC:L/PR:N/UI:N), so no tampering or denial of service is involved, there is no network attack path, and there is no public exploit identified at time of analysis; IBM has published a fix referenced in advisory node/7291755.
Local privilege escalation in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.5 allows an authenticated low-privileged user on the database host to abuse the db2pd monitoring and diagnostic utility to gain privileges beyond those they legitimately hold. Exploitation requires pre-existing local shell access and the ability to run db2pd, so the flaw is not reachable remotely or by unauthenticated actors; it matters most on shared, multi-tenant, or otherwise privileged-access Db2 servers. Our independent assessment rates the true impact higher than IBM's published CVSS 6.5, scoring it CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H; no public exploit code has been identified and the issue is not confirmed as actively exploited (not in CISA KEV), though a vendor patch is available and should be applied to remove the condition.
Privilege escalation in ZITADEL 3.0.0 through 4.19.1 lets accounts that already hold the IAM_END_USER_IMPERSONATOR or ORG_END_USER_IMPERSONATOR role obtain tokens for administrators, including IAM_OWNER, and sign in to relying applications carrying those administrators' roles and claims, because the OIDC token-exchange flow fails to enforce the admin.impersonation check (CWE-863). Exploitation requires the high-privilege prerequisite that an end-user impersonator role has been deliberately granted (CVSS PR:H), so arbitrary authenticated users and unauthenticated attackers cannot trigger it, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis. The vendor fixed the bypass in ZITADEL 4.19.2.
Local privilege escalation in Yun Jia Security Guard up to 2.7.1.9 allows an authenticated local attacker to manipulate the Pid argument to function sub_14000885C in the kgameprotect.sys kernel driver, resulting in improper privilege management. The vulnerability requires the product to be installed with the driver loaded and a low-privileged local account; it cannot be exploited remotely. No public exploit code has been identified, and the vendor has not responded to disclosure attempts.
Improper privilege management in RuoYi up to 4.8.3 allows an authenticated low-privileged attacker to modify role authorization data via the roleKey parameter at the /system/role/authDataScope endpoint, enabling privilege escalation within the management console. Publicly available exploit code exists, and the vendor did not respond to disclosure; no vendor-released patch has been identified at time of analysis. The vulnerability has a CVSS 4.0 base score of 5.3 (medium) with low integrity and availability impact and no confidentiality impact.
Agno's Team Delegation Feature runs member agents without a confirmation gate, allowing an actor who can influence delegated task content to cause team agents to execute actions with unnecessary, unscoped privileges. The flaw resides in the delegate_task_to_member / delegate_task_to_members tooling in libs/agno/agno/team/_default_tools.py and affects agno versions up to 3.0.6 and 3.1.1. Publicly available exploit code exists (no CISA KEV listing), and the upstream fix - PR #10124, which sets delegate_func.requires_confirmation = True - still awaits acceptance, so no released patched version is independently confirmed.
Launching an arbitrary activity with Samsung Flow's own privileges is possible for a local attacker on a device running Samsung Flow prior to version 4.9.22.4, because the app ships with an incorrect default permission setting that exposes the capability to other local code on the device. Only users of the affected Samsung Flow builds on devices that are actually paired/connected to a counterpart device are exposed, and the resulting impact is bounded to the connected system with low confidentiality and integrity effect (vendor CVSS 4.0 base 2.1; our assessment CVSS 3.1 AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N). There is no indication of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the presence of the AT:P attack-requirement in the vendor vector means a specific pairing/connection state must exist before exploitation is even feasible.
Local information disclosure in Samsung Locksettings (prior to SMR Oct-2026 Release 1) allows an attacker who already possesses root privilege on the device to read data belonging to a tied profile while the device is in the Before First Unlock (BFU) state. Exploitation is local-only (AV:L) and requires high privileges (PR:H), with no remote path; it does not enable privilege escalation, code execution, or data modification. No public exploit code exists, and the vulnerability is not listed in CISA KEV; EPSS data was not provided at time of analysis.
Local authenticated attackers with low privileges can bypass or break the Sandbox component in deepseek-harness up to 0.1.1-rc.2 by manipulating the 'Profile' argument to the spawn function, resulting in a sandbox issue that may lead to limited privilege escalation. Publicly available exploit code exists, but the impact is capped at Low for confidentiality, integrity, and availability with no scope change, making this a low-priority issue. The vendor did not respond to disclosure, and no patch has been identified.
Information disclosure in ZTE Z80 Ultra allows a malicious or compromised third-party app installed on the device to invoke system interfaces through reflection and retrieve sensitive information, because those interfaces lack robust invocation authentication and access control. Exploitation is local and requires user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), with confidentiality impact only and no integrity or availability effect. No public exploit identified at time of analysis; the issue is classified under CWE-269 and tagged as privilege escalation, but the assessed impact is a moderate, local-only information-disclosure flaw rather than a high-priority remote threat.
Local information disclosure in ZTE Z80 Ultra devices allows an installed third-party application to capture device-related data returned by system interfaces that do not adequately restrict access. The issue requires local execution and user interaction to install or run the hostile app, and it needs no elevated privileges (PR:N), resulting in a low CVSS score of 3.3 with only confidentiality impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the risk is best treated as low priority.
Information disclosure in ZTE Z80 Ultra allows a locally installed application to read device-related information by invoking framework methods that have insufficient access control. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 5.5) means an attacker needs local access and must persuade or trick the user into installing or interacting with a malicious app, with impact limited to confidentiality; there is no integrity or availability impact and no privilege gain, despite the 'Privilege Escalation' tag. No public exploit code is identified at time of analysis, and the issue is assessed as moderate and locally scoped.
Information disclosure in ZTE Z80 Ultra devices lets a locally installed malicious application read information through system callable functions that lack sufficient access control. This is a low-severity, low-priority local issue (CVSS 3.3) requiring user interaction, typically installing or launching the attacker's app, with only confidentiality impact and no integrity or availability effect. No public exploit identified at time of analysis.
ZTE Z80 Ultra allows a malicious third-party application installed on the device to hook exposed system APIs and read limited sensitive information, resulting in a low-severity information disclosure (CVSS 3.1 base score 3.3). The attack is local-only, requires user interaction to install the attacking app, and requires no special privileges (PR:N), with only a low confidentiality impact and no integrity or availability impact; no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV).
Information disclosure in ZTE Z80 Ultra (nubia Z80 Ultra) smartphones allows a local app to reflectively invoke a system interface that lacks the necessary access-control check and read otherwise-protected information, with no integrity or availability impact. The vendor rates this CVE-2026-108501 at CVSS 5.7 (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N), while the independent assessment treats it as a local, unauthenticated information-disclosure issue (CVSS 3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) that requires code execution on the device via an attacker-controlled app. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is confined to the ZTE Z80 Ultra model.
Authenticated privilege escalation in the Academy LMS WordPress plugin through version 4.0.3 lets a user with the academy_guardian role or higher assign the academy_student role to any existing WordPress account, including their own, via the guardian add_child REST API. The flaw stems from add_role('academy_student') executing before Store::link() validates the guardian-ward relationship and not rolling back on WP_Error, so even self-links rejected by Store::link() leave the role grant in place. This yields Contributor-equivalent edit_posts unconditionally and Author-equivalent upload_files only when the student file-upload setting is enabled; CVSS is 5.4 and no public exploit has been identified at time of analysis.
Local privilege escalation and arbitrary code execution in the BusyBox tar applet (CVE-2026-108119) allow an attacker who supplies a crafted tar archive to create or replace files outside the extraction directory when the archive is extracted with elevated privileges. The flaw is a CWE-59 link-following issue in the applet's deferred symlink/hardlink creation path, with a CVSS 3.1 base score of 6.3 (AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H), affecting BusyBox as shipped in Red Hat Enterprise Linux 6 and Red Hat Hardened Images. No public exploit identified at time of analysis; exploitation requires a privileged user or process to actively extract the malicious archive, and the specific archive construction plus directory-reuse timing makes this high-complexity and local-only.
Privilege escalation in the Ultimate Member WordPress plugin (all versions through 2.13.1) arises from an incorrect privilege assignment that lets a user reach permissions beyond those they should legitimately hold. The assessed vector - CVSS 5.6 (AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L) - combines high attack complexity with low-privileged access, meaning exploitation depends on specific conditions rather than a single trivial request, and the resulting confidentiality, integrity, and availability impact is limited rather than site-takeover grade. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV), so this should be treated as a moderate-priority patch item for any WordPress site running the plugin at or below 2.13.1.
Privilege escalation in the Redux Framework WordPress plugin through version 4.5.11 lets an authenticated attacker with only Subscriber-level access escalate to any role, including Administrator, by writing an arbitrary role value during a profile update. The flaw is conditionally exploitable: it only triggers on sites where an active plugin or theme has integrated Redux user-profile fields via Redux_Users::set_profile/set_section/set_field, which is a non-default integration requirement, so having the plugin installed alone is not sufficient. Wordfence rates this 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), the attack requires no victim interaction and is network-reachable, and no public exploit code has been identified at time of analysis; the practical limiting factor is the required third-party profile-field integration.
World-readable CodeCatalyst token cache files in AWS Toolkit for VS Code versions before 4.10.0 let any other local user on the same host recover bearer tokens for a victim who has connected the CodeCatalyst integration. The flaw is a local information-disclosure and privilege-escalation concern (CWE-276, CVSS 6.8) rather than a remote attack: it requires a shared multi-user system, an ordinary local login, no user interaction, and no elevated privileges, and yields only read impact (confidentiality) with no integrity or availability loss. No public exploit code has been identified at time of analysis and the issue is not reported as actively exploited; the vendor has released a fix in version 4.10.0.
A kernel-mode heap buffer overflow (CWE-122) in HP Sure Click and the related HP Wolf Security product family at versions below 4.4.33 allows a local attacker who already holds elevated privileges to corrupt kernel memory and potentially escalate to full system-level code execution. The flaw is reachable only from a local context on a Windows host running the affected endpoint security agent, requires a non-trivial triggering condition such as precise heap state or a memory-corruption race, and exposes no network or remote attack path. HP has released version 4.4.33 as the vendor-released fix, and no public exploit code has been identified at time of analysis.
Local privilege escalation in Checkmk 2.5.0 (before 2.5.0p10) requires the non-default 'mk-oracle' agent plugin and local write access to the Oracle Instant Client path, enabling an authenticated local attacker to escalate privileges (CWE-426). The vendor has released a patch in 2.5.0p10, and no public exploit identified at time of analysis; the CVSS 4.0 score is 5.2, but exploitation is constrained by multiple preconditions that substantially limit real-world risk, making this a low-to-moderate priority issue.
Privilege escalation in Brocade Fabric OS (versions before 9.2.2d and 10.0.0 through 10.0.0a1) allows an authenticated low-privileged user on the adjacent management network to bypass authorization controls in the account management interface and assign administrative roles to other accounts. Exploitation requires specific conditions and high attack complexity (AC:H), but successful attacks can yield high integrity and availability impact. No public exploit identified at time of analysis; vendor advisory and fixed versions are available.
The cluster-samples-operator in Red Hat OpenShift Container Platform 4 assigns an overly permissive RBAC Role (coreos-pull-secret-reader) that grants get/list/watch on all Secrets in the openshift-config namespace, exceeding the operator's requirement for only the pull-secret Secret. This excessive-privilege weakness (CWE-250) does not provide initial access; an attacker must first compromise the operator pod or its service-account token through a separate vulnerability, after which they can read sensitive cluster secrets such as OAuth identity provider credentials and cloud provider credentials. No public exploit code is identified, and the issue is a defense-in-depth concern rather than a directly exploitable flaw (assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).
Sensitive-file disclosure in the export policies feature of Cisco Application Policy Infrastructure Controller (APIC) allows an authenticated remote administrator to submit crafted values in specific UI fields and read files from the device's underlying filesystem, including cryptographic key material. The flaw carries a moderate CVSS score of 6.5 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N) and is not remotely exploitable without credentials: valid administrative access is mandatory, and the CVSS vector confirms the high privilege requirement (PR:H) with no user interaction. Because the exposed key material may be usable to escalate to root on the affected APIC and on managed switches in the ACI fabric, the fallout of a successful attack can extend well beyond a single controller; no public exploit code or confirmed active exploitation was identified at time of analysis, and there is no CISA KEV listing.
Local privilege escalation in the Aruba/HPE ClearPass client software lets a low-privileged local user execute commands with elevated privileges on the affected host, but only when a specific environmental precondition that the vendor describes as being outside the attacker's control is satisfied. The assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H, score 6.7) confirms that exploitation requires an interactive local session with an existing low-privileged account plus user interaction, meaning there is no remote or unauthenticated attack path and the attacker cannot deterministically force the triggering condition. There is no public exploit identified at time of analysis, no CISA KEV listing, and no evidence of active exploitation; the practical risk is moderate and bounded by these prerequisites rather than by remote reachability.
CRI-O instances explicitly configured with a non-empty bind_mount_prefix can be induced to resolve a container's CRI hostPath bind-mount source outside the intended prefixed root, giving an attacker with the ability to define such mounts read and write access to host files and a route to privilege escalation. The flaw is conditional rather than broadly exploitable: it requires the non-default bind_mount_prefix setting, high privileges to specify hostPath mounts (PR:H), and a carefully arranged intermediate absolute symlink in the requested path (AC:H), and default-configured CRI-O deployments are not exposed. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so this is a moderate, conditional risk rather than an urgent priority.
Improper privilege management in the Chrome UI on macOS allows a remote attacker to bypass system access restrictions by socially engineering a victim into visiting and interacting with a crafted HTML page. Only Chrome for macOS builds prior to 155.0.8059.39 are affected; no authentication is required (PR:N), but the attack cannot succeed without the victim actively engaging with the malicious page (UI:R). Google rates the Chromium security severity as Low, EPSS is just 0.18% (7th percentile), SSVC records no exploitation and no automatable path, and no public exploit code has been identified at the time of analysis. Impact is limited to partial confidentiality and integrity loss with no availability effect.
Local privilege escalation in Google Android's platform message handler lets an actor who already holds System-level execution privileges bypass a missing permission check in platform_msg_handler_init (default_msg_handlers.c) and obtain high-impact control over confidentiality, integrity, and availability on the device. Rated CVSS 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the issue requires local access and a pre-existing high privilege level, making it an authorization-boundary bypass for an already-privileged local actor rather than a path to initial device compromise. There is no public exploit identified at time of analysis and CISA's SSVC assessment records Exploitation: none and Automatable: no, while a vendor fix is published in the October 2026 Android Security Bulletin.
An out-of-bounds write in the Android kernel's Wacom HID driver (wacom_hid_set_device_mode in wacom_sys.c) lets an attacker who can physically attach or emulate a malicious Wacom HID peripheral corrupt kernel memory and escalate privileges on the affected device. No authentication or user interaction is required once the peripheral is connected, because the crafted report reaches the driver's missing bounds check directly; the CVSS 3.1 vector (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms a physical-access-only attack path with high confidentiality, integrity, and availability impact. Only Pixel/Android kernel builds that include and exercise the Wacom HID driver are affected, and there is no public exploit identified at time of analysis; CISA SSVC rates exploitation as none and automatable as no, so the practical risk is bounded by the strict physical-access requirement and the inability to exploit this remotely or at scale.
A logic error in the Android kernel hardware-crypto driver routine kdn_set_sysregs_prot (hwcrypto-kdn.c) causes an information disclosure, but only for an attacker who already executes code with System-level privileges directly on the affected Pixel/Tensor device. The CVSS base score is 4.4 (Medium) with vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N, reflecting a local-only, high-privilege, confidentiality-only impact with no integrity or availability effect; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV (SSVC: Exploitation none). In practice this is a genuine-but-low-priority weakness that hardens an already-compromised or highly privileged execution context rather than a remotely reachable or pre-auth escalation path.
apko truncates out-of-range UID and GID values that it parses from package-supplied /etc/passwd and /etc/group entries, so a crafted package can make an account that appears unprivileged be written into the resulting image as UID 0 / GID 0 (root). An attacker must first control a package installed into the image being built - a supply-chain foothold rather than arbitrary remote access - and the impact is confined to the produced image's file ownership and its resolved run-as user, not the build host itself. The flaw affects apko versions 0.2.0 up to but not including 1.4.5 on 64-bit platforms; it is rated 6.3 under CVSS 4.0 (independently assessed as AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N on CVSS 3.1), and no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patch: 1.4.5.
Read-only administrative users on Red Hat Quay can retrieve repository write (delegate) tokens through the build trigger API, then use those tokens to push arbitrary container images into private repositories despite their restricted role. Exploitation requires an account already holding global read-only administrative privileges (CVSS vector PR:H) plus repositories that have build triggers configured with embedded delegate tokens, so realistic risk is confined to malicious insiders or attackers who have already compromised a read-only admin credential. The flaw is rated moderate at CVSS 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N), and no public exploit identified at time of analysis.
Privilege escalation in Penpot before 2.18.0 lets a non-owner team administrator promote themselves to team owner by creating or modifying team invitations with the :owner role, since the invitation code path lacked the role-ceiling check that guards update-team-member-role. Exploitation requires the attacker to already hold the team-level 'administrator' role (authenticated, PR:H), and the resulting access is confined to that team's owner-only controls; no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied. It is a moderate-priority, within-tenant integrity issue rather than an internet-facing emergency.
Penpot versions prior to 2.18.0 fail to protect a team owner from removal by another administrator: a non-owner team admin can call the delete-team-member RPC to strip the owner's team-profile membership, locking the owner out of the team and its projects, files, fonts, and media. The flaw is an authenticated, high-privilege availability issue (CVSS 4.9, AV:N/PR:H, availability-only), not a remotely exploitable unauthenticated attack, and no public exploit code was identified at time of analysis. The issue is fixed in 2.18.0.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Privilege-model bypass in Rapid7 Velociraptor's Windows.Sysinternals.SysmonLogForward artifact allows an authenticated operator who holds only the COLLECT_CLIENT permission (typically the built-in 'Investigator' role) to launch an arbitrary, attacker-chosen binary on monitored Windows endpoints instead of the installed Sysmon binary. Because the artifact exposes a user-controllable binary-path parameter and fails to enforce the additional EXECVE permission that gates comparable dangerous artifacts, successful collection results in code execution on the endpoint under the elevated privileges the artifact normally runs with, yielding high confidentiality, integrity, and availability impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Exploitation is not anonymous: the attacker must already be a trusted Velociraptor operator with artifact-collection rights, and the chosen binary must be reachable or placeable on the target endpoint, which narrows realistic exposure to insiders or compromised operator accounts. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is a moderate, privilege-escalation class flaw rather than a mass-exploitation threat.
An authenticated Project Member (role 15) in Plane can escalate a Project Guest (role 5) to the Member role without Project Admin approval by sending a PATCH request to the project-member update endpoint at /api/workspaces/{workspace_slug}/projects/{project_id}/members/{member_pk}/. The role-update logic only rejected assignments where the new role exceeded the requester's own role, so submitting a role equal to the attacker's Member role slipped past the check and granted the guest Member-level project capabilities, bypassing project governance controls. This is a moderate-severity, authenticated privilege-escalation flaw (CWE-269) affecting Plane deployments prior to 1.4.0; no public exploit code was identified and the issue is not confirmed as actively exploited (CISA KEV).
Local privilege escalation in MediaTek venc on multiple chipsets allows an attacker who already possesses System-level privileges to escalate to kernel-level code execution via a type confusion that leads to an out-of-bounds write. The vulnerability requires local access and high privileges (PR:H) with no user interaction, and no public exploit has been identified at the time of analysis. This is a post-compromise escalation step, not a remote or initial-access vector.
Local privilege escalation in MediaTek's mtee (MediaTek TEE) allows an attacker who already holds System privilege to exploit a missing bounds check, causing an out-of-bounds write that can elevate privileges on affected MediaTek chipsets. The vulnerability requires local access and high privileges (PR:H) with no user interaction, and affects 25 listed MediaTek chipset models including MT8196, MT6768, MT6769, MT6833, MT6877, MT8186, and MT8188. No public exploit code or active exploitation has been identified at time of analysis.
Local privilege escalation in MediaTek mtee allows a local attacker who already holds Android System privilege to exploit a CWE-843 type confusion and elevate code execution on affected MediaTek chipsets; user interaction is not required. The flaw is local-only (AV:L) and requires high privileges (PR:H), so it cannot be used for initial access or remote compromise and is primarily useful as a chain component after an attacker has already obtained a System-level foothold. MediaTek has published Patch ID ALPS11383899 in its October 2026 bulletin, and no public exploit identified at time of analysis.
Local privilege escalation in MediaTek's vdec (video decoder) component allows an attacker who already holds System privilege on an affected chipset to supply crafted input that triggers a type-confusion-driven out-of-bounds write, corrupting memory and achieving high confidentiality, integrity, and availability impact at a higher privilege level. The issue affects 24 MediaTek SoCs including MT8395, MT6833, MT6789, MT8195, MT6877, MT8189, MT8391, MT8676, MT8678, MT8793, MT8799, MT6855, MT8367, MT8781, MT8196, MT8910, MT8668, MT8188, MT8792, MT6769, MT6768, MT8186, MT8788E, and MT2718, across mobile, tablet, and embedded platforms. Exploitation is local only, requires the System-privilege prerequisite, and needs no user interaction; the CVSS 3.1 base score is 6.7 (MEDIUM) and no public exploit was identified at time of analysis, so the practical risk is a post-compromise escalation primitive rather than a remote entry point.
Local privilege escalation in MediaTek's meta component affects numerous MediaTek chipsets (including MT6789, MT6895, MT6985, MT8195, and others listed in EUVD-2026-92196) and allows an attacker with physical access to the device to trigger an out-of-bounds write due to a missing bounds check, achieving high confidentiality and integrity impact. No authentication, existing execution privileges, or user interaction are required once physical access is obtained. No public exploit has been identified at time of analysis; the physical access prerequisite limits remote exploitation and confines realistic abuse to scenarios such as lost or stolen devices, border inspection, or supply-chain tampering.
Use-after-free memory corruption in MediaTek's apusys driver allows a local attacker who has already obtained Android System privilege (uid system) to escalate to kernel-level code execution on affected devices, with no user interaction required once that foothold exists. The flaw affects firmware running on a broad set of MediaTek SoCs - including MT6897, MT6899, MT6989, MT6991, MT8196, MT8678 and the other MT-series chipsets listed in MediaTek's October 2026 bulletin - and is addressed by Patch ID ALPS11076799 (Issue ID MSV-8143). Because the CVSS vector carries PR:H and AV:L, this is a second-stage privilege-escalation link that presupposes a prior System-level compromise rather than a standalone remotely reachable bug; no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in MediaTek AIDL on affected chipsets is possible via a use-after-free memory corruption, but only after an attacker has already obtained Android System privilege and local access. Successful exploitation requires no user interaction and can yield high confidentiality, integrity, and availability impact within that privileged context. No public exploit identified at time of analysis; the vendor patch ID ALPS11185225 and the October 2026 MediaTek security bulletin address the issue.
Local privilege escalation in the aidl component shipped on a defined set of MediaTek chipsets (MT6899, MT6991, MT8910, MT8781, MT6881, MT8668, MT6989, MT8188, MT6878, MT6993, MT8695, MT8189, MT8696) allows a process that already holds Android System privilege to trigger a use-after-free, corrupt memory, and gain higher-integrity code execution with high confidentiality, integrity, and availability impact. The attack is local (AV:L) and needs no user interaction, but the PR:H prerequisite means it cannot be used for initial access and only functions as a follow-on escalation from an already-compromised privileged context. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; EPSS data was not supplied for this CVE. MediaTek has published a fix under Patch ID ALPS11242428 in its October 2026 Product Security Bulletin.
A missing permission check in the MediaTek AIDL (Android Interface Definition Language) component allows an attacker who already holds the Android System privilege to escalate to higher privileges locally, with no user interaction required. The expected impact is high across confidentiality, integrity, and availability (CVSS 3.1 base 6.7, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), but the local-only vector and the PR:H precondition mean an ordinary unprivileged app cannot trigger it directly - it is only useful as a second-stage step in an existing exploit chain or for already-privileged malware. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); this is a moderate, defense-in-depth issue rather than a top-tier emergency.
Local privilege escalation in the MediaTek display component could allow an attacker who already holds Android System-level privilege to gain elevated code execution through an integer overflow (CWE-190), with no user interaction required. The flaw affects a broad set of MediaTek chipsets (including MT6893, MT6895, MT6983, MT6991, and MT8188) running unpatched firmware and is rated CVSS 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, but MediaTek has published patch ID ALPS11296678 in its October 2026 security bulletin.
Local privilege escalation in the MediaTek display component lets a process that already holds System privilege trigger an out-of-bounds write in a display-path buffer, corrupting memory and potentially escalating to higher-level code execution with high impact to confidentiality, integrity, and availability. The defect is a missing bounds check (CWE-787) reachable without user interaction and with low attack complexity, but only from an existing System-privileged, on-device context (CVSS 3.1 6.7 Medium, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), so it functions as a second-stage escalation primitive rather than an initial-access or remote vector. Affected hardware spans a broad set of MediaTek chipsets including MT6991, MT6993, MT2718, MT8168-class MT8668/MT8678, MT8171, MT8188, MT8189, MT8196, MT8793, and MT8126; MediaTek has issued Patch ID ALPS11292777 (issue MSV-9195) and no public exploit code has been identified at time of analysis.
Local privilege escalation in the battery component shipped with a wide range of MediaTek chipsets (including MT6765, MT6768, MT6853, MT6893, MT6991, MT8186, MT8188 and MT8196) allows an attacker who already holds System privilege to trigger an out-of-bounds write through a missing bounds check, yielding high impact to confidentiality, integrity and availability. No user interaction is required once System access is held, and the flaw is reachable in default configurations of the listed chipsets, making it a post-compromise escalation rather than an initial foothold; the CVSS 6.7 score is dominated by the PR:H prerequisite. A vendor patch is available under MediaTek's October 2026 Product Security Bulletin (patch ID ALPS11276677, issue MSV-9217), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
An out-of-bounds read/write flaw in MediaTek's ccci (cross-core/modem control) component allows an authenticated local attacker who already holds System privilege to corrupt memory, potentially leading to information disclosure, crashes, or further privilege escalation. Exploitation requires local access and, per the vendor description, user interaction - though the vendor CVSS vector omits UI:R - and is limited to specific MediaTek chipsets (MT6880, MT6890, MT6980D, MT6990, MT6986, MT6986D, MT6813, MT6988, MT2735, MT2737). No public exploit code has been identified, SSVC reports exploitation: none and not automatable, making this a high-severity but low-urgency issue due to its high-privilege prerequisite.
Privilege escalation in ezBookkeeping 1.2.0 through 2.0.0 lets an attacker who already holds a short-lived and/or IP-restricted API token exchange it for a full 30-day normal session token by calling POST /api/v1/tokens/refresh.json, because TokenRefreshHandler never verifies the token type before minting a replacement. The resulting session token outlives the original API token's expiry and its IP allowlist, though impact stays within the compromised account's own scope (low confidentiality and integrity impact). Rated CVSS 5.3 (CVSS:4.0 AV:N/AC:L/AT:N/PR:L/UI:N), it requires a prior valid API token (authenticated) and is fully remediated in v2.0.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in OpenLiteSpeed before 1.9.3 lets an attacker who already controls the low-privileged 'nobody' web-server process escalate to root by exploiting a time-of-check/time-of-use race in the admin/misc/lsup.sh auto-update script, which fetches, extracts and executes update packages as root from the nobody-writable /usr/local/lsws/autoupdate/ directory with no integrity verification. Realistic exploitation requires three preconditions together - existing code execution as 'nobody', an administrator-triggered update, and winning the race to replace the package before root runs its install.sh - so the flaw is genuine but conditional rather than remotely weaponizable; no public exploit code has been identified at time of analysis (no CISA KEV entry). The vendor fix in 1.9.3 adds SHA-256 checksum verification of downloaded packages, a mode-0700 update directory that refuses symlinks, HTTPS-only downloads with redirects refused, and a proper lock file.
Privilege escalation in Ghost CMS (TryGhost Ghost) versions 0.5.0 through before 6.64.0 allows an authenticated Editor or Super Editor to assign their own elevated role to other staff accounts, promoting existing Author and Contributor users to Editor or Super Editor without holding the authority to do so. Exploitation is gated by the attacker already holding an Editor or Super Editor account (PR:L in the assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, vendor CVSS 4.0 score 5.3), so anonymous outsiders cannot abuse it, and the effect is limited to integrity rather than confidentiality or availability. A vendor-supplied patch is available and no public exploit code has been identified at time of analysis.
Local privilege escalation in Johnson Controls Easy IO FG controllers prior to version 2.0b52 allows an authenticated attacker with low-privileged local access to brute-force privilege management controls, potentially leading to high integrity and availability impact. Exploitation is complex and requires a specific attack precondition, and no public exploit code has been identified at the time of analysis. This is a medium-severity, operator-dependent flaw in a niche building-automation controller, not a high-priority mass-exploitation risk.
Privilege escalation in JetBrains YouTrack before 2026.2.19422 allows an authenticated attacker with pre-existing elevated privileges (CVSS PR:H) to abuse user-group membership changes and gain higher privileges, though success requires a specific group-configuration state (AC:H). The flaw is network-reachable (AV:N) and needs no user interaction (UI:N), but the high privilege and configuration prerequisites sharply narrow realistic risk to insiders or holders of a compromised privileged account; no public exploit identified at time of analysis. Vendor CVSS 6.6 Medium and CWE-266 (Incorrect Privilege Assignment) match the assessed vector and the need to manipulate group membership under constrained conditions.
Subscriber privilege escalation in FluentBoards WordPress plugin versions up to 2.0.12 lets an authenticated low-privilege user elevate privileges within the plugin. Exploitation requires a valid Subscriber-level account, is remote and low-complexity, and can result in low confidentiality, integrity, and availability impact; sites with open registration are most exposed. No public exploit or CISA KEV active-exploitation confirmation was identified at time of analysis, making this a genuine but moderate-priority issue rather than a high-urgency one.
Information disclosure in ZTE U30 Air devices allows remote, unauthenticated attackers to read limited sensitive information from the affected interface, owing to improper permission control in the product's access management. The issue is rated CVSS 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), meaning no authentication or user interaction is required but the impact ceiling is low confidentiality only - there is no integrity or availability effect and therefore no route to device takeover from this flaw alone. Exploitation requires network reachability to the vulnerable service, and attack surface is further constrained by the device's niche deployment; no public exploit identified at time of analysis and no evidence of active exploitation.
Local privilege escalation in HPE Networking Instant On firmware 3.4.1.0 and earlier allows an attacker who already holds high-privilege local access to the affected daemon to achieve arbitrary code execution as root. The CVSS 3.1 vector (AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H, score 6.4 Medium) shows the barriers are steep: the attacker must be local and already privileged, and exploitation is further gated by 'certain preconditions outside of the attacker's control,' consistent with a high-complexity trigger such as timing or transient system state. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authentication bypass in the captive portal of HPE Networking Instant On (all versions up to and including 3.4.1.0) lets a network-reachable, unauthenticated remote attacker circumvent the portal's authentication controls and obtain limited read access to data plus the ability to make limited changes inside that component. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, base 6.5 Medium) confirms a low-friction attack path requiring no credentials and no user interaction, although the impact is bounded to the captive-portal component with no availability effect. No public exploit code or confirmed in-the-wild exploitation has been identified - no public exploit identified at time of analysis - and no EPSS score was supplied with the source data.
Sandbox containment failure in the deepseek-ai deepseek-harness Code Mode Sandbox (up to and including 0.1.0-rc.7) allows remote, low-privileged attackers who can submit code through the run_code function to escape the worker's intended containment. The vendor's own SAFETY.md and design notes state the worker is "containment, not a security boundary," so the flaw primarily harms deployments that mistakenly rely on it for isolation; there is no public exploit identified at time of analysis and the pre-release, niche nature of the library keeps real-world risk low-to-moderate. Impact is limited to low confidentiality, integrity, and availability effects on the harness itself, with no downstream-scope compromise.
Authenticated contributors can bypass publishing permissions and spoof post authorship in WordPress sites running WPeMatico RSS Feed Fetcher before 2.8.27. By running a feed campaign, a user with contributor-level access or above can publish posts live without editorial review and set any registered user, including an administrator, as the author. Publicly available exploit code exists, but no active exploitation has been reported, and the EPSS score is low at 0.13% (percentile 2%). The independent assessment rates this as a moderate-severity, low-priority authorization flaw.
Capgo CLI's Android onboarding flow silently grants the Google Play service account it generates the account-wide Play Console permission CAN_MANAGE_DRAFT_APPS_GLOBAL, so anyone who obtains the resulting PLAY_CONFIG_JSON key can create, edit, and delete draft apps across the entire Google Play developer account rather than only the single confirmed package the UI claims was shared. The issue affects the npm package @capgo/cli through 7.98.2 and is present in default onboarding, but exploitation is entirely conditional on key exposure - a leaked key in a public repository, CI log, or compromised secrets store - and impact is confined to draft apps with no effect on already-published releases and no confidentiality impact. No vendor-released patch was identified at time of analysis, and no public exploit code has been identified.
Authenticated GLPI users who lack configuration-update privileges can enable the application's debug mode on versions 0.72 through 10.0.25 and 11.0.0 through 11.0.7 by injecting a use_mode parameter into the user-setting update endpoint, which pre-patch code failed to gate behind the Config::canUpdate() check. Successful abuse exposes debug-level diagnostic output that a legitimate low-privilege account should not be able to trigger, resulting in limited confidentiality impact; the flaw does not allow data modification or code execution. No public exploit code has been identified at time of analysis and there is no indication of active exploitation, though a vendor fix is available in GLPI 10.0.26 and 11.0.8. NVD rates the issue 5.3 (CVSS 4.0), and the independent assessment concurs that this is a low-to-moderate authorization weakness given the mandatory authentication prerequisite and confined information-exposure impact.
Improper privilege management in Krayin laravel-crm up to and including 2.2.5 lets an authenticated back-office user who can reach the Settings > Users/Roles area escalate their own privileges by manipulating the role_id argument handled in packages/Webkul/Admin/src/Http/Controllers/Settings/UserController.php. The pre-patch code applies no canManageRole() authorization check and does not block a user from editing the role assigned to their own account or from creating/updating a role carrying permissions broader than their own, so a low-privileged account can grant itself full administrative rights. Publicly available exploit code exists (a proof-of-concept advisory has been published and the issue is tracked on GitHub), while the vendor assigns a modest CVSS 4.0 score of 2.1; exploitation still requires valid credentials for a settings-capable account, so this is a targeted, post-authentication privilege-escalation risk rather than an unauthenticated compromise.
In the Linux kernel, the following vulnerability has been resolved: xfs: initialise args->total for parent pointer updates xfs_parent_da_args_init() builds an xfs_da_args from a zeroed xfs_parent_args (kmem_cache_zalloc), leaving args->total == 0. xfs_da_grow_inode_int() treats that field as a running block reservation and subtracts from it; because it is an xfs_extlen_t (uint32_t), the first attr-fork growth wraps it to ~0U. That defeats the free-space check in xfs_alloc_space_available(), and when it coincides with an AG that has exactly zero available blocks the allocation is clamped to maxlen 0 and returns -ENOSPC, which xfs_defer_finish_noroll() escalates to a filesystem shutdown. Set args->total the way the log recovery path does (xfs_attri_recover_work(), xfs_attr_item.c:706), in the add and replace paths that can grow the fork. Removals and lookups never grow it, so they leave the field alone, matching that switch.