Hispasec•July 23, 2026•🇪🇸Translated from Spanish

CVE-2026-8933: snap-confine Flaw Allows Local Root Escalation on Default Ubuntu Desktop Installs

A security defect in snap-confine, an internal component of snapd, opens the door to local privilege escalation up to root on systems running Ubuntu Desktop. The vulnerability, registered as CVE-2026-8933 and rated high severity, directly impacts default installations of Ubuntu Desktop 24.04, 25.10, and 26.04, a common scenario on corporate laptops, developer workstations, and administrative endpoints.

The weakness does not permit remote access on its own. It requires prior local presence or the ability for an attacker to already execute code with user-level permissions. Once that limited foothold exists, the flaw can convert it into full system control. In CVSS metrics the issue carries a score of 7.8 with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating high risk to confidentiality, integrity, and availability after the attacker is inside the system.

The root cause is linked to a hardening modification that replaced the traditional setuid root model with one based on Linux capabilities. While the redesign was intended to reduce attack surface, it introduced a delicate window during sandbox initialization. Exploitation relies on race conditions during the creation of temporary directories and files in /tmp, combined with FUSE mounts and symbolic links to redirect writes toward sensitive paths.

One described technique bypasses AppArmor confinement by planting a malicious udev rule in /run/udev/rules.d/ and forcing systemd-udevd to execute commands as root. This type of chaining illustrates the real risk on endpoints, where a single untrusted binary executed by a user can lead to complete host compromise.

The upstream fix is included in snapd 2.76.1. Corrected Ubuntu packages comprise 2.76+ubuntu22.04.1, 2.76+ubuntu24.04.1, and 2.76+ubuntu26.04.3, plus ESM versions for Ubuntu 16.04, 18.04, and 20.04. The practical recommendation is to update snapd immediately and verify the version on each machine rather than assuming prior updates or system age provide protection.

In enterprise environments, deployment should prioritize workstations, development teams, and any endpoint likely to run user-privileged software. Beyond patching, tightening the internal perimeter by reducing execution of untrusted binaries, strengthening local access controls, and maintaining solid hardening with active and updated AppArmor helps limit the maneuverability exploited by such local flaws.

Related articles

Habr•Vulnerabilities & Exploits

From HFT to Infosec: How AI Accelerates the Developer-Hacker Arms Race

An experienced security researcher draws a parallel between high-frequency trading evolution and modern vulnerability research, showing how artificial intelligence compresses the time between patch release and working exploit. The author describes the classic workflow where developer Rob fixes buffer overflows in an FTP server while researcher Dave reverse-engineers the diff to locate the exact change. With AI assistance, both sides now generate patches or exploits in minutes rather than days or weeks. The piece highlights that publishing a patch effectively discloses the location of the flaw, allowing automated tools to produce reliable exploits almost instantly. Historical examples such as wu-ftpd CVEs and the EternalBlue/MS17-010 worm illustrate how quickly mass exploitation follows disclosure. The author warns that open-source projects face an existential dilemma: withhold patches and leave users exposed, or release them and trigger immediate automated scanning. Recommendations include mandatory back-porting of fixes and wider use of runtime protections, yet the overall outlook remains pessimistic about the coming wave of fully automated attacks.

Habr•Vulnerabilities & Exploits

Ghost Assets in Vulnerability Management: How Identification, Merging and Asset History Eliminate Anomalies in MaxPatrol VM

Positive Technologies experts explain how infrastructure changes create duplicate, merged and phantom assets that distort vulnerability management. The article details three core mechanisms inside MaxPatrol VM: unique asset identification across scan sources, non-destructive merging of new and existing data, and full lifecycle history with configurable aging policies. It describes how the system distinguishes assets using prioritized keys such as system ID, FQDN, MAC address and VM ID, then applies recursive merging rules that respect multiple data sources. Policies allow teams to set freshness and obsolescence thresholds, automatically hiding assets after 90 days while preserving historical snapshots for PDQL queries. The piece also covers practical cloning and partial-scan scenarios that can produce misleading duplicates or lingering collections.

BoletimSec•Vulnerabilities & Exploits

GreyNoise Detects Active Exploitation Attempts of CVE-2021-36260 Against Hikvision Cameras

GreyNoise recorded exploitation attempts targeting CVE-2021-36260 in Hikvision cameras and recorders between September 21 and October 1. The vulnerability carries a CVSS score of 9.8 and allows unauthenticated remote command execution through insufficient input validation in the embedded web server. Attack traffic originated from four IP addresses, three routed through a commercial VPN in Lithuania and one from a Ukrainian residential network, with all targets located in Ukraine. Attackers leveraged a publicly available Nuclei template to probe devices, though GreyNoise confirmed only scanning activity and not successful compromises. The five-year-old flaw remains actively scanned despite an available firmware patch from Hikvision and a CISA advisory recommending immediate updates. Password changes provide no protection because the attack requires no authentication. Defenders are advised to apply firmware updates, remove devices from public internet exposure, and segment video surveillance networks from critical infrastructure.

Security NEXT•Vulnerabilities & Exploits

Splunk Enterprise Discloses 46 Vulnerabilities Including Critical Patroni Authentication Flaw

Splunk has published three security advisories detailing a total of 46 vulnerabilities affecting Splunk Enterprise and related components. Three of the issues were rated critical, with CVE-2026-76268 receiving a CVSS v3.1 base score of 9.8. The flaw resides in the Patroni REST API used for PostgreSQL cluster management within search head clusters, allowing unauthenticated remote attackers to execute arbitrary operating system commands. Another high-severity issue, CVE-2026-76266, enables local privilege escalation to root on Linux systems during package updates. The remaining vulnerabilities cover product code, internally identified problems, and third-party packages. Organizations are urged to apply the available patches promptly.