Critical9.2KEVMirageEPSS 99%Palo Alto Unit 42CVE-2026-109618
Two critical remote code execution vulnerabilities, CVE-2026-109618 and CVE-2026-109619, affect PHP. These flaws involve improper memory handling during fatal error processing with longjmp(), allowing attackers to execute arbitrary code remotely. CVE-2026-109618 arises from uninitialized request memory after out-of-memory errors, while CVE-2026-109619 involves global memory pointing to freed regions exploitable in subsequent requests. Over 22.6 million exposed instances have been identified. Palo Alto Networks provides protections via multiple security products and recommends immediate patching. At least one European government took precautionary measures by taking its website offline. Users should consult the PHP Group’s security advisory for patching guidance.
Cisco Talos has identified a new Windows-based command-and-control (C2) framework named NIK C2 that integrates AI directly into its attack chain. This Go-based implant enables adversaries to dump credentials, capture keystrokes, and deploy screen-locking ransomware. It uses an embedded OpenAI model to analyze harvested data in real time, funding API requests by hijacking the victim's own OpenAI API keys. This integration allows continuous data collection and exploitation without offline delays, turning compromised hosts into active operational assets. The use of victim API keys also masks attacker infrastructure, complicating detection and incident response. Defenders are advised to implement continuous behavioral monitoring and update endpoint defenses accordingly.
Botan is a C++ cryptography library. From 2.1.0 until 3.13.0, the Botan C API function botan_block_cipher_block_size converted a size_t block size to int without a bounds check. In an application that accepts external algorithm parameter strings and uses the FFI raw ECB mode, an attacker can select the variable-block-size Lion cipher so that the reported size is truncated, the caller allocates insufficient memory, and later block processing causes memory corruption. The C++ API and normally used C API modes such as CBC and CTR are unaffected. This issue is fixed in version 3.13.0.
Botan versions from 1.11.34 up to but not including 3.13.0 have a vulnerability in the botan ocsp_check command-line tool where OCSP responses are accepted without verifying the signature or authorizing the signer. This allows a malicious or on-path attacker to provide a forged OCSP response indicating a revoked certificate is valid. The issue is fixed in version 3.13.0.
Botan, a C++ cryptography library, had a vulnerability in its Python binding from versions 1.11.22 up to but not including 3.13.0. The issue involved improper handling of embedded null (U+0000) characters in Python strings, causing bcrypt and check_bcrypt functions to process only the password prefix before the null byte. This allowed applications to bypass password policies by validating longer passwords but hashing shorter effective values. The vulnerability does not affect scrypt and argon2 functions. The issue is fixed in Botan version 3.13.0.
CVE-2026-118766 is a server-side request forgery (SSRF) vulnerability in the Botan C++ cryptography library prior to version 3.13.0. The issue arises from Botan's online OCSP client allowing a single HTTP redirect when posting OCSP requests, which can be exploited by a malicious OCSP responder or an on-path attacker to make a blind request to internal HTTP services. This can potentially affect internal services that have non-idempotent GET handlers and allow timing-based information leakage. The vulnerability is fixed in Botan version 3.13.0.
Botan is a C++ cryptography library. From 3.7.0 until 3.13.0, an application that calls AutoSeeded_RNG::clear() and then calls randomize with an empty output buffer while the generator is unseeded can cause AutoSeeded_RNG to mark itself seeded without consulting the configured entropy source. On builds without BOTAN_HAS_SYSTEM_RNG, the fallback uses only a clock value and process ID, so a later non-empty request can produce output from predictable state. This issue is fixed in version 3.13.0.
CVE-2026-118764 is a high-severity vulnerability in the isaacs minimatch library prior to version 11.0.1. It involves asymmetric resource consumption due to repeated expansion of malicious glob patterns, leading to excessive CPU and memory usage during pattern compilation. The issue is fixed in version 11.0.1.
CVE-2026-118763 is a vulnerability in sigstore-js versions prior to 0.7.2 where registry credentials can be leaked to attacker-controlled hosts. The RegistryClient.signIn() method stores authorization headers globally, and RegistryClient.uploadBlob() sends PUT requests to arbitrary blob-upload URLs without verifying their origin. This allows a malicious registry to capture sensitive credentials during artifact pushes. The issue is fixed in version 0.7.2 by isolating registry credentials and restricting their transmission to the registry origin only.
The npm package @chatunitycenter/baileys 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, trusted computer are strongly advised.
CVE-2026-118762 is a critical vulnerability in the Monkeytype repository's CI workflow prior to version 26.43.0. The GitHub Actions workflow runs with repository write permissions on pull_request_target events and executes code from forked pull requests with elevated privileges. This allows an external contributor to execute arbitrary code, access the GITHUB_TOKEN, and potentially push changes or modify pull requests and issues. The vulnerability affects only the repository's CI workflow, not the Monkeytype application or user data. The issue is fixed in version 26.43.0.
CVE-2026-115805 is a high-severity vulnerability in Rapid7 Insight Agent on Linux and macOS. It involves improper neutralization of special elements in OS commands due to unsafe handling of local filesystem paths. Authenticated local users with existing access can exploit this flaw to gain elevated privileges. The vulnerability is fixed in version 4.1.4.43.
CVE-2026-119115 is an incorrect authorization vulnerability in the issuer resolution logic of AWS Private CA Connector for Kubernetes. Authenticated users with approval policies limited to namespace-scoped issuers could, under certain conditions, obtain certificates signed by cluster-scoped issuers they are not authorized to use. This includes the ability to obtain subordinate CA certificates. The issue affects aws-privateca-issuer versions before v1.10.1 and the AWS Private CA Connector for Kubernetes EKS add-on before v1.10.1-eksbuild.1. AWS has published a security bulletin with details and remediation guidance.
The decode-uri-component package has a denial of service vulnerability due to quadratic time complexity when processing malformed inputs with many distinct percent-encoded runs. An attacker can craft a payload of about 224 KB that causes the Node.js event loop to block for approximately 20 seconds, making the application unresponsive. This affects version 0.5.0 and earlier. The issue arises because the fallback decoding function performs multiple regex replacements proportional to the number of distinct encoded runs, leading to O(K·L) complexity. The vulnerability impacts availability only, with no confidentiality or integrity effects. It is fixed in version 0.5.1.
An unauthenticated remote denial of service vulnerability exists in the Twisted HTTP/2 server due to improper handling of rapid stream resets. A remote client can send a request with END_STREAM followed immediately by a stream reset, causing the server to render the request fully before processing the reset. This allows repeated rapid resets on a single connection to exhaust CPU resources, bypassing the concurrent-stream limit. The issue affects Twisted versions prior to 26.10.0rc1 and has no impact on confidentiality or integrity.
A denial of service vulnerability exists in the zip crate versions 5.1.0 up to but not including 9.0.0 when the legacy-zip feature is enabled. An attacker can craft a malicious ZIP64 archive with an uncompressed size set to an extremely large value, causing a capacity overflow panic in the Shrink decoder during extraction. This panic terminates the affected process, leading to denial of service. The issue arises because the decoder reserves output buffer capacity based on the uncompressed size from ZIP metadata before validating the compressed data size. This vulnerability is fixed in version 9.0.0.
A vulnerability in the zip crate (versions 7.2.0 up to but not including 9.0.0) allows an attacker to write arbitrary files outside the intended extraction directory by exploiting symlink validation flaws. The issue arises because the path validation is purely lexical and absolute symlink targets are not properly rejected, enabling directory traversal outside the extraction target. This is especially impactful on Windows, where a single symlink can redirect extraction to a different drive or remote share. The vulnerability requires the attacker to know or guess the absolute extraction path. The issue was introduced by a change in path handling in version 7.2.0 and fixed in version 9.0.0.
A vulnerability in the zip crate's AES-encrypted entry handling allows an attacker to bypass HMAC authentication if the entry's declared compressed size exceeds the actual data length, causing premature EOF. This results in truncated, unauthenticated plaintext being accepted without error. Zero-payload entries also bypass authentication. The flaw affects versions from 0.6.0 up to but not including 9.0.0 and is fixed in version 9.0.0.
A vulnerability in the zip crate (versions >=1.3.0 <9.0.0) allows an attacker to cause an uncatchable process abort during extraction by specifying an unbounded symlink target size. The flaw arises because the symbolic-link extraction code allocates memory based on an attacker-controlled size from the ZIP central directory without bounds checking. This leads to an infallible allocation failure that aborts the process, causing denial of service. The issue is fixed in version 9.0.0.