A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4 address when the host is written with non-ASCII characters, such as fullwidth digits (`１２７.0.0.1`).
`tls.checkServerIdentity()` did not recognize such hosts as IP addresses, even though they normalize and resolve to a regular IPv4 address, and matched them against the certificate DNS names and Common Name instead. A certificate containing `DNS:127.0.0.1` or `DNS:*.0.0.1` could therefore be accepted for an IP endpoint it was not issued for. This is a regression introduced after the fix for CVE-2026-48618.
This vulnerability affects Node.js **26.x** and **24.x**.
A business logic flaw in Node.js 26.x's zlib.ZipFile API can cause it to return incorrect bytes from a ZIP archive when local and central headers do not match. This occurs because the local header is cached without a content offset after validation failure, allowing attacker-controlled bytes to be returned while CRC-32 verification still passes. This discrepancy can cause Node.js-based scanners to approve different content than other ZIP implementations extract.
A flaw in Node.js Permission Model filesystem enforcement leaves `fs.realpathSync()` without the required read permission checks. This is an incomplete fix of CVE-2026-21715, which only covered `fs.realpathSync.native()`.
As a result, code running under `--permission` with restricted `--allow-fs-read` can still use `fs.realpathSync()` to check file existence, resolve symlink targets, and enumerate filesystem paths outside of permitted directories.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Tandoor Recipes versions from 2.0.0 up to but not including 2.7.0 contain a server-side request forgery (SSRF) vulnerability in the Pestle importer. This flaw allows authenticated low-privileged users to craft malicious image URLs in Pestle JSON import files that cause the server to issue arbitrary GET requests. The vulnerability arises from a raw requests.get call that bypasses the application's centralized SSRF protections, enabling attackers to access internal-only endpoints, perform port and service discovery, and exfiltrate internal responses via stored recipe images.
The jobwharf package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that execute code from remote URLs. These packages do not contain the payload themselves but facilitate downloading and running malicious scripts. The campaign is coordinated and intended to deceive users into executing harmful code.
The PyPI package 'slatejob' version 0.1.0 is part of a malicious campaign involving loader packages that download and execute remote malicious scripts. Although the package itself does not contain the payload, it acts as a delivery mechanism for potentially harmful code. This coordinated campaign aims to provide multiple deceptive methods to load malicious code remotely.
The reedworker package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that execute code from remote URLs. These packages do not contain the malicious payload themselves but are designed to download and run remote malicious scripts, indicating a coordinated effort to facilitate malicious code execution.
The loadferry package on PyPI version 0.1.0 is part of a coordinated malicious campaign involving loader packages that download and execute remote malicious scripts. Although the package itself does not contain the payload, its functionality enables execution of potentially harmful code from external sources.
Cisco is investigating the impact of an emergency distrust of eMudhra root and intermediate certificate authorities on its product line. The advisory lists numerous Cisco products under active investigation to determine if they are affected. As of now, no specific affected versions or confirmed vulnerabilities have been identified. Cisco will update the advisory as the investigation progresses.
The runpier package on PyPI version 0.1.0 is part of a coordinated campaign involving multiple loader packages designed to download and execute remote malicious scripts. Although the package itself does not contain the payload, its functionality enables execution of potentially harmful code from external sources. This campaign is identified as malicious with intent similar to infostealers.
The sedgehaul package on PyPI version 0.1.0 is part of a coordinated malicious campaign involving loader packages that download and execute remote malicious scripts. These packages do not contain the payload themselves but serve as deceptive loaders to facilitate malicious code execution. The campaign is identified as having clear malicious intent, including potential infostealing activities.
The taskquay package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that download and execute remote malicious scripts. While the packages themselves do not contain the payload, their coordinated use facilitates executing harmful code from external sources. This campaign is identified as having clear malicious intent, such as infostealing.
The marshrunner package on PyPI version 0.1.0 is part of a coordinated malicious campaign involving loader packages that execute code from remote URLs. Although the packages themselves do not contain the payload, they facilitate downloading and executing remote malicious scripts. This campaign is identified as having clear malicious intent, including potential infostealing activities.
The 'workslip' package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that execute code from remote URLs. Although the packages themselves do not contain the payload, they serve as a mechanism to download and run malicious scripts. This coordinated campaign aims to provide multiple deceptive methods to load malicious code remotely.
The brookworker package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that download and execute remote malicious scripts. These packages do not contain the payload themselves but serve as deceptive loaders to execute code from external URLs. The campaign is identified as having clear malicious intent, such as infostealing.
The cobbleload package on PyPI version 0.1.0 is part of a coordinated campaign involving multiple loader packages designed to download and execute remote malicious scripts. Although the package itself does not contain the payload, its functionality enables execution of potentially harmful code from external URLs. This campaign is identified as malicious with intent similar to infostealers.
The brambletask package on PyPI version 0.1.0 is part of a coordinated malicious campaign involving loader packages that execute code from remote URLs. Although the packages themselves do not contain the payload, they facilitate downloading and executing remote malicious scripts. This campaign is identified as having clear malicious intent, such as infostealing.
The ferretqueue package on PyPI version 0.1.0 is part of a malicious campaign involving loader packages that execute code from remote URLs. These packages do not contain the malicious payload themselves but serve as a mechanism to download and run malicious scripts. The campaign is coordinated and aims to provide multiple deceptive methods to load malicious code remotely.
The otterload package on PyPI version 0.1.0 is part of a coordinated campaign involving multiple loader packages designed to download and execute remote malicious scripts. Although the packages do not contain the payload themselves, their intent is clearly malicious, facilitating the execution of potentially harmful code from external sources.
The badgertask package on PyPI version 0.1.0 is part of a coordinated campaign involving multiple loader packages designed to download and execute remote malicious scripts. While the packages themselves do not contain the payload, their intent is clearly malicious, facilitating the execution of potentially harmful code from external sources.