Nextflow is a DSL for data-driven computational pipelines. From 25.09.2-edge until 25.10.6 and 26.04.3, nextflow auth login writes Seqera Platform OIDC bearer tokens to ${NXF_HOME:-~/.nextflow}/seqera-auth.config through AuthCommandImpl.writeConfig in plugins/nf-tower/src/main/io/seqera/tower/plugin/auth/AuthCommandImpl.groovy without setting restrictive file permissions, allowing the default umask 022 to create the file with mode 0644. On a multi-user POSIX host, a local user who can traverse the victim's home directory can read seqera-auth.config and impersonate the victim against Seqera Platform within the token's scope. Single-user systems and headless CI runners that do not use the interactive login flow are not affected. This issue is fixed in 25.10.6 and 26.04.3.
mise manages dev tools like node, python, cmake, and terraform. Prior to 2026.6.4, mise's trust feature gates config files (mise.toml, .tool-versions) through trust_check, but task-include files are loaded on a path that never reaches it. When a directory has a task-include dir (mise-tasks/, .mise/tasks/, …) but no config file, mise falls back to the default includes and renders each task's tera fields — and that tera environment has exec() registered. A {{ exec(command='…') }} in any rendered field runs arbitrary commands the moment the tasks are merely listed. There's no config file to gate on, so no trust prompt ever appears. Read-only commands trigger it: mise tasks, mise task ls, mise run, mise tasks --usage (the query shell completion runs on Tab). The victim only has to cd into a cloned repo and list or tab-complete a task. This vulnerability is fixed in 2026.6.4.
CWE-732 Incorrect Permission Assignment for Critical Resource vulnerability that could cause unauthorized disclosure of password hashes and potential account compromise when an attacker with privileged local access reads improperly protected system files.
motionEye (mEye) is an online interface for motion software, a video surveillance program with motion detection. Versions prior to 0.44.0 create the configuration file /etc/motioneye/motion.conf with 644 permissions (-rw-r--r--), making it readable by any local user on the system. This file contains sensitive data including the admin password hash, which can be leveraged by other vulnerabilities to escalate privileges. Additionally, per-camera configuration files (camera-*.conf) are also created with the same 644 permissions, potentially exposing camera-specific credentials and settings. The exposed SHA1 admin password hash can be cracked offline to recover the plaintext password, used directly to forge authenticated admin API requests via the signature authentication weakness (GHSA-45h7-499j-7ww3), and chained with the OS command injection flaw (CVE-2025-60787) to escalate a local unprivileged user to the Motion daemon user (often root), enabling full system compromise. This issue has been fixed in version 0.44.0.
# Pi auth.json writes could briefly expose stored credentials to local users
Pi stored API keys and OAuth credentials in `auth.json`. A race condition in the file write path could briefly create or rewrite this file with permissions derived from the process umask before tightening the file to owner-only permissions.
## Info
The affected credential storage code wrote `auth.json` and then corrected the file mode in a separate operation. During the interval between those operations, a local user who could read and traverse the Pi agent configuration directory could potentially read the file before its permissions were restricted.
The file can contain API keys, OAuth access tokens, and OAuth refresh tokens for configured providers. The affected behavior was present in the original `auth.json` credential storage implementation and thus affects both the original `@mariozechner/pi-coding-agent` package as well as `@earendil-works/pi-coding-agent`.
## Impact
Exploitation requires local access to the same machine and read/traverse access to the victim's Pi agent configuration directory. Users whose `~/.pi/agent` directory is private to their account are less exposed. The main impact is disclosure of stored provider credentials, which may allow use of the configured provider accounts according to the privileges of those credentials.
This is not remotely exploitable by itself.
## Affected versions
- Affected: `@mariozechner/pi-coding-agent >= 0.28.0, <= 0.73.1`
- Affected: `@earendil-works/pi-coding-agent >= 0.74.0, < 0.78.1`
- Patched: `@earendil-works/pi-coding-agent >= 0.78.1`
## The solution
Version 0.78.1 changed the credential storage writes to create `auth.json` with mode `0600` at open time. The fix applies to initial file creation and credential save paths, including OAuth token refresh writes.
## Recommendations
Upgrade to `@earendil-works/pi-coding-agent` version 0.78.1 or later. Users still on the deprecated `@mariozechner/pi-coding-agent` package should migrate to the `@earendil-works/pi-coding-agent` package and install version 0.78.1 or later.
After upgrading, rotate any credentials that may have been exposed on multi-user systems where the Pi agent configuration directory was readable by other local users.
## Workarounds
If upgrading immediately is not possible, restrict the Pi agent configuration directory so only the owning user can traverse it, restrict `auth.json` to owner-only permissions, and run Pi with a restrictive umask such as `077` until the upgrade is complete.
## Timeline
- 2026-05-29: Report received
- 2026-06-02: Fix committed
- 2026-06-04: Fixed version released
- 2026-06-08: Advisory published
## Credits
Reported by Paul Urian and Cosmin Alexa of CrowdStrike.
CVE-2026-12957 is a high-severity vulnerability in Amazon Web Services Language Servers before version 1.65.0. It involves improper permission assignment that allows arbitrary code execution if a local user opens a maliciously crafted workspace and trusts it when prompted. The issue affects all supported platforms and requires user interaction to exploit. Upgrading to version 1.65.0 or later mitigates the risk.
gonic is a music streaming server / free-software subsonic server API implementation. Prior to version 0.21.0, a logic error in `ServeCreateOrUpdatePlaylist` allows any authenticated Subsonic user (including non-admin) to write playlist M3U content to an attacker-controlled absolute filesystem path on the gonic host, and to create intermediate directories with `0o777` permissions. The bug is independent of CVE-2026-49338 and CVE-2026-49339. It is an unreachable guard clause combined with no path containment in `Store.Write`. Version 0.21.0 patches the issue.
Steeltoe.Configuration.Abstractions versions 4.0.0 through 4.1.0 improperly store TLS client credentials from MySQL or PostgreSQL service bindings in world-readable temporary files on Linux systems. These files are created with permissions that allow other users to read sensitive key material and are not deleted after use. Version 4.2.0 addresses this issue by patching the insecure file handling. The vulnerability has a medium severity rating with a CVSS score of 4.7.
CVE-2026-0271 is a medium severity privilege escalation vulnerability in the Palo Alto Networks Prisma Access Agent on Linux devices. It allows a local user to execute code with elevated privileges due to incorrect permission assignment of critical resources. This vulnerability does not affect Prisma Access Agent on Windows, macOS, iOS, Android, or ChromeOS. No patch or official remediation guidance has been provided yet.
CVE-2026-50590 is a vulnerability in Mimecast Incydr versions including 1.2.0 where incorrect permission assignment allows arbitrary file access. This issue is classified under CWE-732, indicating improper permission settings for critical resources. The vulnerability has a medium severity with a CVSS score of 4.5. No official patch or remediation guidance has been provided yet.
Broadcast events allow malicious software to rewrite the device's default Mobile Device Management (MDM) endpoint address, shifting administrative ownership to an external attacker.
CVE-2026-10591 is a high-severity vulnerability in AWS Kiro IDE versions before 0.11. It involves incorrect permission assignment in the file write tool, allowing remote unauthenticated actors to execute arbitrary commands by writing to execution-sensitive paths such as .vscode/tasks.json. This can lead to automatic execution of malicious instructions when a folder is opened. The issue is fixed in version 0.11 and later.
Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow backup files to be publicly exposed when the administrator configures their path within the NGINX webroot. This vulnerability allows an attacker with network access to directly download backup ZIP files via ‘http(s)://[server]/download/…’ without requiring authentication. This exposes highly sensitive information that can lead to server impersonation, unauthorized access to databases, and lateral movement.
CVE-2026-7480 is a high-severity vulnerability in ASUS System Control Interface version 3.1.59.0 and earlier. It involves incorrect permission assignment for a critical resource, enabling a local user to elevate privileges to SYSTEM by crafting a malicious RPC call that bypasses validation. The vulnerability has a CVSS 4.0 base score of 7.3. No official patch or remediation guidance has been provided by ASUS, and no known exploits have been reported in the wild.
Incorrect permission assignment for a critical resource in Armoury Crate allows a local user to bypass the driver’s validation mechanism, resulting in unauthorized read and write access to physical memory.Refer to the '
Security Update for Armoury Crate App ' section on the ASUS Security Advisory for more information.
A Local Privilege Escalation (LPE) vulnerability affects Acer NitroSense software versions prior to 3.01.3052. The vulnerability stems from the the PSAdminAgent service, which creates a Named Pipe with a weak Access Control List (ACL). This allows any authenticated local user to connect and send commands. Because the service does not check the caller's privileges before running file deletion commands, a low-privileged local user can exploit this to delete arbitrary files with system authority.
Hitachi Vantara Pentaho Data Integration & Analytics versions before 10.2.0.6 and 11.0.0.0, including 9.3.x and 8.3.x, does not apply ACLs on certain API endpoints related to platform mail notfications.
CVE-2026-25112 is a high-severity vulnerability in Genetec RabbitMQ versions prior to 3.13.7.19. It involves improper specification of permissions for a security-critical resource, allowing unintended actors to read or modify it. This can lead to privilege escalation without requiring user interaction. The vulnerability impacts confidentiality, integrity, and availability of the affected system.