A flaw was found in KubeVirt/containerized-data-importer. When a VirtualMachine with an embedded DataVolumeTemplate carrying the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant, the service-account clone authorization check can be bypassed, allowing a PVC from another namespace to be cloned into the tenant's namespace without the required permissions. This can result in cross-tenant data disclosure.
svglib reads SVG files and converts them to other formats. Prior to 2.3.1, the svg2rlg() renderer recursively expands nested SVG <use> references by deep-copying each referenced subtree; SvgRenderer.renderUse() in src/svglib/svglib.py calls xlink_href_target(), which rejects direct cycles but permits acyclic reference graphs with repeated fan-out. A small attacker-controlled SVG can therefore trigger exponentially increasing node expansion, consuming excessive CPU and memory in any application that renders it without a non-default option; HTML-to-PDF workflows using xhtml2pdf can reach the same renderer when an embedded data:image/svg+xml image in an HTML img element is passed to pisa.CreatePDF(). This issue is fixed in 2.3.1.
CVE-2026-79751 is an improper privilege management vulnerability in snct-SportEase web application versions prior to 1.3. An authenticated user with an incomplete profile can assign themselves as a class representative for any class in the active event by submitting a chosen class_id during profile completion. This grants unauthorized access to view roster details and modify competition-team assignments for that class. The elevated representative role cannot be revoked via the API and requires direct database or out-of-band remediation. The issue is fixed in version 1.3.
Microsoft has been recognized as a Leader in the 2026 Gartner Magic Quadrant for Security Information and Event Management (SIEM) with its cloud-native SIEM product, Microsoft Sentinel. Sentinel integrates security data, advanced analytics, automation, and threat intelligence to provide comprehensive visibility and proactive threat detection across complex, multicloud environments. Microsoft also introduced the Integrated Security Operations Center (ISOC) in Microsoft Defender, which unifies SIEM with extended detection and response (XDR), threat intelligence, and posture management to enable faster, coordinated attack disruption. This integrated approach helps automatically contain threats such as ransomware and business email compromise, often disrupting ransomware attacks within 30 seconds. AI and automation capabilities in Sentinel reduce manual workload and accelerate investigations, enabling security teams to act more effectively against sophisticated threats.
Tapo provides Rust and Python APIs and an MCP server for TP-Link Tapo smart devices. From 0.3.1 until 0.5.0, the Streamable HTTP implementation in tapo-mcp/src/server.rs calls disable_allowed_hosts() without replacement Host or Origin validation, while TAPO_MCP_API_KEY remains optional for a listener that can bind to all interfaces. A malicious website can use DNS rebinding to send same-origin browser requests to the victim's local or LAN Tapo MCP listener when it runs without an API key. The attacker can invoke exposed tools including control_device for smart-device actuation and take_snapshot for configured cameras. Deployments with TAPO_MCP_API_KEY set are not affected by the unauthenticated path, and exploitation requires a running listener configured with real Tapo credentials and devices, plus victim interaction with the malicious site. This issue is fixed in version 0.5.0.
memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.2 until 0.1.34, concurrent surfacing RPC failures can start more than one reconnect for the same dirty session because concurrent LTM recovery is not uniquely owned by a session generation. Cancellation during a post-reconnect retry can also leave the replacement transport reusable after an interrupted protocol exchange, causing session-state integrity loss or local service degradation. The duplicate-reconnect subcase was introduced in 0.1.24, while the cancellation-recovery subcase affects the broader listed range. This issue is fixed in version 0.1.34.
The IPv6 Neighbor Discovery code in subsys/net/ip/ipv6_nbr.c flushes a neighbour's queued packets at the end of handle_ra_input(). The Source Link-Layer Address Option (SLLAO) is optional in a Router Advertisement; when it is absent, handle_ra_input() still obtains (or creates) a neighbour cache entry for the RA source via net_ipv6_nbr_add() with a NULL link-layer address, so the entry stays in NET_IPV6_NBR_STATE_INCOMPLETE with nbr->idx == NET_NBR_LLADDR_UNKNOWN. The pending-packet drain loop was entered unconditionally for that unresolved entry.
Each net_send_data() in the drain loop runs synchronously into net_ipv6_prepare_for_send(), which finds the neighbour still unresolved and hands the packet to net_ipv6_send_ns(), which puts it straight back onto the same pending_queue. The loop therefore never sees an empty queue. With a single queued packet it transmits a fresh Neighbor Solicitation on every iteration; with two or more queued packets it rotates the queue with no allocation and no transmission at all. The loop runs in the network RX thread with the global IPv6 neighbour mutex held.
An unauthenticated attacker on the same link can trigger this deterministically: advertise itself as a router, induce the victim to queue off-link traffic toward that router (for example by sending echo requests with an off-link source address) while leaving the solicitation unanswered, then send a second Router Advertisement without an SLLAO option. Spoofing an SLLAO-less RA from the legitimate router's link-local address has the same effect whenever traffic is queued for it. Router Advertisements are processed with no authentication whenever CONFIG_NET_IPV6_ND is enabled, which is the default for IPv6-capable builds.
The result is a permanent denial of service: the RX thread spins forever holding the neighbour lock, so all IPv6 transmission and every other user of the neighbour cache blocks, and the Neighbor Advertisement that would resolve the entry can no longer be processed. The ipv6_ns_reply_timer work item that would normally drop the pending packets also blocks on the same mutex. In the single-packet variant the loop additionally floods the link with Neighbor Solicitations. The fix restricts the flush to resolved entries (nbr->idx != NET_NBR_LLADDR_UNKNOWN), leaving the packets queued for the NS reply timeout. There is no memory-safety impact.
CVE-2026-77332 is a vulnerability in memtomem-stm versions 0.1.0 through 0.1.33 where untrusted long-term and working-memory fields are not properly serialized as inert data. This allows Markdown or HTML-compatible structures to be introduced into the surfaced-memory envelope, potentially misleading consuming AI agents by altering structural boundaries or visually concealing content. The issue is fixed in version 0.1.34.
Budibase is an open-source low-code platform. Prior to 3.50.0, a BASIC application user, or an unauthenticated visitor to a public write form, can store markup in a shared external datasource that a builder or administrator later evaluates in any Handlebars binding Preview that surfaces the value, including the Data-section Formula column editor or any binding drawer. jsonFormatter.format() in packages/frontend-core/src/utils/jsonFormatter.ts leaves raw strings and object keys unescaped, while packages/builder/src/components/common/bindings/EvaluationSidePanel.svelte inserts the formatted result as raw HTML. The Handlebars SafeString path preserves the attacker-controlled value, and the Builder origin lacks a Content-Security-Policy that would block the resulting script. This permits stored script execution in the higher-privileged builder or administrator session rather than the writer's own role, allowing privileged Builder API actions and workspace data access. This issue is fixed in versions 3.50.0 and 4.0.0.
Budibase versions prior to 3.50.0 have an improper access control vulnerability in the public POST /api/global/users/init endpoint on self-hosted single-tenant deployments. An unauthenticated attacker can specify an arbitrary tenantId to bypass initialization guards, causing creation of tenant-specific CouchDB databases and global-administrator documents without authentication. This can lead to resource exhaustion and latent privileged records. The vulnerability is fixed in version 3.50.0.
CVE-2026-35376 is a time-of-check to time-of-use (TOCTOU) vulnerability in the recursive relabeling functionality of the 'chcon' utility in uu_chcon versions prior to 0.10.0. The issue arises because recursive targets were resolved with a fresh path lookup not anchored to the traversal directory file descriptor, allowing a privileged user to redirect the relabel operation to unintended filesystem objects via rename or symlink races. This flaw was fixed in version 0.10.0 by anchoring recursive relabel resolution to the traversal directory file descriptor.
The uu_env utility incorrectly rejects certain backslash sequences within single-quoted strings in its -S/--split-string parsing, diverging from GNU env behavior. Specifically, uu_env treats sequences like '\x' as invalid, whereas GNU env keeps backslashes literal except for specific escapes. This issue affects uu_env versions prior to 0.10.0 and has been fixed in version 0.10.0. The vulnerability has a low severity rating and does not impact confidentiality or integrity but may cause availability issues due to errors.
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to donor account account takeover in all versions up to, and including, 4.17.0. This is due to the plugin not properly validating a donor's identity prior to updating the password of a linked WordPress account. The donation receipt processes an attacker-controlled first name through the V3 template engine and then reprocesses the result through the legacy `{meta_donor_*}` engine, which can disclose the donor's email-access bearer token. The donor-dashboard password endpoint accepts that token by itself and calls `wp_set_password()` for the WordPress user linked to the donor. This makes it possible for unauthenticated attackers to reset the password of any WordPress account linked to a GiveWP donor record and gain access to that account. If the linked account is an administrator, the attacker can achieve full site compromise and remote code execution through standard administrator functionality. A published GiveWP form with a usable gateway, enabled donor email access (enabled by default), knowledge of the donor email address, and an account already linked to the targeted donor record are required. NOTE: This vulnerability can be chained with CVE-2026-82676 to satisfy the administrator donor pre-requisite for a targeted administrator user attack.
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.16.7.2. This is due to missing nonce validation on the `give_render_donor_view()` function. This makes it possible for unauthenticated attackers to reassign an arbitrary GiveWP donor record to an arbitrary WordPress user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The resulting association changes donor-account ownership and can satisfy the linked-donor precondition for a separately tracked account-takeover vulnerability (CVE-2026-82675).
The 'split' utility in uu_split versions prior to 0.10.0 contains a time-of-check to time-of-use (TOCTOU) vulnerability in its output file handling. The program checks if the input and output paths are identical before opening the output file, but opens the output with truncation after the check, allowing a race condition. This race can lead to truncation or overwriting of a file different from the intended output, including the input file or other accessible files. This issue is fixed in version 0.10.0 by hardening the output open path against TOCTOU swaps.
Incorrect privilege assignment in the user and group reconciliation logic in AWS ssosync before 2.9.5 might allow an authenticated remote user who is assigned a reused Google Workspace e-mail address or group name to inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity, via automatic synchronization of that Google Workspace account or group.
To remediate this issue, users should upgrade to version 2.9.5 or later.
CKAN versions prior to 2.10.11 and between 2.11.0 and 2.11.5 are affected by a session fixation vulnerability in the web user registration form when configured with server-side session storage. This allows an attacker who can set or steal a session cookie to fixate a session. The vulnerability has been fixed by regenerating session identifiers after registration in versions 2.10.11, 2.11.6, and 2.12.0. Workarounds include using the default cookie-based session storage or disabling web user registration.
The netty-incubator-codec-ohttp library contains a vulnerability where OHTTP codecs retain consumed outer cumulation buffers after completed exchanges. This retention causes the codec to hold onto large buffers for the lifetime of idle keep-alive connections, potentially leading to memory pressure across many such connections. The issue affects versions from 0.0.20.Final up to but not including 0.0.27.Final. A fix is available in version 0.0.27.Final.
Mattermost versions 11.11.x <= 11.11.1, 11.7.x <= 11.7.14, 11.10.x <= 11.10.4 fail to restrict the broadcast scope of group WebSocket events to sessions permitted to read the group which allows an authenticated user, including guests, to obtain the display name, description, member count and member IDs of non-referenceable groups via the received_group event emitted when a group is created, updated, deleted or restored. Mattermost Advisory ID: MMSA-2026-00731