Zammad before 7.2.3 contains a missing authorization vulnerability that allows authenticated customers to delete agents' shared ticket drafts by supplying a shared_draft_id. Attackers can create tickets via POST /api/v1/tickets or reply to accessible tickets referencing a draft id, destroying draft text prepared by agents.
Apache ZooKeeper contains an improper authorization vulnerability in its SASL authentication on the client port. When enabled, the server grants any client-requested authorization identity without verifying it against the authenticated principal if the principal is not covered by auth_to_local rules. This allows an authenticated client to assume arbitrary SASL identities, including superuser access if the identity matches a configured superUser. The issue is fixed in versions 3.8.8 and 3.9.7.
Parse Server versions from 9.7.0 up to but not including 9.10.5 contain an authorization flaw involving installation update misdirection via the X-Parse-Installation-Id header. This flaw allows attackers who know another installation's object ID to trigger protected field processing on that installation while writing data elsewhere, when the protectedFieldsTriggerExempt feature is enabled. The issue is fixed in version 9.10.5.
Apache ActiveMQ versions from 6.0.0 before 6.3.3 and before 5.19.12 contain an improper input validation vulnerability. The broker does not verify that user-provided connection IDs match the authenticated user, allowing authenticated clients to spoof other users' connection, session, and consumer IDs. This enables unauthorized consumption from another user's temporary queues or topics, disruption of live subscriptions by tearing them down, and permanent deletion of unacknowledged messages via forged acknowledgments. The issue is fixed in versions 6.3.3 and 5.19.12.
phpMyFAQ 4.2.0-alpha before 4.2.0-RC.2 contains an information disclosure vulnerability that allows authenticated frontend users to receive restricted FAQ titles by subscribing to Web Push notifications. When editors publish user/group-restricted FAQs, WebPushService::sendToAll() delivers the question, FAQ id, category, and slugified URL to every subscriber, bypassing the FAQ ACL.
phpMyFAQ before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains an authentication bypass in password reset, letting external-identity accounts receive local passwords. Attackers with mailbox access can request reset tokens for OIDC, Keycloak, Entra ID, LDAP, SSO, or WebAuthn accounts and log in locally, skipping IdP MFA and deprovisioning.
phpMyFAQ 4.1.0 before 4.1.12 and 4.2.0-alpha before 4.2.0-RC.2 contains a missing authorization vulnerability that exposes restricted and inactive category metadata to unauthenticated visitors. Attackers can enumerate category IDs via /category/{id}/{slug}.html or query /api/v4.0/categories to read names, descriptions, images and FAQ counts of restricted categories.
This vulnerability in jackson-databind version 4.0 involves unbounded growth of the type ID cache in the TypeDeserializerBase component, which retains every unknown raw type ID. This behavior can lead to resource exhaustion due to uncontrolled memory consumption.
This vulnerability, identified as CVE-2026-90425, relates to the iommu/tegra241-cmdqv component requiring exactly one Stream ID for a vSID. The affected product is Microsoft software version 4.0. No detailed technical or impact information is provided in the available data.
CVE-2026-35371 is a vulnerability in the uutils coreutils id command related to misleading identity reporting when using pretty print mode. The issue involves incorrect or deceptive output of identity information, which may affect user understanding or system auditing. No CVSS score or detailed impact information is provided.
CVE-2026-35370 is a vulnerability in uutils coreutils id version 4.0 involving incorrect access-control decisions due to misrepresented group membership. The flaw relates to improper authorization checks that could lead to unauthorized access or privilege escalation. No CVSS score or detailed impact information is provided. There is no indication of active exploitation or available patches at this time.
CVE-2026-104047 is an information disclosure vulnerability in SSSD version 4.0 related to query injection in Entra ID lookups. The vulnerability could allow unauthorized access to sensitive information through crafted queries. No CVSS score or detailed impact information is provided.
LightSaml versions 4.6.1 through 5.0.0 contain a signature validation flaw allowing signature wrapping bypass. The vulnerability arises because LightSaml collects direct-child assertions for validation, but the underlying XML signature library (xmlseclibs) validates the signature against the first ID-bearing element in the entire document, which may differ. This discrepancy enables an attacker to present a forged assertion with attacker-controlled claims that appear signed by reusing a genuine signature from a buried assertion element. The issue is fixed in LightSaml versions 4.7.1 and 5.0.1.
The Synopsys DesignWare I3C controller driver (drivers/i3c/i3c_dw.c) tracks free Device Address Table (DAT) slots with get_free_pos(), which signals an exhausted table by returning -1. The helper declared its return type as uint8_t, so the sentinel was truncated to 255, and both consumers (dw_i3c_attach_device() and dw_i3c_i2c_attach_device()) also stored it in a uint8_t before testing if (pos < 0) — a comparison that is never true for an unsigned value. The exhaustion guard was therefore inert in every build.
With the guard defeated, an attach attempted on a full DAT proceeds with pos == 255: it writes data->dw_i3c_i2c_priv_data[255].id, more than 200 bytes past the end of the 32-element dw_i3c_i2c_priv_data array and past the end of struct dw_i3c_data; it stores the resulting out-of-bounds address in desc->controller_priv, from which later detach, reattach and IBI operations read the slot index back; and it performs a 32-bit MMIO store 1020 bytes beyond the hardware DAT base, outside the table the controller reports. The attach still returns success, so the upper layer believes the device is bound.
The DAT is smaller than the software array (its depth is read from DEVICE_ADDR_TABLE_POINTER, commonly 8 or 16 entries), so exhaustion is reachable. In a dual-role build (CONFIG_I3C_DUAL_ROLE with CONFIG_I3C_USE_IBI) acting as a secondary controller, the attach count is supplied by the bus's active controller: i3c_sec_handoffed() attaches one device per entry of the received DEFTGTS list, so a hostile or malfunctioning controller on the local I3C bus that declares more targets than the local DAT depth triggers the condition once per surplus entry. Exhaustion can also be reached from a devicetree that declares more devices than the table holds, or by repeated i3c attach shell commands.
Impact is bounded: the out-of-bounds store is a single byte of fixed value at a fixed displacement, with no attacker-chosen data or offset, so the realistic outcomes are corruption of neighbouring static driver state, writes into reserved controller registers, and inconsistent driver bookkeeping (a crash or a wedged I3C bus) rather than a controllable memory-write primitive. The attack vector is the local chip-to-chip I3C bus; there is no network-reachable path.
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260513.0, Draft Workspace identifiers are accepted without verifying that the authenticated user can access the referenced draft. Any authenticated user can enumerate draftWorkspaces, use a disclosed DRAFT_ID with draftWorkspaceEntities to read unpublished reports, descriptions, observables, and other staged intelligence, or place the identifier in the opencti-draft-id header and run mutations that inject entities and relationships into another user's private workspace. The flaw permits cross-user disclosure and tampering but does not cause a denial of service. This issue is fixed in version 7.260513.0.
Phison E12 and E18 PCIe SSD controllers contain a Secure Boot bypass vulnerability that allows a privileged local attacker to inject persistent boot-patch tuples into the unsigned, CRC-protected flash ID page read by the BootROM. By overwriting a fuse-derived RAM variable via a crafted patch entry using Phison Vendor Specific Commands, an attacker can force CRC-only firmware verification instead of signature checking, enabling an unsigned firmware image to load and creating a persistent controller-level implant that survives firmware reinstallation and operates below the host operating system.
An information disclosure vulnerability exists in thirdweb Dashboard through commit 940b3745. Authenticated users can access non-public team metadata by requesting the team join page with any invite ID. This exposure includes sensitive billing and support information such as billing email, billing status, Stripe customer ID, verified domain, and support identifiers.
visualTicket has a vulnerability involving information exposure through JSONP on session-bound cart service endpoints. Sensitive session data including session id, cart id, item ids, ticket/event metadata, quantities, and prices are exposed inside a script wrapper. Because the symfony session token can be passed in the URL, an attacker who obtains this token can read the victim's cart session data. This issue was mitigated in version 20260817 by setting the session cookie with SameSite=Lax, preventing other websites from accessing the cart data.