M-Y-Mo

**Name of the Vulnerable Software and Affected Versions** Docmost versions prior to 0.70.0 **Description** Docmost is open-source collaborative wiki and documentation software. The software is subject to a stored cross-site scripting (XSS) attack, which occurs when an application includes untrusted data in a web page without proper validation, allowing a malicious script to be permanently stored on the server. This issue is caused by improper handling of MIME type spoofing, where an attacker can misrepresent the file type of an uploaded file to trick the browser into executing it as a script. **Recommendations** Update to version 0.70.0.

**Name of the Vulnerable Software and Affected Versions** Sentry versions prior to 26.1.0 **Description** Sentry is a developer-first error tracking and performance monitoring tool. Versions prior to 26.1.0 have a cross-organization Insecure Direct Object Reference (IDOR) issue in the `GroupEventJsonView` endpoint. An Insecure Direct Object Reference occurs when an application uses user-supplied input to directly access objects, potentially allowing unauthorized access to data. **Recommendations** Update to version 26.1.0 or later.

**Name of the Vulnerable Software and Affected Versions** Sylius versions prior to 2.0.16 Sylius versions prior to 2.1.12 Sylius versions prior to 2.2.3 **Description** Sylius, an Open Source eCommerce Framework on Symfony, contains an authenticated Insecure Direct Object Reference (IDOR) issue in several shop LiveComponents. This is due to unvalidated resource IDs accepted via the #[LiveArg] parameters. Actions accepting resource IDs via #[LiveArg] and loading them with ->find() without ownership validation are affected. Specifically, the Checkout address FormComponent’s `addressFieldUpdated` action accepts an `addressId` via #[LiveArg], potentially exposing another user's personal information including first name, last name, company, phone number, street, city, postcode, and country. The Cart WidgetComponent’s `refreshCart` action and Cart SummaryComponent’s `refreshCart` action both accept a `cartId` via #[LiveArg], allowing direct access to order data such as order total and item count, subtotal, discount, shipping cost, taxes, and order total. Because sylius order contains both active carts and completed orders in the same ID space, the cart IDOR can expose data from all orders. **Recommendations** Update Sylius to version 2.0.16 or later. Update Sylius to version 2.1.12 or later. Update Sylius to version 2.2.3 or later.

**Name of the Vulnerable Software and Affected Versions** Arm Mali GPU kernel driver versions Bifrost r0p0 through r39p0 Arm Mali GPU kernel driver versions Valhall r19p0 through r39p0 Arm Mali GPU kernel driver versions Midgard r4p0 through r32p0 **Description** The issue is related to the mishandling of GPU memory operations, allowing unprivileged users to access freed memory. This can lead to a denial of service. The estimated number of potentially affected devices is not provided. There is no information about real-world incidents where this issue was exploited. The vulnerability is related to the use of memory after it has been freed, which can be exploited by a remote attacker. **Recommendations** For versions Bifrost r0p0 through r39p0, update to a version that properly handles GPU memory operations to prevent access to freed memory. For versions Valhall r19p0 through r39p0, update to a version that properly handles GPU memory operations to prevent access to freed memory. For versions Midgard r4p0 through r32p0, update to a version that properly handles GPU memory operations to prevent access to freed memory. As a temporary workaround, consider restricting access to the GPU kernel driver to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Swagger-Parser versions <= 1.0.30 Swagger codegen versions <= 2.2.2 **Description** A vulnerability in Swagger-Parser's yaml parsing functionality results in arbitrary code being executed when a maliciously crafted yaml Open-API specification is parsed. This affects the 'generate' and 'validate' commands in swagger-codegen and can lead to arbitrary code being executed when these commands are used on a well-crafted yaml specification. **Recommendations** For Swagger-Parser versions <= 1.0.30, update to a version greater than 1.0.30 to resolve the issue. For Swagger codegen versions <= 2.2.2, update to a version greater than 2.2.2 to resolve the issue. As a temporary workaround, consider restricting the use of the 'generate' and 'validate' commands in swagger-codegen until a patch is available.