A vulnerability in the openclaw CLI's Slack integration allowed any Slack user who could send a direct message to the bot to execute privileged slash commands when the Slack DM policy was set to open. This bypassed intended allowlist and access-group restrictions. The issue affects openclaw versions from 2026.1.29 up to but not including 2026.2.14 when configured with dmPolicy=open. A patch is available in version 2026.2.14 that corrects the authorization logic for direct messages.
A vulnerability in openclaw-cli versions from 2026.1.29 up to but not including 2026.2.26 allows DM pairing-store identities to bypass group allowlist authorization checks. This flaw enables a sender authorized via direct message pairing to satisfy group sender allowlist requirements without explicit inclusion in the group allowlist, causing an authorization boundary violation between DM pairing and group allowlists. The issue is fixed in version 2026.2.26.
OpenClaw CLI versions up to 2026.2.21-2 have a sender-authorization bypass vulnerability in the toolsBySender group policy matching when using untyped keys. This flaw allows an attacker to gain stronger tool permissions by causing an identifier collision with another sender's identity. The issue is fixed by introducing explicit typed sender keys and deprecating untyped keys. A patch is planned for version 2026.2.22.
OpenClaw CLI versions up to 2026.3.11 have a vulnerability in the Zalouser allowlist authorization where mutable group names were accepted instead of stable group IDs. This allowed different groups with the same display name to be mistakenly authorized, weakening channel authorization and potentially allowing messages from unintended groups to reach the agent. The issue is fixed in version 2026.3.12 by requiring stable group identifiers for allowlist authorization.
OpenClaw CLI versions up to 2026.3.24 contain a vulnerability where sender policy resolution incorrectly downgrades a route-level group allowlist policy to open, allowing unintended interaction with bots. This affects Google Chat spaces and Zalouser groups, permitting any member of an allowlisted group to interact with the bot despite intended sender-level restrictions. The issue is fixed in version 2026.3.28.
A vulnerability in the openclaw-cli package allows unauthorized Telegram group senders to trigger audio preflight transcription, causing resource consumption. The issue affects versions from 2026.1.29 up to but not including 2026.3.31. The impact is limited to resource or billing consumption without direct data exposure or host compromise. A patch is available in version 2026.3.31.
A vulnerability in the Openclaw CLI component interaction misclassifies Group Direct Messages (DMs) as Direct Messages, affecting policy or session handling. This issue is present in versions from 2026.1.29 up to but not including 2026.3.31. The vulnerability has a medium severity with a CVSS score of 5.4. A fix has been released in version 2026.3.31.
OpenClaw CLI versions up to 2026.3.28 have a vulnerability where Discord slash commands bypass the group DM channel allowlist. This allows authorized Discord users to circumvent channel restrictions within group DMs. The issue is limited in scope and does not cross stronger trust boundaries. The vulnerability is rated medium severity with a CVSS score of 5.4. A patch is available in version 2026.3.31 and later.
A vulnerability in openclaw-cli versions 2026.4.10 through 2026.4.13 allows delivery queue recovery to lose group tool-policy context for media replay. This can cause recovered outbound media to be replayed without enforcing the original session's group tool policy, weakening channel media restrictions after a restart or recovery. The issue is fixed in version 2026.4.14.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.4.25 contain a vulnerability where tool group policy callers could accept unvalidated group IDs. This may cause the application of incorrect group-policy decisions for tool invocations when the affected feature is enabled and accessible. The vulnerability does not alter the trusted-operator model of OpenClaw. A patch is available starting with version 2026.4.25. Until patched, it is recommended to avoid exposing group-policy controlled tools to untrusted senders and to apply configuration hardening measures.
OpenClaw CLI versions up to 2026.2.21-2 have an authorization issue where the elevated allowFrom configuration accepted broader identity signals than intended, potentially allowing elevated sender approval based on less strict identity matching. The fix in version 2026.2.22 tightens identity matching to sender-scoped fields only and requires explicit prefixes for mutable metadata. This vulnerability is considered an authorization hardening issue in the context of 1:1 or trusted group chats.
A vulnerability in the openclaw CLI package causes a mismatch in authorization scope for LINE group allowlists. Sender IDs approved via direct message (DM) pairing could improperly satisfy group allowlist checks, allowing broader group sender access than intended. This is due to group allowlist composition inheriting entries from the DM pairing store. The issue affects versions up to 2026.2.25 and is fixed starting from version 2026.2.26.
CVE-2026-70463 is an authorization bypass vulnerability in rsync versions 3.1.0 through 3.4.4. The flaw arises from incorrect parsing of the auth users directive, specifically when group names contain spaces. This causes deny rules associated with such groups to be discarded, allowing authenticated users who should be denied access to connect to restricted modules.
A newline injection vulnerability exists in rsync versions before 3.5.0 within the name-converter uid/gid mapping interface. This flaw allows local attackers to craft user or group names containing newline characters, which can be injected into the rsync daemon's protocol messages. As a result, the daemon may misinterpret attacker-influenced data as legitimate input, corrupting uid/gid mapping logic. The vulnerability has a medium severity rating with a CVSS score of 6.5.
Jewelbug is a China-based hackers-for-hire group conducting parallel operations: espionage campaigns targeting government ministries and militaries across the Middle East, Southeast Asia, and South Asia, alongside a cryptocurrency fraud business. Both missions operate from a single control panel called XG-Web, a browser-centric remote-access framework. The group's main implant is the Antino backdoor, complemented by a malicious browser extension disguised as 'PDF Viewer' and the ClientKing Linux/router implant. Their largest operation compromised over 15 government webmail tenants in a Middle Eastern country through a single watering-hole attack. The victim database recorded over one million implant check-ins and 580,000 stolen browser cookies within three months. Operators are linked to a registered Hunan Province company, with infrastructure supporting both espionage and commercial SEO poisoning operations targeting Chinese-speaking cryptocurrency users.
Jewelbug is a China-based threat actor conducting dual operations: espionage campaigns targeting foreign governments and militaries, alongside a for-profit cryptocurrency fraud business administered from the same control panel. Operating as a small development team with role-based access controls and documented roadmaps, the group recorded over one million implant check-ins, 580,000+ stolen browser cookies, and 2,300+ exfiltrated emails between February and May 2026. Espionage attacks targeted government entities in the Middle East, Southeast Asia, and South Asia with confirmed intrusions. The group deploys the Antino backdoor, a malicious Chrome/Firefox extension called 'PDF Viewer,' and a Linux implant named ClientKing targeting servers and routers. The financially motivated arm operates as a registered Hunan company running industrial-scale SEO poisoning funneling Chinese-speaking victims to fake cryptocurrency exchange sites.
An incorrect authorization check in the v2 Alarm REST API in OpenNMS Meridian and Horizon allows a low-privileged authenticated user (ROLE_REST) to acknowledge, escalate, or clear alarms recorded as an arbitrary username, and, when also assigned ROLE_READONLY, to modify alarm state despite the read-only restriction. A credential check that should restrict these operations is guarded by an inverted condition, so it never executes for a real (non-blank) username. This can potentially allow an attacker to compromise the integrity of alarm state and audit records.
The solution is to upgrade to Meridian 2024.3.12, 2025.0.9 and Horizon 36.0.3 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.
A JEXL expression sandbox bypass exists in multiple versions of OpenNMS Meridian and Horizon. A low-privileged authenticated user can submit a crafted expression to the Measurements REST API that escapes the sandbox and loads arbitrary Java classes on the server. This can potentially allow an attacker to gain access to confidential information and compromise integrity.
The solution is to upgrade to Meridian 2024.3.12, 2025.0.9 and Horizon 36.0.3 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.
vinny/views.py: (ModifyEmailNotifications) IDOR: view fetches VinceCommEmail by raw pk from URL and toggles email_function/name without checking the record's contact belongs to the requesting group-admin. Lets a vendor admin flip notification routing (or read email/name) for another vendor's contact.