CVE-2026-112498 is a high-severity vulnerability in Apple macOS that allows an application to potentially break out of its sandbox due to an access control issue. This flaw could lead to a sandbox escape, compromising system confidentiality and integrity. Apple has addressed the vulnerability by adding additional sandbox restrictions. The issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, and macOS Tahoe 26.7.2.
CVE-2026-112569 is a high-severity vulnerability in Apple macOS that allows an application to potentially escape its sandbox due to an access control issue. The flaw affects multiple macOS versions prior to 15.8.2, 26.7.2, and 27.2. Exploitation requires local user interaction and can lead to complete compromise of confidentiality and integrity without impacting availability. Apple addressed the issue by adding additional sandbox restrictions in the fixed versions.
CVE-2026-112624 is a vulnerability in Apple iOS and iPadOS that allows an app to bypass Privacy preferences, potentially leading to unauthorized access to user privacy settings and compromising data confidentiality. The issue has been addressed with improved checks and fixed in iOS 26.7.2, iOS 27.2, iPadOS 26.7.2, iPadOS 27.2, and related macOS and visionOS versions.
CVE-2026-95628 is a path traversal vulnerability in the Apache Camel Docling component affecting versions from 4.15.0 before 4.18.5 and from 4.19.0 before 4.22.2. The issue arises because the validation method intended to restrict path arguments to a safe directory only checked for relative traversal sequences and did not block absolute paths. This allows an attacker able to control custom arguments to specify absolute paths, potentially accessing directories outside the intended scope. The vulnerability is fixed in Apache Camel versions 4.18.5 and 4.22.2. Users on unsupported versions must upgrade or apply mitigations to prevent exploitation.
CVE-2026-95629 is a path traversal vulnerability in the Apache Camel Docling component affecting versions from 4.15.0 before 4.18.5 and from 4.19.0 before 4.22.2. The issue arises because the CamelDoclingOutputFilePath header value is passed verbatim to the external docling tool's --output flag without proper normalization or directory confinement, allowing an attacker able to set this header to write conversion output files to arbitrary directories writable by the Camel process. The vulnerability is mitigated by upgrading to Apache Camel versions 4.18.5, 4.22.2, or later, which introduce an outputBaseDirectory option to restrict output paths. For versions that cannot be upgraded immediately, users should ensure the header is not influenced by external inputs and is filtered appropriately.
The Pixel Tag Manager for WooCommerce WordPress plugin before 2.2.3 does not perform a capability check in one of its AJAX actions, and exposes the nonce protecting it to any user able to access the admin dashboard, allowing users with a role as low as Contributor to overwrite the Pixel Tag Manager for WooCommerce WordPress plugin before 2.2.3's tracking configuration and have arbitrary JavaScript executed in the browsers of all visitors, including administrators.
PraisonAI versions from 4.6.10 up to but not including 4.6.59 contain an OS command injection vulnerability. This occurs because certain file operation commands are constructed using raw path arguments that are passed to shell-backed compute providers without proper sanitization. An attacker able to control these path arguments can execute arbitrary shell commands on the compute environment, either on the host or inside a Docker container. The issue is fixed in version 4.6.59.
An attacker able to supply a crafted XML document to an application using QXmlStreamReader can cause disproportionate CPU consumption during parsing, making the application unresponsive (denial of service). Exploitation requires only that the application parse attacker-influenced XML; no authentication, privileges, or user interaction beyond ingesting the input are needed. There is no loss of confidentiality or integrity — no data disclosure, data modification, or code execution — and the impact is contained to the affected process.
Incus versions 7.0.0 before 7.0.2 and 7.1.0 before 7.5.0 contain a critical path traversal vulnerability. This flaw allows clients with the ability to create instances to write arbitrary files on the host system by exploiting unvalidated custom volume names in instance backup index.yaml files. Attackers can craft backups with directory traversal sequences to create root-owned directories with attacker-controlled content, potentially leading to full host compromise.
A flaw was found in the `lm-evaluation-harness` component of Red Hat OpenShift AI. An authenticated user, able to submit an evaluation job, could exploit this by providing a malicious model URL in the `JobSpec`. This vulnerability allows for the disclosure of the tenant's model authentication secret to an attacker-controlled external listener. Additionally, it enables Server-Side Request Forgery (SSRF) attacks against internal network endpoints reachable from the evaluation job pod.
### Summary
`launch-editor` forwarded file paths directly to editors without sanitization. If a path resembles a CLI flag, editors like Vim may interpret it as a command, potentially causing unintended file overwrites or command execution.
### Impact
#### Direct `launch-editor` users
Only apps that match all of the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with `+` or `-` in the working directory
- The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- The first argument of `launchEditor` can start with `+` or `-` or the user is using WSL
#### `launch-editor-middleware` users
Only apps that match the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with `+` or `-` in the working directory
- The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- launch-editor older than v2.2.0 is used, or the user is using WSL
#### Vite users
Only apps that match the following conditions are affected:
- The attacker is able to create a file system entry (e.g. a file or directory) starting with `+` or `-` in the working directory
- The user uses or the app specifies any of the following editors:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
- The user is using WSL
### Details
`launchEditor(file)` function passes the file name as-is to the editor if the file with that file name exists. If the file name starts with `-` (also `+` for Vim), the editor treats them as flags rather than positional arguments. For example, Vim treats arguments starting with `+` as an Ex command. As a result, an existing relative directory such as:
```
+call writefile(["SAFE_MARKER"],"LAUNCH_EDITOR_MARKER")|qa!
```
is not treated as a filename when passed to Vim. Vim executes the embedded Ex command.
The following editor has a potentially destructive operation exposed to the CLI arguments:
- Vim (including gVim)
- MacVim
- Emacs (including Emacsclient)
- Notepad++ (only if using a plugin exposing dangerous operations via plugin messages)
`launch-editor-middleware` v2.2.0+ converts the passed file path to an absolute path so those are not affected as long as the user is not using WSL. For WSL, `launch-editor` converts the paths to relative paths internally, so those are still affected.
Vite 2.0.0+ uses `launch-editor-middleware` v2.2.0+ so the WSL users are only affected.
A vulnerability was found in DrayTek Vigor2960 1.5.1.6 Revision 8218. This vulnerability affects unknown code of the file /cgi-bin/mainfunction.cgi of the component Apmupload. Performing a manipulation of the argument action results in path traversal. The attack is possible to be carried out remotely. The exploit has been made public and could be used. Upgrading to version 1.5.1.7 is able to resolve this issue. Upgrading the affected component is advised. The vendor explains: "2960 1.5.1.7 has corrected many security issues. And 2960 is EoS with limited support, only major issues would be reviewed(e.g. unauthenticated vuln.)". This vulnerability only affects products that are no longer supported by the maintainer.
A vulnerability has been found in DrayTek Vigor2960 1.5.1.6 Revision 8218. This affects the function uploadlangs of the file /cgi-bin/mainfunction.cgi of the component Upload Endpoint. Such manipulation leads to command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.5.1.7 is able to mitigate this issue. It is recommended to upgrade the affected component. The vendor explains: "2960 1.5.1.7 has corrected many security issues. And 2960 is EoS with limited support, only major issues would be reviewed(e.g. unauthenticated vuln.)". This vulnerability only affects products that are no longer supported by the maintainer.
CVE-2026-86961 is a high-severity vulnerability in Apple iOS and iPadOS that involves a race condition allowing a malicious app to potentially break out of its sandbox. This issue was addressed by Apple with additional validation and fixed in iOS 27 and iPadOS 27. The vulnerability could lead to complete compromise of confidentiality, integrity, and availability if exploited.
CVE-2026-112991 is a server-side request forgery (SSRF) vulnerability in the html_to_markdown expansion module of MISP misp-modules. The vulnerability arises from an incomplete URL validation function that fails to block several critical internal IP address ranges. An authenticated user able to create or modify attributes triggering this module can cause the MISP server to make requests to internal network addresses, potentially exposing sensitive data from internal services. The vulnerability affects versions from 0 up to and including 3.0.12.
Bulletin ID: 2026-052-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 07/06/2026 13:45 PM PDT Description: Amazon mcp-gateway-registry is an open-source gateway and registry for Model Context Protocol (MCP) servers, providing centralized discovery, authentication/authorization, and proxying of MCP tools for AI agents. We identified CVE-2026-14471, an issue in the metrics-service retention policy management component where a caller-supplied table_name value is interpolated into SQL statements in identifier position without proper neutralization. An authenticated remote user is able to supply a crafted table_name value to execute arbitrary SQL queries against the metrics database. This allows the user to read stored data (including API key material) and to delete or alter stored data. Impacted versions: >=1.0.3 AND <=1.0.12 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
A deserialization of untrusted data vulnerability exists in Apache Camel's camel-hazelcast component in versions from 4.0.0 before 4.18.5 and from 4.19.0 before 4.22.1. Certain configuration paths fail to apply Java deserialization filters, allowing an attacker able to publish data into the connected Hazelcast cluster to cause arbitrary Java object deserialization, potentially leading to remote code execution. Hazelcast clusters lack authentication and TLS by default, increasing exposure. Upgrades to Apache Camel 4.23.0, 4.22.1, or 4.18.5 fix this issue. Workarounds include supplying explicit Hazelcast configurations with deserialization filters, injecting pre-built Hazelcast instances, setting JVM-wide serialization filters, and enabling Hazelcast cluster authentication and TLS.
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description.
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel CXF component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When a route behind a CXF SOAP consumer failed with an exception the service contract does not declare, the exception was described back to the SOAP client in the fault: CXF copies the message into the SOAP faultstring, and can be configured to place the stack trace in the fault detail. An external caller able to provoke a failure could therefore read internal detail about the deployment - class and package names, and whatever the exception message carries. Declared faults, annotated @WebFault, are a different matter: those are part of the published contract that clients are written against, and suppressing them would break the service rather than protect anything.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, replaces an undeclared route failure with a generic fault carrying no class name, message or stack trace. Faults the contract declares are reported exactly as before. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, declare the exceptions the service is allowed to report and map every other failure onto one of them in an onException handler, so no undeclared exception reaches the fault.