Monthly
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and memory-protection bypass in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to execute code at higher privilege, tamper with data, disclose information, or cause denial of service. The flaw is in the kernel-mode layer and affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver/Virtual GPU Manager deployments, with a CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N). No public exploit identified at time of analysis, and no CISA KEV active-exploitation signal is present; the assessed attack path requires prior local access on the host or inside a vGPU guest.
Local privilege escalation in uutils coreutils before 0.10.0: the `install` utility applies a requested setuid/setgid mode (for example -m 4755 or -m 2755) to the destination before performing the requested ownership change, so if the underlying chown(2) call fails the file is left behind as a setuid/setgid executable owned by the privileged invoker who ran the command. Affected are uutils coreutils releases from 0.0.18 up to but not including 0.10.0 (CPE cpe:2.3:a:uutils:coreutils:*:*:*:*:*:*:*:*) on capability-restricted hosts where chown can actually fail, such as environments with euid != 0 or a dropped CAP_CHOWN; a local, authenticated low-privileged operator who can invoke `install` can then execute the leftover binary with elevated privileges. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided; the honest risk picture is a genuine but modest-priority local flaw (CVSS:4.0 7.3 AV:L/AC:H/AT:P/PR:L, our independent CVSS:3.1 assessment AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), not a mass-exploitable remote issue, because on unrestricted systems where chown succeeds the setuid bits are correctly cleared and re-applied.
Sandbox escape in the Avast/AVG/Norton sandbox minifilter driver (aswSnx.sys) on Windows allows an authenticated, low-privileged process already executing inside the sandbox to break file isolation and escalate to SYSTEM (CVSS 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-281). The driver opens the virtualization target with only GENERIC_WRITE and FILE_WRITE_ATTRIBUTES, omitting WRITE_DAC, so every attempt to reapply the original DACL fails silently and virtualized copies of sensitive files are left with permissive permissions; the IRP_MJ_CREATE handler additionally fails to strip WRITE_DAC for sensitive directories, letting a sandboxed process rewrite the security descriptor of a virtualized object, read the virtualized SAM copy, extract local NTLM hashes and run code as SYSTEM. Publicly available exploit code exists (the PrettyPrague proof of concept), the vendor has released patches for the affected Avast, AVG and Norton products, and no CISA KEV entry indicates confirmed active exploitation.
Unauthenticated information disclosure in the wpForo Forum WordPress plugin versions prior to 3.0.2 allows remote attackers to bypass access controls and read forum content that should be restricted. The flaw stems from improper permission preservation (CWE-281), letting unauthenticated users access data intended only for authorized members. No public exploit identified at time of analysis, but a vendor patch is available via Patchstack advisory.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest drivers) allows an authenticated local user to abuse improper permission handling in a kernel mode layer handler, enabling code execution, privilege elevation, and data tampering. CVSS 7.8 reflects high impact across confidentiality, integrity, and availability, but the attack vector is local and authenticated. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC marks technical impact as total.
Privilege escalation in Snipe-IT versions before 8.4.1 allows an authenticated user holding only the `users.edit` permission to grant themselves the `admin` role by sending a PATCH request to `/api/v1/users/{id}` with `permissions[admin]=1`. The API user controller sanitized only the `superuser` key from the submitted permissions array, leaving `admin` and every other permission assignable by any account able to edit users. No public exploit has been identified at time of analysis and the EPSS score is very low (0.01%), but the trivial exploit primitive and full admin takeover make this a high-severity issue (vendor CVSS 4.0 8.7).
Denial of service in Xen's oxenstored (the OCaml Xenstore daemon) arises because quota-related use counts are not released when a domain is destroyed, per Xen Security Advisory 483 (XSA-483). A malicious or buggy guest can repeatedly create and destroy Xenstore state so that leaked accounting counters permanently consume quota, eventually preventing legitimate Xenstore operations and denying service to the host control plane and other domains. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux (open-source kernel module variant) allows any unprivileged local user with an account on the host to abuse a DMA mapping code path where memory access permissions are not properly preserved, potentially yielding code execution, privilege escalation, denial of service, information disclosure, or data tampering. The vulnerability is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires only local access, no user interaction, and no elevated privileges to trigger, but it is confined to systems running the open-source kernel module - the proprietary module is not affected. There is no public exploit identified at time of analysis and no CISA KEV listing; risk is concentrated in multi-user, VDI, cloud-GPU, and HPC hosts where untrusted local users share GPU-equipped machines.
Local privilege escalation in NVIDIA GPU Display Driver for Linux allows an authenticated local unprivileged user to write to memory that the kernel-mode display driver should keep read-only because permissions are not preserved (CWE-281), potentially causing code execution, privilege escalation, denial of service, information disclosure, or data tampering. The affected CPE branches are GeForce, RTX/Quadro/NVS, Tesla, and Guest Driver on Linux, with CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicating high impact after local access. No public exploit identified at time of analysis, and the practical risk is a genuine but not emergency-grade local privilege-escalation issue, most meaningful in shared or multi-tenant GPU environments.
Local privilege escalation and memory-protection bypass in NVIDIA GPU Display Driver for Linux allows an unprivileged local user to execute code at higher privilege, tamper with data, disclose information, or cause denial of service. The flaw is in the kernel-mode layer and affects GeForce, RTX/Quadro/NVS, Tesla, and vGPU Guest Driver/Virtual GPU Manager deployments, with a CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N). No public exploit identified at time of analysis, and no CISA KEV active-exploitation signal is present; the assessed attack path requires prior local access on the host or inside a vGPU guest.
Local privilege escalation in uutils coreutils before 0.10.0: the `install` utility applies a requested setuid/setgid mode (for example -m 4755 or -m 2755) to the destination before performing the requested ownership change, so if the underlying chown(2) call fails the file is left behind as a setuid/setgid executable owned by the privileged invoker who ran the command. Affected are uutils coreutils releases from 0.0.18 up to but not including 0.10.0 (CPE cpe:2.3:a:uutils:coreutils:*:*:*:*:*:*:*:*) on capability-restricted hosts where chown can actually fail, such as environments with euid != 0 or a dropped CAP_CHOWN; a local, authenticated low-privileged operator who can invoke `install` can then execute the leftover binary with elevated privileges. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided; the honest risk picture is a genuine but modest-priority local flaw (CVSS:4.0 7.3 AV:L/AC:H/AT:P/PR:L, our independent CVSS:3.1 assessment AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), not a mass-exploitable remote issue, because on unrestricted systems where chown succeeds the setuid bits are correctly cleared and re-applied.
Sandbox escape in the Avast/AVG/Norton sandbox minifilter driver (aswSnx.sys) on Windows allows an authenticated, low-privileged process already executing inside the sandbox to break file isolation and escalate to SYSTEM (CVSS 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-281). The driver opens the virtualization target with only GENERIC_WRITE and FILE_WRITE_ATTRIBUTES, omitting WRITE_DAC, so every attempt to reapply the original DACL fails silently and virtualized copies of sensitive files are left with permissive permissions; the IRP_MJ_CREATE handler additionally fails to strip WRITE_DAC for sensitive directories, letting a sandboxed process rewrite the security descriptor of a virtualized object, read the virtualized SAM copy, extract local NTLM hashes and run code as SYSTEM. Publicly available exploit code exists (the PrettyPrague proof of concept), the vendor has released patches for the affected Avast, AVG and Norton products, and no CISA KEV entry indicates confirmed active exploitation.
Unauthenticated information disclosure in the wpForo Forum WordPress plugin versions prior to 3.0.2 allows remote attackers to bypass access controls and read forum content that should be restricted. The flaw stems from improper permission preservation (CWE-281), letting unauthenticated users access data intended only for authorized members. No public exploit identified at time of analysis, but a vendor patch is available via Patchstack advisory.
Local privilege escalation in NVIDIA Display Driver for Linux (GeForce, RTX/Quadro/NVS, Tesla, and vGPU guest drivers) allows an authenticated local user to abuse improper permission handling in a kernel mode layer handler, enabling code execution, privilege elevation, and data tampering. CVSS 7.8 reflects high impact across confidentiality, integrity, and availability, but the attack vector is local and authenticated. No public exploit identified at time of analysis and EPSS is 0.01%, but SSVC marks technical impact as total.
Privilege escalation in Snipe-IT versions before 8.4.1 allows an authenticated user holding only the `users.edit` permission to grant themselves the `admin` role by sending a PATCH request to `/api/v1/users/{id}` with `permissions[admin]=1`. The API user controller sanitized only the `superuser` key from the submitted permissions array, leaving `admin` and every other permission assignable by any account able to edit users. No public exploit has been identified at time of analysis and the EPSS score is very low (0.01%), but the trivial exploit primitive and full admin takeover make this a high-severity issue (vendor CVSS 4.0 8.7).
Denial of service in Xen's oxenstored (the OCaml Xenstore daemon) arises because quota-related use counts are not released when a domain is destroyed, per Xen Security Advisory 483 (XSA-483). A malicious or buggy guest can repeatedly create and destroy Xenstore state so that leaked accounting counters permanently consume quota, eventually preventing legitimate Xenstore operations and denying service to the host control plane and other domains. There is no public exploit identified at time of analysis, and the issue is not listed in CISA KEV.