CVE-2026-65960 is a vulnerability in cilium tetragon versions before 1.7.0 where the default Helm configuration exposes a privileged gRPC API via an unauthenticated TCP listener on localhost:54321. This allows an attacker with access to same-node hostNetwork pods to invoke privileged methods without authentication, potentially leading to privilege escalation or container escape. Version 1.7.0 fixes this by changing the default endpoint to a Unix-domain socket, mitigating the exposure.
A critical improper authorization vulnerability exists in node-opcua versions from 2.42.0 up to but not including 2.180.0. The issue arises because namespace-level access control configured via setDefaultRolePermissions is not enforced for nodes lacking explicit per-node RolePermissions. This allows anonymous network clients to write variables or invoke methods despite restrictive namespace defaults. The flaw is fixed in version 2.180.0.
A local privilege escalation vulnerability in the Zimbra Collaboration Suite (ZCS) MTA package allows the Unix zimbra account to execute arbitrary commands as root. The installed sudo policy permits passwordless root execution of Postfix administration commands without restricting their arguments. An attacker can select a zimbra-controlled daemon_directory in the Postfix configuration and invoke postfix set-permissions, causing Postfix to execute the attacker's post-install program as root. The Postfix configuration directory is also writable by zimbra, so restricting postconf alone does not remove the execution path. Exploitation requires local command execution as zimbra on an MTA node. ZCS 10.1.16 and 10.1.21 are affected.
Trudesk versions up to 1.2.11 have a missing authentication vulnerability in debug routes when NODE_ENV is unset. This allows unauthenticated attackers to remotely invoke debug endpoints, including /debug/populatedb, which deletes all groups, tags, and tickets. Attackers can then log in using seeded accounts with the password 'password'.
OpenClaw Windows Node versions before 2026.7.1-3 have a missing authorization vulnerability in NodeService capture handlers. This flaw allows connected gateways or agents to perform screen snapshots, camera captures, and location retrievals without user consent or prompts. Attackers can silently invoke these functions over the node WebSocket interface, compromising user privacy without interaction.
LightLLM versions up to 1.2.0 have a memory exhaustion vulnerability in the NCCL control channel when started with the --pd_trans_mode nccl option. This flaw allows unauthenticated attackers to invoke the exposed_set_value method to store unlimited key-value pairs without size restrictions, leading to exhaustion of KV-transfer worker memory. The resulting memory exhaustion causes the worker process to crash and triggers node failure.
CVE-2026-102829 is a critical OS command injection vulnerability in the steveukx git-js package, specifically related to the argv-parser dependency prior to version 2.0.1. The flaw allows an attacker to influence environment variables, causing Git to invoke an attacker-controlled editor during certain Git operations. This can lead to arbitrary command execution with the privileges of the Node.js process running git-js. The issue is fixed in argv-parser version 2.0.1.
OpenClaw versions 2026.5.1 through 2026.7.0 fail to apply the configured exec approval path to Google Meet node commands. The googlemeet.chrome command accepts caller-supplied audio command arrays and executes them on a paired node without going through the normal system.run approval flow. In deployments with the Google Meet plugin enabled, a paired Chrome node, and the googlemeet.chrome node command allowed, a tool-enabled agent able to invoke that command can execute attacker-selected processes on the paired node, impacting files, credentials, browser profiles, and availability on that node. The issue is fixed in 2026.7.1; as a workaround, remove googlemeet.chrome from allowed node commands or disable the Google Meet plugin.
OpenClaw (npm package 'openclaw') before 2026.7.1 does not enforce the administrator scope requirement on browser control when it is reached through the node.invoke method, although direct browser.request access requires administrator scope. In Gateway deployments that honor caller identity and narrower operator scopes, a write-scoped caller with access to a connected browser-capable node can inspect pages, navigate tabs, or interact with browser-visible applications without the configured admin requirement; practical impact depends on the browser profile and signed-in state. Shared-secret token and password callers are considered fully trusted operators under OpenClaw's security model and are not affected. The issue is fixed in 2026.7.1.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (f996c75c75423a57a64c1c89b04f2e1ba87674973dba2dd359df5b0937ffe3cf)
The package is a dotenv typosquat that runs a hidden Windows loader on every require() and on CLI startup. dist/index.cjs and dist/cli.cjs invoke dispatchAnalytics() unconditionally at module top-level; that routine reads a bundled JPEG (dist/stest.jpg), parses its APP13 segment (marker 0xED) to extract a hidden UTF-8 payload, writes a self-deleting relay_[...].vbs into os.tmpdir(), and spawns wscript.exe detached with windowsHide:true to launch powershell.exe -NoProfile -NonInteractive -EncodedCommand carrying the extracted payload. Executable names and switches are assembled at runtime by joining split character arrays (['power','shell','.exe'].join(''), ['-No','Profile'], ['-Non','Interactive'], ['-Encoded','Command'], ['wscript','.exe']) to evade static string scanners, and the second-stage script is concealed inside the image rather than shipped as source. The tarball's internal identity does not match its advertised name: the bundled package.json inside dist/cli.cjs declares name:'node-env-buffer' version 2.2.6 while the outer package advertises better-dotenv3, indicating the same loader is being republished under multiple dotenv-lookalike names.
A use-after-free vulnerability in the Linux kernel's ACPI bus subsystem was addressed by introducing a new function, acpi_bus_get_primary_device(), which safely obtains the first physical device associated with a given ACPI device while properly reference counting it. The previous function, acpi_get_first_physical_node(), could return a stale device pointer due to a race condition, potentially leading to use-after-free when callers invoke get_device() on that pointer. This vulnerability affects Linux kernel version 3.8. The issue has been fixed in several commits.
Flowise before 3.1.4 contains a remote code execution vulnerability in the Custom MCP node that allows authenticated attackers to execute arbitrary code by supplying npx package names in the mcpServerConfig parameter. Attackers can invoke npx with attacker-controlled npm packages to execute code on the Flowise server.
n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the workflow setting named This workflow can be called by was enforced by the Execute Workflow node but not when a workflow was attached to an Agent as a tool. A user able to build an Agent could invoke a restricted workflow and read its returned data. The affected path is packages/cli/src/modules/agents/tools/workflow-tool-factory.ts, where executeWorkflow omitted SubworkflowPolicyChecker.checkForProject. This issue is fixed in versions 2.37.7 and 2.38.2.
The npm package @testrelic/appium-analytics version 1.1.1-next.88 contains malicious code that executes automatically during installation. It uses obfuscated code to reconstruct and invoke the Function constructor, enabling execution of a hidden payload with access to Node.js module and filesystem APIs. The package also performs network calls and includes install-time dropper behavior. Any system with this package installed should be considered fully compromised, and all secrets on that system should be rotated immediately.
The npm package @testrelic/playwright-analytics version 2.13.0 contains malicious code embedded in its postinstall script. This script uses obfuscation techniques including whitespace padding and a custom shuffle to hide a payload that dynamically executes arbitrary code. The payload gains access to Node.js built-ins by assigning key globals to the global object, enabling potentially harmful operations. Additional bundled files in the package invoke child processes and make outbound HTTP POST requests, inconsistent with the package's declared purpose as a Playwright analytics reporter.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8cebaa0a3370c12104ef2816420193171f431df0d113fdc5d8c9f1dc921deeb5)
Package advertises itself as a TOTP utility but its postinstall script (`node./index.js --setup 2>/dev/null || true`) and its exported `validateSecret` API both invoke a hidden `_run()` routine that (1) scans Discord/Chrome/Edge/Brave/Opera LevelDB stores under `os.homedir()` for Discord auth-token regexes, DPAPI-decrypts encrypted tokens via a spawned powershell `ProtectedData.Unprotect` call, parses Minecraft launcher credentials (vanilla `launcher_accounts.json`, Lunar `accounts.json`, ModrinthApp `app.db` JWTs), validates the harvested Discord tokens against `discord.com/api/v9`, and POSTs the collected credentials to a hardcoded Discord webhook whose URL is stored as chunked base64 in `_x` and reassembled at runtime (`Buffer.from(_x.join(''),'base64')`) to a `discord.com/api/webhooks/1532429233769419004/...` endpoint; and (2) enumerates vanilla/Modrinth/Lunar Minecraft profile `mods/` directories and writes an opaque JAR named `optimized-renderer-1.0.0.jar` (URL also stored as chunked base64 decoding to `cdn.discordapp.com/attachments/1507484731535785994/1540335670831222894/optimized-renderer-1.0.0.jar`) into each discovered mods folder, delivering unverified code that will execute the next time the user launches Minecraft with a Fabric loader. The postinstall suppresses stderr and uses a 4-second `setTimeout` to appear to finish cleanly. Because `validateSecret` (part of the three-function public API) schedules `_run()` via `setImmediate`, the same theft and dropper also fire whenever a downstream consumer imports the package and calls the advertised TOTP function — extending the attack surface well beyond install time.
## Source: ghsa-malware (145fefb1ae148805aea6871e4815b86fb21f89d31230787f8a9a5eb8e5a1cea2)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
## Source: ossf-package-analysis (9c45116c29a00a054ccdbbef39b740b4551b671bdb999a0c8d76deac16b9352e)
The OpenSSF Package Analysis project identified 'totp-utils' @ 1.4.4 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Etherpad is a real-time collaborative editor. From 2.1.0 until 3.1.0, Etherpad's src/node/handler/APIHandler.ts authorizes requests to /api/2/* in the authorization_code OAuth path by using requiredClaims with the admin claim. This check requires only that the claim exists, while src/node/security/OAuth2Provider.ts issues admin: false for configured non-admin users. A non-admin user with a valid signed token can therefore invoke administrative functions including setHTML, setText, appendText, deletePad, copyPad, movePad, restoreRevision, anonymizeAuthor, listAllPads, and listAuthorsOfPad, allowing disclosure, modification, or deletion of pads across the instance. This issue is fixed in version 3.1.0.
CVE-2026-72683 is a vulnerability in Elasticsearch where an authenticated user with privileges to invoke the simulate pipeline API can submit a request that creates a self-referential data structure. This causes an internal component to recurse indefinitely, leading to a fatal error that terminates the node process and results in denial of service. The flaw affects multiple Elasticsearch versions prior to patched releases. No known exploits are reported in the wild. A patch is available to address this issue.
The npm package mutex-lite version 1.4.2 is a malicious package impersonating the legitimate async-mutex library. It exports a similar Mutex API but includes hidden code that decrypts and executes an encrypted payload when triggered by a specific jobId value. This payload runs detached Node.js processes silently, potentially targeting Ethereum wallet operations via the bundled ethers library. This results in arbitrary code execution within applications that use the package and invoke the runExclusive method with the attacker-controlled jobId.
FUXA versions 1.3.2 and earlier contain a missing authorization vulnerability in the Node-RED integration. An unauthenticated remote attacker can obtain a signed guest token and access the Node-RED HTTP admin editor and flow deployment API without proper identity verification. This allows the attacker to deploy function nodes or invoke scripts, potentially gaining control over project data, configuration, scripts, and runtime helpers, including operating system commands if unsafe modules are enabled. The issue is fixed in version 1.3.3.