OpenPanel versions prior to 3.0.0 have an SQL injection vulnerability in the ConversionService.getConversion function. This flaw allows users with project-read permissions or share-link holders to inject malicious ClickHouse SQL via unescaped event names and date parameters. Exploitation can bypass project_id restrictions, enabling unauthorized access to other tenants' analytics data. The vulnerability is rated high severity with a CVSS score of 7.1 and was fixed in version 3.0.0.
OpenPanel versions before 3.0.0 have a SQL injection vulnerability in the profileColumnAccess function within cohort.service.ts. This flaw allows project-read members to inject SQL by providing unescaped profile filter column names. Exploitation can enable attackers to execute subqueries within cohort.preview filters, potentially reading data from other tenants' ClickHouse databases. The vulnerability is fixed in OpenPanel version 3.0.0.
OpenPanel versions before 3.0.0 have a sandbox escape vulnerability in the JavaScript runtime validator. This flaw allows a project member with write access to bypass the AST allowlist by aliasing the Function constructor, enabling arbitrary code execution in the worker process. The vulnerability is fixed in version 3.0.0.
OpenPanel versions before 3.0.0 have an authorization bypass vulnerability that allows unauthenticated attackers to access any project's annotations. This occurs via the public reference.getChartReferences tRPC procedure, where attackers can use guessable slug-based project IDs to retrieve annotation titles, descriptions, and dates across tenants.
OpenPanel versions prior to 3.0.0 have an improper access control vulnerability in the event.bots tRPC procedure. This flaw allows unauthenticated attackers to read bot event information by sending anonymous requests with a projectId, bypassing authorization checks. As a result, attackers can retrieve bot-event names, types, and paths for private or password-protected projects, exposing internal routes.
OpenPanel versions before 3.0.0 have an SQL injection vulnerability that allows authenticated users to read data across tenants. By manipulating the profile.values property parameter, attackers can inject custom SQL SELECT statements to bypass project_id restrictions and access other projects' profiles, events, and sessions. This vulnerability is fixed in version 3.0.0.
OpenPanel versions prior to 3.0.0 contain an SQL injection vulnerability that allows authenticated users to bypass tenant scoping. This occurs because unescaped profile filter names are injected into a JOIN subquery, enabling attackers to manipulate the query with a crafted filter name and trailing comment. This bypasses the project_id WHERE clause and allows reading events from all projects.
OpenPanel versions before 3.0.0 have an authorization vulnerability in the onboarding.project tRPC mutation. This flaw allows non-admin organization members to create projects and generate write-type ingestion credentials, bypassing intended admin-only restrictions. Exploitation can lead to exposure of plaintext secrets, injection of fake analytics events, distortion of business metrics, and unauthorized consumption of the organization's usage budget. The vulnerability has a medium severity score of 5.3 and is fixed in OpenPanel version 3.0.0.
OpenPanel versions prior to 3.0.0 have an information disclosure vulnerability that allows read-level project members to access argon2id hashes of ingestion credentials via the client.list tRPC query. This exposure enables offline verification of leaked secrets without generating audit trails. The vulnerability is fixed in version 3.0.0.
DOMPurify versions from 3.4.4 up to but not including 3.4.17 contain a vulnerability that allows attackers to bypass the SAFE_FOR_TEMPLATES protection. This flaw enables preservation of template expressions in attached shadow roots when using certain return modes, leading to potential cross-site scripting (XSS) when these expressions are merged and evaluated by downstream template engines.
DOMPurify versions before 3.4.17 contain a cross-site scripting (XSS) vulnerability. This flaw allows attacker-controlled event handlers to remain active when an IN_PLACE hook removes a parent or sibling node during sanitization. As a result, attacker markup in detached subtrees is not properly sanitized, enabling event handlers like img onerror to execute after the sanitize() function completes.
DOMPurify versions before 3.4.17 contain a cross-site scripting (XSS) vulnerability. This flaw allows attackers to bypass the SMIL attributeName=href guard when parsing application/xhtml+xml content. The vulnerability arises because the transformCaseFunc function does not lowercase attribute names, enabling malicious SVG elements with animate or set tags to execute JavaScript when users click sanitized links. The issue is fixed in version 3.4.17.
CVE-2026-116801 is a vulnerability in parse-community's parse-server affecting versions before 8.6.105 and 9.10.5-alpha.6. It involves improper validation of the owning object reference in $relatedTo relation queries, allowing a client with read access to some objects to infer linked objects it cannot read by bypassing owning-object ACL checks.
CVE-2026-116800 is a local file inclusion vulnerability in WWBN AVideo versions before 29.5.0. It allows unauthenticated attackers to include and execute PHP files outside the intended locale directory by exploiting a path traversal flaw in the Accept-Language header processing. The vulnerability arises from insufficient sanitization of traversal sequences, enabling bypass of single-pass removal in the setLanguage() function. This flaw is fixed in version 29.5.0.
A vulnerability was detected in SourceCodester Online Food Ordering System 1.0. This issue affects the function unlink of the file admin/delete.php. Performing a manipulation of the argument image_name results in path traversal. The attack is possible to be carried out remotely. The exploit is now public and may be used.
CVE-2026-106282 is a vulnerability in Chromium's WebOTP feature involving UI misrepresentation. Affected versions are those before and including 155.0.4283.48. The issue has been fixed in version 155.0.4283.48.
Fireblocks' mpc-lib library has a cryptographic fail-open vulnerability in its BIP32 hardened derivation implementation when the private parent key is missing. This flaw breaks the ancestor isolation property, allowing an attacker with a compromised lower-level signer share and knowledge of the chain code to recover higher-level shares up to the root share. The primary MPC secret-sharing layer still prevents full private key reconstruction from a single share compromise, but the hardened derivation no longer provides defense-in-depth isolation between derivation levels. No vendor fix is currently available, and mitigation involves keeping the chain code secret and auditing derivation paths.
CVE-2026-116556 is a cross-site scripting (XSS) vulnerability in Argilla versions 2.0 through 2.8.0. It arises from improper handling of the 'text' argument in a frontend Vue component, allowing remote attackers to inject malicious scripts. The vulnerability has a medium severity score of 4.8 and public exploit code is available. The Argilla project has been notified but has not yet issued a response or patch.
CVE-2026-116555 is a cross-site scripting (XSS) vulnerability in Argilla up to version 2.8.0. It arises from improper handling of the 'template' argument in a component file within the frontend codebase. The vulnerability allows remote attackers to inject malicious scripts. Public exploit code has been disclosed, but no official response or patch has been issued by the project as of the publication date.
A confused deputy attack exists in the StatefulSet controller that allows a user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects to create a cross-namespace pod. An attacker exploiting this vulnerability would have full control over the resulting pod’s metadata and specification, including namespace selection. Note that the cross-namespace pod will be immediately deleted by the garbage collector unless the attacker is able to construct a valid StatefulSet OwnerReference. This would require referencing the UID of an existing StatefulSet in the victim’s namespace.