Joomla Extension - phoca.cz - Stored XSS through YouTube links in Phoca Gallery extension 4.2.0-6.1.6 - The YouTube upload feature did not validate the supplied video URL and embedded the derived video ID without escaping, allowing users with frontend upload permission to inject HTML attributes into the gallery detail view.
Joomla Extension - vi-solutions - Improper per-form authorization for field management in Visforms extension 1.0.0-5.6.4, 6.0.0-6.2.1 - Field creation, editing and ordering checked permissions against a user-supplied form ID instead of the form the field belongs to, allowing backend users to manage fields of other forms.
Quasar before 2.35.3 contains a DOM clobbering vulnerability that allows attackers to break native wrapper detection by injecting HTML elements named Capacitor, cordova, or StatusBar. Attackers can place markup such as a div with id Capacitor into server-rendered or pre-rendered HTML so app.use(Quasar) throws and the application never mounts, or openURL() and AddressbarColor.set() throw.
Tandoor Recipes before 2.7.4 contains a server-side request forgery vulnerability that allows space admins to reach internal hosts because Nextcloud.get_client builds WebDAV clients from Storage.url without calling safe_request. Attackers can create a NEXTCLOUD storage via POST /api/storage/ pointing at internal hosts, import a file, then call GET /api/get_recipe_file/<id>/ to read internal service or cloud metadata responses.
node-soap before 1.14.1 contains a prototype pollution vulnerability in WSDL.xmlToObject that allows unauthenticated attackers to pollute Object.prototype via an XML element with id="__proto__". Attackers can send a single crafted SOAP request to a soap.listen() server, or return a malicious response to a client, causing all subsequent SOAP parsing to fail until process restart.
A use-after-free vulnerability in the Linux kernel's nvmet_pr_preempt() function was identified and fixed. The flaw involves reading freed memory when handling reservation preemption notifications, potentially causing memory corruption or kernel instability. The issue arises because the old registrant is freed asynchronously but accessed afterward without proper synchronization. The fix involves passing the host ID of the controller that sent the command instead of the freed registrant to avoid accessing freed memory.
Mattermost Plugins versions <=12.-1 11.0.11 11.11.7 11.2.10.0 fail to check for a nil result after decoding the HTTP request body which allows an authenticated user to crash the Zoom plugin process, causing denial of service, via sending a JSON null body to the plugin's action endpoints. Mattermost Advisory ID: MMSA-2026-00722
Mattermost Plugins versions <=12.-1 11.11.7 11.2.10 11.1.11.0 fail to enforce the GitLab project permission check for confidential issues when the project is publicly visible which allows an authenticated user with no GitLab membership in the project to obtain the contents of confidential issues, including title, description, author, and URL via subscribing a channel to the parent public GitLab group with the confidential_issues feature and waiting for a confidential issue webhook event. Mattermost Advisory ID: MMSA-2026-00738
Mattermost versions 11.7.x <= 11.7.11, 11.10.x <= 11.10.2, 11.11.x <= 11.11.1 fail to bound the number of records a single GraphQL request may hydrate which allows an authenticated user to exhaust server memory and cause a denial of service via a small query that repeats the runs field under many aliases. Mattermost Advisory ID: MMSA-2026-00767
A time-of-check to time-of-use (TOCTOU) race condition vulnerability exists in the Linux kernel's drm/panthor component. The flaw occurs because panthor_group_destroy() checks a GROUP_REGISTERED mark and then erases an entry without holding the necessary lock across both operations. This can lead to a use-after-free condition if another thread destroys the handle and a concurrent creation reuses the freed ID.
MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace("/\s+/", "", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic.
The vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide.
The fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster 'meta' keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances.
A vulnerability in the Linux kernel's NFS server (NFSD) causes it to send the CB_RECALL_ANY callback operation to NFSv4.0 clients, which only support CB_GETATTR and CB_RECALL. This results in the client marking its callback channel as down, preventing delegation renewals and further delegations until the client re-establishes its client ID. The issue affects certain Linux kernel versions and has been fixed in later releases.
CVE-2026-99351 is a vulnerability in the Linux kernel's sunrpc subsystem where empty auth.unix.gid replies were incorrectly treated as valid positive entries. This caused the system to strip all supplementary groups from a user after a failed group ID lookup, potentially affecting access control for up to 30 minutes. The issue was fixed by treating empty group replies as negative entries, preserving existing group credentials during such failures.
Cozy Cloud cozy-stack versions 1.6.62 through 1.6.68 contain an authorization bypass vulnerability in the shared-drive move handler. This flaw allows authenticated users who own a shared drive to manipulate the move source by specifying another instance's domain and directory ID, enabling unauthorized access to and deletion of files in the victim's file tree. The vulnerability is fixed in version 1.6.69.
A vulnerability in JTL-Shop's checkout process allows an attacker, including guests, to manipulate the delivery address ID stored in the session. The system does not verify that the delivery address belongs to the ordering customer, enabling attackers to attach another customer's delivery address to their order. This can lead to exposure of personal information such as name, address, and possibly other contact details in order confirmations and customer accounts. The sequential nature of address IDs allows attackers to enumerate addresses. This flaw may result in goods being shipped to incorrect addresses.
The Strava datasource plugin's resource handler POST /strava-api forwards a client-supplied endpoint string, and its query parameters, to the Strava API (https://www.strava.com/api/v3/<endpoint>) without validation.
When the datasource is not in OAuth pass-through mode, the request is made with the access token stored on the datasource, not the caller's identity. Grafana authorises plugin resource calls only on the datasources:query permission, which Viewers have by default. Any such caller could therefore request any Strava API path the connected account's OAuth grant allows, for example athlete/clubs or routes/{id}, and read the response.
The plugin's frontend (stravaApi.ts) only needs a fixed set of paths: athlete, athlete/activities, activities/{id}, activities/{id}/streams and segments/{id}.
Requests to Strava are GET only, so the issue is read-only.
Affected: plugin versions 1.2.0 through 1.7.2. The fix restricts endpoint to those five patterns and is pending release. The check runs before the access token is resolved, so a rejected request never causes a token refresh or any call to Strava. Paths with .. segments are rejected as well.