Loading story…
Two high-severity vulnerabilities disclosed in VNC-related software allowed local attackers to access or interfere with graphical sessions without proper authorization. OpenClaw versions before 2026.2.21 were affected by CVE-2026-32064, a missing-authentication flaw in the sandbox browser noVNC observer entrypoint. The issue stemmed from x11vnc being launched without authentication, enabling anyone on the host loopback interface to connect to the exposed noVNC port and observe or interact with the sandbox browser. The bug was classified as CWE-306 and carried a CVSS 3.1 score reflecting high confidentiality and integrity impact.
A separate issue, CVE-2026-34352, affected TigerVNC before version 1.16.2 in Image.cxx within x0vncserver. Incorrect permissions could let other local users observe or manipulate screen contents and potentially crash an application, leading to a privilege-escalation scenario. The flaw was classified as CWE-732 and assigned a CVSS 3.1 vector indicating high confidentiality impact with lower integrity and availability effects. Fixes and advisories were published through the projects' GitHub repositories, release channels, and security mailing lists.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-34352 was publicly published for TigerVNC before version 1.16.2. The vulnerability was classified under CWE-732 and assigned a high-severity CVSS v3.1 score reflecting significant confidentiality impact.
TigerVNC released version 1.16.2 to fix a privilege escalation vulnerability affecting earlier versions. The issue involved incorrect permissions in x0vncserver that exposed screen contents and allowed limited manipulation or application crashes by local users.
TigerVNC vulnerability CVE-2026-34352 was received by cve@mitre.org on March 26, 2026. The flaw in Image.cxx within x0vncserver could let other local users observe or manipulate screen contents or crash an application because of incorrect permissions.
The OpenClaw vulnerability was publicly documented as CVE-2026-32064, affecting versions prior to 2026.2.21. The issue was classified as CWE-306 and described as allowing host-local attackers to observe or interact with sandbox browser sessions without credentials.
OpenClaw addressed a missing authentication issue in the sandbox browser entrypoint for noVNC observer sessions in version 2026.2.21. The flaw allowed unauthenticated access to the VNC interface because x11vnc was launched without authentication.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two high-severity vulnerabilities in OpenClaw exposed paths for authenticated users to gain access beyond their intended roles. **CVE-2026-32042** affects versions before `2026.2.25` and allows an attacker with valid shared gateway authentication to present a self-signed, unpaired device identity and bypass pairing requirements, then self-assign elevated operator scopes including `operator.admin`. The issue is classified as `CWE-863` and effectively turns a trusted but unapproved device identity into a route for privilege escalation. A second flaw, **CVE-2026-32051**, affects OpenClaw versions before `2026.3.1` and allows users with `operator.write` scope to reach owner-only tool surfaces such as gateway and cron through agent runs in scoped-token deployments. The authorization mismatch lets lower-privileged authenticated users perform control-plane actions that should be restricted to owners, creating high risk to confidentiality, integrity, and availability. Advisories for both issues point to fixes and security guidance through GitHub and VulnCheck.
Jun 29, 2026
OpenClaw disclosed two high-severity vulnerabilities affecting versions before `2026.2.21` and `2026.3.25`, exposing gateway routes to unauthorized access and privilege escalation. **CVE-2026-32045** is an authentication bypass in HTTP gateway routes caused by incorrect application of tokenless Tailscale header authentication, allowing attackers on trusted networks to reach protected routes without valid tokens or passwords. The issue is tracked as `CWE-290` and carries a CVSS v3.1 vector of `AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`, indicating a confidentiality-focused impact.
Jun 29, 2026
OpenClaw disclosed several high-severity vulnerabilities that can lead to arbitrary code execution and security control bypass across recent releases. **CVE-2026-35641** affects versions before `2026.3.24` and lets a malicious local plugin or hook package use a crafted `.npmrc` file to override the `git` executable during `npm install`, resulting in arbitrary program execution. **CVE-2026-41349** affects versions before `2026.3.28` and allows low-privileged remote attackers to bypass execution approval through `config.patch`, silently disabling agentic consent protections. Belgium's Centre for Cybersecurity warned that multiple OpenClaw flaws can lead to RCE and urged immediate patching. Additional OpenClaw issues published shortly after expand the attack surface. **CVE-2026-41336** affects versions before `2026.3.31` and allows workspace `.env` files to override `OPENCLAW_BUNDLED_HOOKS_DIR`, causing trusted bundled hooks to be replaced with attacker-controlled code from untrusted workspaces. **CVE-2026-41352**, also fixed in `2026.3.31`, allows a device-paired node to bypass the node scope gate and execute arbitrary node commands on the host without proper pairing validation. Separately, the Node.js package **simple-git** disclosed **CVE-2026-6951**, an RCE flaw in versions before `3.36.0` caused by incomplete blocking of Git configuration options, allowing attackers to abuse `--config`, enable `protocol.ext.allow=always`, and trigger execution through an `ext::` clone source when untrusted input reaches the library's options.
Jun 29, 2026