The react-cache-hook npm package contains malicious code that compromises any computer on which it is installed or running. This compromise potentially grants full control to an outside entity, risking exposure of all secrets and keys stored on the affected system. Immediate removal of the package and rotation of all secrets from a different, uncompromised machine is strongly advised.
The npm package 'cortico-world-see-now' version 0.2.2 contains malicious code that can fully compromise any computer on which it is installed or running. This compromise may lead to unauthorized access and control by an outside entity. Immediate removal of the package and rotation of all secrets and keys from a different, uncompromised computer is strongly advised.
The npm package '@cutehttp/strict-uri-encode' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys on the affected system should be rotated immediately from a different, trusted machine. Simply removing the package may not fully eliminate the malicious presence, as the attacker may have gained full control of the system.
The npm package '@cutehttp/encode-url' contains malicious code that fully compromises any computer on which it is installed or running. This compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Immediate removal of the package is advised, but due to the extent of the compromise, complete remediation may require rotating all secrets and keys from a separate, trusted computer.
The fiddle-js npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, uncompromised device. Removing the package alone does not guarantee removal of all malicious software introduced by the package.
The jest-test npm package contains malicious code that compromises any computer on which it is installed or run. The compromise is severe enough that all secrets and keys on the affected system should be rotated immediately from a separate, uncompromised device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package 'stellar-api-safe' contains malicious code that fully compromises any computer on which it is installed or running. This compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Immediate removal of the package is advised, but full remediation may require rotating all secrets and keys from a separate, uncompromised device due to the risk of persistent malicious software.
The npm package @nexoratechorg/postcss-keyframes contains malicious code that compromises any computer on which it is installed or running. Systems with this package should be considered fully compromised, and all secrets and keys stored on those systems must be rotated immediately from a different, trusted computer. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.
The tailwindcss-animation-suite npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected computer should be rotated immediately from a different, uncompromised machine. Removal of the package alone does not guarantee elimination of all malicious software, as full control of the computer may have been given to an attacker.
Grav 2.0.0 before 2.2.18 resolves Flex sort and filter field names by first calling them as public methods, so a field named delete invokes FlexObject::delete() without any permission check. Authenticated users with only list access can send GET /api/v1/flex-objects/user-accounts?sort=delete requests to delete every account, then use the reopened API first-run setup to create a super admin.
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. Attackers can send a consent link to a signed-in victim so either consent button runs script in the NocoDB origin, stealing the session token for account takeover.
Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root.
This issue affects Apache Iggy: before 0.9.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue.
In the Linux kernel, the following vulnerability has been resolved:
ALSA: usx2y: Initialize idle URBs before submitting streams
usb_stream_start() submits the first two capture and playback URBs and
only afterwards assigns sk->idle_inurb, sk->idle_outurb,
sk->completed_inurb and sk->completed_outurb to the remaining two URBs
of each direction.
A transfer can complete as soon as usb_submit_urb() has been called, so
the completion handler i_capture_start() or i_playback_start() may run
before those pointers are set. While the stream is still being
synchronized (state below usb_stream_sync1), stream_start() then calls
playback_prep_freqn(sk, sk->idle_outurb) with sk->idle_outurb still
NULL, and the packet descriptors are written through that NULL pointer:
Oops: general protection fault, probably for non-canonical address
0xdffffc0000000018: 0000 [#1] SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000000c0-0x00000000000000c7]
RIP: 0010:playback_prep_freqn+0x11c/0x4a0 sound/usb/usx2y/usb_stream.c:33
Call Trace:
<IRQ>
stream_start+0x5dc/0x8d0 sound/usb/usx2y/usb_stream.c:596
i_capture_start+0x3da/0x710 sound/usb/usx2y/usb_stream.c:654
__usb_hcd_giveback_urb+0x238/0x550 drivers/usb/core/hcd.c:1657
usb_giveback_urb_bh+0x20b/0x530 drivers/usb/core/hcd.c:1691
tasklet_hi_action+0xa/0x20 kernel/softirq.c:994
handle_softirqs+0x16f/0x440 kernel/softirq.c:645
</IRQ>
The four URBs referenced by these pointers are allocated long before and
do not depend on any transfer state, so assign them before the submit
loop. Keeping the assignment inside the retry path also restores a
well-defined URB rotation when the start frame mismatch handling kills
and resubmits the streams.
A vulnerability in the GNU C Library (glibc) versions 2.26 to before 2.39_2 causes an assertion failure in the DNS stub resolver when processing a long search domain (around 200 characters or more) from /etc/resolv.conf or the LOCALDOMAIN environment variable. This assertion failure aborts the process using the library. The issue arises because the resolver truncates the search list into a fixed-size buffer but performs a consistency check against the wrong size, causing a valid truncated list to fail the assertion. This affects any process resolving names via glibc, including long-running processes that reload /etc/resolv.conf after changes. An attacker on the local network may trigger this without privileges by influencing DHCP or VPN-provided search domains. A patch is available in glibc version 2.39_2.
The npm package 'apintergrationpost' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, clean computer. Removing the package alone does not guarantee removal of all malicious software introduced by it, as the attacker may have gained full control of the system.
The npm package '@tnhorg/agent-skills' contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, clean computer. Removing the package alone may not eliminate all malicious software introduced by its installation, as full control of the system may have been granted to an attacker.
The npm package 'a-sub-watcher' contains malicious code that fully compromises any computer on which it is installed or running. The compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Immediate rotation of all secrets and keys from a different, uncompromised computer is strongly advised. Removal of the package alone may not eliminate all malicious software introduced by its installation.
The universallinks-unit npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, secure computer. Removing the package alone does not guarantee removal of all malicious software, as the attacker may have gained full control of the system.
The npm package 'transitions-promise-segmentedcontrol' contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, and all secrets and keys stored on the affected machine should be rotated immediately from a separate, secure device. Removal of the package alone does not guarantee elimination of all malicious software introduced by it.