In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: reject feature changes after endpoint vhost_scsi_setup_vq_cmds() runs from VHOST_SCSI_SET_ENDPOINT and allocates each command's protection scatterlist array (prot_sgl) according to the acknowledged VIRTIO_SCSI_F_T10_PI bit. The command pools are not rebuilt when VHOST_SET_FEATURES changes that bit later. Although virtio feature bits must not change after feature negotiation, vhost_scsi_set_features() currently accepts such a request after the endpoint is active and updates acked_features. Enabling T10-PI after endpoint setup therefore leaves prot_sgl NULL while the I/O path follows the new feature bit. For a 129-page protection payload, vhost_scsi_mapal() passes the missing first chunk to sg_alloc_table_chained(): sg_alloc_table_chained(table, 129, first_chunk=NULL, nents_first_chunk=inline_sg_cnt) sg_pool_index() then hits: BUG_ON(nents > SG_CHUNK_SIZE); /* 129 > 128 */ The kernel reported the following call trace and register state: Call Trace: <TASK> ? __sg_alloc_table+0x1d8/0x250 ? __pfx_vhost_run_work_list+0x10/0x10 [vhost] sg_alloc_table_chained+0x59/0xf0 ? __pfx_sg_pool_alloc+0x10/0x10 ? vhost_scsi_calc_sgls.constprop.0+0x43/0x60 [vhost_scsi] vhost_scsi_handle_vq+0xf02/0x1700 [vhost_scsi] ? __pfx_vhost_scsi_handle_vq+0x10/0x10 [vhost_scsi] vhost_scsi_handle_kick+0x37/0x50 [vhost_scsi] vhost_run_work_list+0x8e/0xd0 [vhost] vhost_task_fn+0xe1/0x210 ret_from_fork+0x348/0x540 </TASK> RIP: 0010:0x4 CR2 = 0x4 RSP: 0018:ffffc90000dbf940 EFLAGS: 00010202 RAX: ffffffff82396810 RBX: ffff88811dc28b80 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000820 RDI: 0000000000000081 VHOST_F_LOG_ALL is a vhost-specific runtime feature and remains the only exception. Reject changes to any feature other than VHOST_F_LOG_ALL while the endpoint is active. This preserves the existing runtime log toggle while preventing feature-dependent command resources and data-path state from becoming inconsistent. Userspace must clear the endpoint before changing any other negotiated feature and set the endpoint up again afterward.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (8cebaa0a3370c12104ef2816420193171f431df0d113fdc5d8c9f1dc921deeb5)
Package advertises itself as a TOTP utility but its postinstall script (`node./index.js --setup 2>/dev/null || true`) and its exported `validateSecret` API both invoke a hidden `_run()` routine that (1) scans Discord/Chrome/Edge/Brave/Opera LevelDB stores under `os.homedir()` for Discord auth-token regexes, DPAPI-decrypts encrypted tokens via a spawned powershell `ProtectedData.Unprotect` call, parses Minecraft launcher credentials (vanilla `launcher_accounts.json`, Lunar `accounts.json`, ModrinthApp `app.db` JWTs), validates the harvested Discord tokens against `discord.com/api/v9`, and POSTs the collected credentials to a hardcoded Discord webhook whose URL is stored as chunked base64 in `_x` and reassembled at runtime (`Buffer.from(_x.join(''),'base64')`) to a `discord.com/api/webhooks/1532429233769419004/...` endpoint; and (2) enumerates vanilla/Modrinth/Lunar Minecraft profile `mods/` directories and writes an opaque JAR named `optimized-renderer-1.0.0.jar` (URL also stored as chunked base64 decoding to `cdn.discordapp.com/attachments/1507484731535785994/1540335670831222894/optimized-renderer-1.0.0.jar`) into each discovered mods folder, delivering unverified code that will execute the next time the user launches Minecraft with a Fabric loader. The postinstall suppresses stderr and uses a 4-second `setTimeout` to appear to finish cleanly. Because `validateSecret` (part of the three-function public API) schedules `_run()` via `setImmediate`, the same theft and dropper also fire whenever a downstream consumer imports the package and calls the advertised TOTP function — extending the attack surface well beyond install time.
## Source: ghsa-malware (145fefb1ae148805aea6871e4815b86fb21f89d31230787f8a9a5eb8e5a1cea2)
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.
## Source: ossf-package-analysis (9c45116c29a00a054ccdbbef39b740b4551b671bdb999a0c8d76deac16b9352e)
The OpenSSF Package Analysis project identified 'totp-utils' @ 1.4.4 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
CVE-2026-59318 is an authorization vulnerability in Spring AI's tool calling support. The vulnerability arises because the per-request tool list, which is advertised to the model as a boundary, is not fully enforced when dispatching a tool call. This can allow a tool that was not made available to the current request to be invoked, potentially leading to privilege escalation. The issue affects multiple versions of Spring AI, including 1.0.0 through 1.0.9, 1.1.0 through 1.1.8, and version 2.0.0.
MLflow versions from 3.13.0 up to but not including 3.15.0 contain a vulnerability where the LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth mode. This allows any authenticated user to call the POST /api/2.0/mlflow/runs/log-inputs endpoint for another user's run and inject attacker-controlled DatasetInput records into the dataset_inputs lineage metadata without having UPDATE permission. The issue is fixed in version 3.15.0.
The customer update route in EverShop is declared with "access": "public" in packages/evershop/src/modules/customer/api/updateCustomer/route.json, which causes the admin authentication middleware to call next() without checking the caller, and no customer-session middleware guards the route; the only middleware in the chain parses the JSON body. The handler in updateCustomer.js then loads the customer by the uuid taken from the URL path and writes the supplied fields back to that record, hashing a password if one is provided, without verifying that the caller owns the record. An unauthenticated request carrying a known customer uuid can therefore overwrite that customer's email address and password and read back the updated record from the 200 response, taking over the account and locking out its owner. Customer uuids are exposed through order confirmation email links and administrative URLs. Version 2.2.1 changes the route to "access": "private".
deepmerge-ts versions prior to 8.0.0 have an uncontrolled recursion vulnerability in several deep merge APIs. The merging functions do not track visited objects or pairs, causing infinite recursion when merging objects with self-references at the same property path. This leads to a synchronous crash of the Node.js process due to a maximum call stack size exceeded error. The issue is fixed in version 8.0.0.
GitPython versions up to 3.0.0_13 have a vulnerability in the Repo.init() method where unsafe git options, specifically --template, are forwarded without validation. This allows an attacker who can control the template path to plant malicious git hooks that execute arbitrary code during subsequent git operations. The vulnerability requires the attacker to stage an executable hook directory at a known path and have the application call Repo.init with the malicious template argument.
CVE-2026-76878 is a high-severity vulnerability in OpenStack Aodh before version 22.0.1 where the alarm list API improperly handles the all_projects query parameter. This flaw allows non-admin users with reader roles to bypass project scoping and list alarms from all projects, exposing sensitive information such as webhook URLs, Heat signal endpoints, project IDs, and user IDs. Additionally, OpenStack Watcher's webhook trigger endpoint lacks authorization controls since version 4.0.0, enabling any authenticated user who obtains a webhook URL to trigger audits and action plans regardless of their permissions.
A vulnerability in Splunk On-Call (VictorOps) app versions before 1.0.43 allows users without admin or power roles to read a partially masked API key stored in the App Key Value Store. The API key is not fully masked before storage, exposing sensitive information to unauthorized users with read access to the KV Store.
CVE-2026-17091 is an integer overflow or wraparound vulnerability in IBM PowerVM Hypervisor versions FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2. An attacker with root access to a guest partition can exploit this flaw by issuing a crafted hypervisor call that injects arbitrary data into hypervisor or partition memory. This can cause a crash leading to a full platform reboot and termination of all hosted partitions or memory corruption. The hypervisor restarts automatically, but repeated exploitation may cause sustained availability issues. The vulnerability impacts system integrity and availability.
CVE-2026-17097 is a vulnerability in IBM PowerVM Hypervisor affecting multiple firmware versions. It involves improper validation of array indices in the hypervisor call interface. An attacker with root access to a guest partition can exploit this flaw to cause a virtual processor to become permanently unresponsive, requiring a full platform reboot. Additionally, exploitation may lead to unintended data injection into hypervisor or partition memory without attacker control over the target location. The vulnerability impacts system integrity and availability.
CVE-2026-72529 is a critical vulnerability in TrueConf Server that allows remote attackers with network access to port 4307/TCP to execute arbitrary scripts without authentication. This affects multiple versions of TrueConf Server prior to 5.3, as well as specific ranges within 5.3.x, 5.4.x, and 5.5.x. The flaw stems from missing authentication on a critical function accessible via an undocumented call.
MyBooks is anebook management web server also known as Talebook. In 3.41.2 and earlier, the SignUp.post handler for POST /api/user/sign_up in webserver/handlers/user.py does not enforce the ALLOW_REGISTER configuration flag, even though the frontend hides registration controls when the flag is false. An unauthenticated remote attacker can call the endpoint directly and create a valid account on an instance whose administrator disabled public registration. The process_auth_header function in webserver/handlers/base.py also does not verify the account's active flag, so the newly created and unactivated account can authenticate immediately and access user-level API functionality. The bypass defeats the intended account-creation policy and can supply the low-privilege account required by related authorization vulnerabilities. This issue is fixed in version 3.42.0.
phpMyFAQ before 4.1.7 contains an authentication bypass vulnerability in SetupController that allows unauthenticated attackers to run database migrations and create configuration backups when maintenance mode is enabled. Attackers can call POST /api/setup/update-database and POST /api/setup/backup endpoints to execute database updates, disable maintenance mode, and extract database credentials from generated ZIP archives.
Oracle has released a Critical Security Patch Update (CSPU) addressing multiple vulnerabilities in various components of Oracle E-Business Suite versions 12.2.3 through 12.2.15. The update includes fixes for modules such as General Ledger, Payments, Workflow, Sales, Purchasing, and Call Center Technology. The CSPU is part of Oracle's ongoing efforts to provide targeted security fixes with minimal disruption. Oracle strongly recommends applying these patches promptly to avoid exploitation of known vulnerabilities.
CVE-2026-58087 is a local privilege escalation vulnerability in the semctl(2) system call's GETALL and SETALL commands. These commands improperly handle semaphore sets by relying on a sequence number that can wrap after extensive create/destroy cycles. An unprivileged local user can exploit this to cause out-of-bounds reads and writes on kernel heap memory, potentially leading to privilege escalation.
CVE-2026-49415 is a local privilege escalation vulnerability occurring during the execve system call of a SUID binary. The vulnerability arises because the new virtual address space is installed before the process credentials are updated, allowing a race condition. During this window, an unprivileged local user running as the same user can access and modify the target process's memory via procfs or linprocfs before the credentials are elevated. This can lead to full system compromise if exploited.
The animate-css-vite npm package version 1.0.1 contains malicious code that fetches and executes remote code during the build process. This behavior is hidden by obfuscation techniques including RC4 and base64 encoding. The remote code execution occurs via a dynamic function call with require in scope, allowing arbitrary code execution within the consumer's build environment.
The npm package @sarex-team/viewer version 9.9.11 contains malicious code that exfiltrates sensitive system information via DNS queries. During installation and each require() call, it sends the installer's OS username, hostname, and current working directory basename to an attacker-controlled domain. This exfiltration is concealed by reconstructing key module and domain names from numeric char-code arrays. The malicious behavior occurs silently without user interaction, embedded in the package's install script and runtime code.