---
_-= Per source details. Do not edit below this line.=-_
## Source: ghsa-malware (6891c7601fca7e7dc5fe0e94747480b0638daef317c819d9012cd5edb3d51559)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: ghsa-malware (c5899e643592a7aa270cfad701dd55582d107474606bb685f041c177136f986e)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: ghsa-malware (e2d7d313d31dd184009e419a65996c65c32fe149d202c07de53826a1bbba5a33)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: ghsa-malware (2b9082a1feea7f11c6b67b150968ece101e40d923de45f0f6e08ead9f22d96cf)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Vault Community Edition and Vault Enterprise did not apply explicit ACL policy deny rules to letter case variants of user and group names in auth methods that treat these names as case-insensitive. This may allow an authenticated user with delegated permissions to modify a protected user or group, potentially leading to privilege escalation. This vulnerability (CVE-2026-128100) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.25.
Kanbanz plugin for WordPress versions before 1.0.3 contains an authorization bypass vulnerability allowing authenticated Kanban Staff users to access and modify boards they do not belong to. This is due to missing access control checks in admin-ajax handlers, enabling attackers to manipulate board_id or task_id parameters arbitrarily. Exploitation can lead to unauthorized reading of sensitive task data, modification of status columns, subtasks, labels, comments, attachments, and task creation on other teams' boards. The issue is fixed in version 1.0.3.
CVE-2026-128123 is a vulnerability in SvelteKit framework versions 5.5.7 up to but not including 5.5.8 and 6.0.0-next.0 up to but not including 6.0.1, as well as versions >=3.0.0-next.0 <3.1.1 and <2.70.4. The issue occurs in the @sveltejs/adapter-node where an attempt to add a header to an immutable request causes the server to crash, resulting in a denial of service. This flaw is fixed in versions 5.5.8, 6.0.1, 3.1.1, and 2.70.4. The CVSS score is 5.9, indicating a medium severity impact primarily due to availability disruption.
The PyPI package 'qap793gl4l' version 0.1.1 is part of a malicious campaign that executes remote code. It overrides the install command in its setup.py to run malicious code during installation, including downloading and executing a remote malicious script. The campaign is identified as having clear malicious intent, such as infostealing.
A cross-site scripting (XSS) vulnerability exists in SvelteKit's @sveltejs/adapter-cloudflare from version 4.7.0 up to but not including 7.2.10 and from 8.0.0-next.0 up to but not including 8.0.2. The flaw allows attacker-influenced links crawled during prerendering to inject whitespace, control characters, wildcards, or placeholders into redirect paths. These paths are written into Cloudflare _redirects output without proper validation, enabling unintended routing rules that could redirect or expose requests beyond intended prerendered routes. The issue is fixed in versions 7.2.10 and 8.0.2.
SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to @sveltejs/adapter-vercel 6.3.5 and 7.0.2 and @sveltejs/adapter-static 3.0.11 and 4.0.1, an attacker-influenced link crawled during prerendering could be emitted into the generated Vercel routing configuration without escaping regular-expression metacharacters. The configuration could consequently interpret the path as regular-expression syntax, match unintended application paths, and expose content or behavior outside the intended path. This issue is fixed in @sveltejs/adapter-vercel 6.3.5 and 7.0.2 and @sveltejs/adapter-static 3.0.11 and 4.0.1.
This is a Request for Comments (RFC) open for community review until December 11, 2026, proposing a design for a cloud mirror system searchable by AI assistants where the server never stores the user's encryption key. The design aims to enhance data confidentiality by encrypting messages client-side and limiting server knowledge to token hashes and encrypted keys. It acknowledges limitations such as potential key exposure on a compromised server, deterministic search tag leakage, and lack of end-to-end encryption with AI providers. The RFC solicits feedback on cryptographic design choices, key rotation, token lifetimes, attestation, and other architectural questions.
SvelteKit versions from 2.42.0 up to but not including 3.1.1 contain an inefficient algorithmic complexity vulnerability in the experimental remote functions feature. Specifically, parsing a specially crafted request with many form entries can cause quadratic synchronous work, blocking the event loop and resulting in a denial of service. This issue is resolved in version 3.1.1.
CVE-2026-128119 is an authorization flaw in SvelteKit versions from 2.60.1 up to but not including 3.1.1. The issue occurs when using the experimental remote functions flag, allowing separate non-exported query.batch functions to share the same generated identifier. This can cause arguments intended for one function to be passed to another, potentially disclosing sensitive function arguments. The vulnerability is fixed in version 3.1.1.
A path parsing flaw in Nuxt versions 4.6.0 through 4.6.3 allows an unauthenticated attacker to bypass server-side route controls by using request paths starting with double slashes (//). This causes server middleware and route rules keyed on normal paths (e.g., /admin) to be skipped, enabling unauthorized access to protected pages and skipping security headers or redirects. The issue is fixed in version 4.6.4.
SvelteKit versions from 3.0.0 up to but not including 3.1.1 contain a vulnerability where server-only modules imported via src/params.js could be bundled into client-side code. This exposure allows private environment values or other server secrets to be accessible in the client bundle. The issue is resolved in version 3.1.1.
The @opentelemetry/instrumentation-http package for Node.js versions >=0.204.0 and <0.222.0 improperly handles sensitive query parameters in incoming HTTP requests. While outgoing client spans redact sensitive URL query parameters, incoming server spans do not, resulting in raw query strings—including credentials like AWS presigned URLs, Azure SAS tokens, and GCS signed URLs—being recorded in plaintext in the url.query attribute. This sensitive information is then exported to the tracing backend, exposing valid credentials to anyone with access to telemetry data. The issue is patched in version 0.222.0, which redacts sensitive query parameters by default for incoming spans and introduces a redactedQueryParamsServer option for customization.
SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. Prior to versions 2.70.4 and 3.1.1, the reroute hook could rewrite an invalid percent-encoded pathname into a valid route and reach a comparison that decoded the original malformed pathname outside the guarded decoding operation. The resulting unhandled URIError could crash an adapter-node server and deny service to other requests. This issue is fixed in 2.70.4 and 3.1.1.
FlowiseAI Flowise versions up to 3.1.4 contain a server-side request forgery (SSRF) vulnerability. Authenticated users with permissions to create or update chatflows or agentflows can bypass the Custom Function sandbox's SSRF protections by requiring specific module subpaths inside allowlisted packages. This bypass returns an unwrapped HTTP client that skips validation, allowing attackers to send arbitrary HTTP requests to internal network addresses or cloud metadata endpoints. This can lead to network mapping, credential disclosure, and unauthorized state changes on internal services.
CVE-2026-128116 is a cross-site scripting (XSS) vulnerability in SvelteKit, a web application framework. Versions prior to 2.70.4 and 3.1.1, when configured with router.resolution set to 'server', could misinterpret pathnames starting with // as protocol-relative module specifiers during client-side navigation. This flaw allows an attacker to craft a link that causes the server-side route resolution to import and execute JavaScript from an external origin in the user's browser. The vulnerability is fixed in versions 2.70.4 and 3.1.1.
A vulnerability in dnspython prior to version 2.9.2 allows an attacker to cause uncontrolled resource consumption via the from_text() parser for WKS records. The parser does not validate that the service number is within the valid range (0 to 65535), enabling an attacker to supply a larger number that causes excessive memory and CPU usage, potentially terminating the process. This affects applications parsing attacker-controlled zone-file text with WKS records. The issue is fixed in dnspython version 2.9.2.