Sonatype Nexus Repository 3 contains a vulnerability where an unauthenticated remote attacker can supply attacker-controlled input to a Java class loading call via an ExtDirect endpoint. This allows the attacker to determine the presence of specific classes in the application but does not enable code execution by itself. The issue affects versions from 3.0.0 up to but not including 3.97.0. The vulnerability has a medium severity rating with a CVSS 4.0 score of 6.9.
Multiple name constraints bypass issues were identified in BoringSSL's Subject Alternative Name (SAN) validation logic affecting different validation paths. Some issues have been fixed, one is accepted and under coordination, one is disputed, and one was declined. These issues affect how BoringSSL enforces name constraints on certain SAN forms, potentially allowing subordinate certificate authorities to issue certificates with names outside intended constraints. The impact depends on enforcement of name constraints on affected paths and use of the accepted names for authorization. Presence of BoringSSL alone does not imply that products like Chrome or Android are affected.
A vulnerability in the Linux kernel's mac80211 wireless subsystem could cause a warning (WARN_ONCE) in the driver when setting the bitrate mask if the wireless interface is marked running but not yet fully registered in the driver. This occurs because ieee80211_set_bitrate_mask() does not verify that the interface is still present in the driver before calling driver operations. The issue is triggered by certain wireless ioctl calls during interface teardown or early bringup stages. The fix adds a check for the interface presence in the driver and returns an error to avoid the warning.
A vulnerability in Siemens SIMATIC IPC BX-21A and related models allows bypassing UEFI Secure Boot protections due to the presence of a BIOS vendor test key in the UEFI Secure Boot key database. This affects all versions prior to V31.01.13 for IPC BX-21A, prior to V1.1.4 for IPC RW-543A, and prior to V28.01.15 for IPC227G, IPC277G, IPC277G PRO, IPC327G, and IPC377G. An attacker with local physical or administrative access could exploit this to boot unauthorized operating systems or UEFI applications, potentially compromising device confidentiality, integrity, and availability.
A vulnerability in the Windows Machine Config Operator (WMCO) for Red Hat OpenShift Container Platform allows a compromised Windows worker node to escalate privileges to cluster-administrator by submitting a specially crafted Certificate Signing Request (CSR). This flaw arises because the CSR auto-approver validates the presence of the organization system:wicd-nodes but does not reject additional organization values such as system:masters. Exploitation requires prior compromise of a Windows worker node and access to WICD credentials. No mitigation or workaround is currently available, and a fix is pending.
The npm package @xrelly-stack/bails contains malicious code that fully compromises any computer on which it is installed or running. The presence of this package means that all secrets and keys stored on the affected computer should be considered compromised and must be rotated from a separate, secure device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package @alipclutch/libsignal-node 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 system should be rotated immediately from a secure, unaffected device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The npm package @we3js/framework contains malicious code that can fully compromise any computer on which it is installed or run. The presence of this package indicates a severe security risk, as attackers may gain full control of the affected system. Immediate removal of the package and rotation of all secrets and keys from a separate, uncompromised device is strongly advised. However, removal of the package alone may not eliminate all malicious components introduced by the compromise.
The npm package @badzz88/eslint-config 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 computer should be rotated immediately from a separate, secure device. Removing the package alone does not guarantee removal of all malicious software introduced by it.
The eth-gas-oracle RubyGem version 0.9.1 contains malicious code embedded in its native extension build script. During installation, it decodes and executes a hidden Ruby payload that establishes a reverse shell to a hardcoded IP address, allowing remote command execution on the installer's machine. The payload includes evasion techniques to avoid detection in sandbox or CI environments and requires the presence of developer artifacts to activate. The package metadata is inconsistent, indicating it is a disposable vehicle for malicious activity rather than legitimate functionality.
The web3-signer-kit RubyGem version 0.9.1 contains malicious code embedded in its extconf.rb file. During gem installation, it decodes and executes a base64 payload that establishes a remote shell connection to a hardcoded IP address, enabling full remote code execution. The payload includes sandbox evasion techniques and requires the presence of developer artifacts before activating. The gem itself has no legitimate functionality and acts as a decoy to deliver this malicious payload.
The Ruby gem 'tron-trc20-utils' version 0.9.1 contains malicious code that executes a reverse shell during installation. The gem's extconf.rb file decodes and evaluates a base64-encoded payload that connects to a remote IP address and provides an interactive shell to the attacker. The malicious behavior is designed to evade sandbox and continuous integration environments by checking for specific environment variables, hostnames, usernames, working directories, system uptime, and the presence of developer artifacts. The gem's metadata and contents are inconsistent, indicating deception. This reverse shell is the primary functionality of the package, posing a significant security risk to users who install it.
The RubyGem 'perp-funding-rates' version 0.9.1 contains malicious code in its native-extension script that executes during installation. The script decodes and evaluates a hidden Ruby payload that establishes a reverse shell to a hardcoded command-and-control server, allowing remote code execution on the installer's machine. The payload activates only on developer workstations or build systems identified by the presence of specific user files, indicating a targeted attack. This behavior is obfuscated and delayed to evade detection.
The npm package @fer2809fl/baileys contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a different, trusted machine. Removing the package alone does not guarantee removal of all malicious software introduced by it.
A malicious file identified by the SHA-256 hash 1ecfe3ec7b25893dc55c0ed14196a817f1edd0469cca0a6ad42974d0eccbf146 was observed by OffSeq Mirage honeypot sensors on October 9, 2026. The file is associated with attacker activity involving the T1105 technique (Ingress Tool Transfer), indicating it was used to stage or deliver a malicious payload such as a dropper, web shell, miner, or post-exploitation tool. This hash can be used as an indicator of compromise to detect the presence of this specific malicious payload in environments and security tools. No specific software versions or patches are applicable. No known exploits or threat actors are linked to this hash at this time.
A vulnerability in the Linux kernel's VLAN tag insertion function (__vlan_insert_inner_tag) allows uninitialized memory to be transmitted when the MAC header is not present. This occurs because the function assumes the presence of the MAC header and rewrites bytes without verifying its existence, potentially leaking kernel slab memory in transmitted packets.
The Drupal module 'Permissions by term' allows restricting view access to nodes based on taxonomy terms. A vulnerability exists where, in 'Permission mode', access rights are not properly checked when a node references a deleted taxonomy term and is accessed via JSON:API. Exploitation requires a specific module configuration, the presence of references to deleted terms, and access through JSON:API. A patch is available for versions prior to 3.1.41.
CVE-2026-87975 is an authorization bypass vulnerability in Django affecting versions 6.1 before 6.1.2, 6.0 before 6.0.9, and 5.2 before 5.2.18. The issue arises in django.forms.models.BaseModelFormSet.save_existing_objects(), which incorrectly trusts the presence of a primary key on a submitted form's instance as proof that the instance belongs to the formset's limiting queryset. This flaw allows an authenticated user with permission to submit such a formset to delete objects outside the intended queryset by submitting forged management-form data. Models using the default AutoField primary key are not affected. The vulnerability has a medium severity with a CVSS score of 4.3.
A vulnerability in the Linux kernel's libipw component related to TKIP frame processing has been fixed. The issue involved the libipw_michael_mic_verify() function incorrectly assuming the presence of a full eight-byte Michael MIC in TKIP frames. This could cause out-of-bounds reads when processing short TKIP frames lacking a full MIC.