CVE-2026-122676 is a Blind SQL Injection vulnerability in the PublishPress Authors plugin affecting versions prior to 4.20.0. This flaw allows an attacker with low privileges to execute crafted SQL commands that can expose sensitive data. The vulnerability has a high severity score of 8.5 and impacts confidentiality and availability. A fix is available in version 4.20.0.
The npm package sirens-lamentt version 99.0.2 contains malicious code that executes a postinstall script. This script sends an HTTPS GET request to a hardcoded webhook.site URL, transmitting the installer's IP address and install event data to a third-party collector. The behavior is consistent with a dependency confusion attack probe targeting internal package names.
Guard Core versions prior to 3.13.0 contain a vulnerability where the X-Forwarded-For (XFF) header is extracted without IP address validation and used directly in Redis key names and KEYS glob patterns. This allows attacker-controlled strings to cause cross-client counter contamination, unbounded Redis key growth, blocking Redis scans, and potential server errors due to unhandled exceptions. The issue affects deployments where the extracted XFF entry is attacker-controllable and trusted proxies are configured. No data exposure is reported. A fix is available in version 3.13.0 that validates the IP and escapes glob metacharacters or replaces the KEYS command usage.
Guard-core versions prior to 3.13.0 in enhanced detection mode preprocess input by collapsing all whitespace, including CR and LF characters, before pattern matching. This preprocessing removes the CRLF characters required by two built-in detectors (http_split and cmd_injection), causing them to miss payloads that include CRLF sequences. As a result, HTTP response splitting and newline-anchored command injection payloads evade detection, although other attack types remain detected. The issue is fixed in version 3.13.0 by preserving CRLF during whitespace collapse or adjusting detection to run on preprocessed content.
A quadratic regular-expression denial of service (ReDoS) vulnerability exists in guard-core's built-in template-injection detection pattern starting from version 3.5.0 up to but not including 3.13.0. This flaw allows unauthenticated remote clients to freeze the asyncio event loop of applications embedding guard-core by sending specially crafted requests containing repeated '{' characters. The vulnerable pattern executes without timeout protection, causing the event loop to block for seconds per request without triggering detection or rate limiting. This regression was introduced in version 3.5.0, undoing previous protections. The issue is fixed in version 3.13.0.
k8s-mcp-server versions prior to 1.1.0 running in default SSE transport mode expose an unauthenticated HTTP endpoint on port 8080 bound to all interfaces. This endpoint allows any network-accessible client to enumerate and invoke Kubernetes tools, including destructive operations, without authentication. The server does not enforce authorization or origin checks, and the default configuration permits state-changing commands. This vulnerability is due to missing authentication on critical functions and is classified as CWE-306.
CodeWhale versions 0.8.67 and earlier contain a vulnerability in the interactive Agent profile where certain shell commands are auto-approved without user prompt. This occurs because commands classified as "parallel read-only" such as 'fd', 'rg', and 'git grep' bypass the approval prompt despite having flags that enable arbitrary external program execution. The flaw allows silent remote code execution on the developer host by executing attacker-controlled commands without explicit approval. The issue is fixed in version 0.9.0.
Multiple security issues affecting the nginx HTTP/2 implementation were disclosed in November 2026. AWS acknowledges these issues and recommends upgrading to nginx versions 1.30.7 (stable) or 1.31.9 (mainline) where the vulnerabilities have been addressed. AWS is also deploying mitigations globally. These vulnerabilities occur at the HTTP/2 protocol layer before a full HTTP request is formed, limiting the effectiveness of AWS WAF rules in detecting or blocking exploitation attempts.
CodeWhale versions 0.8.67 and earlier have a vulnerability where the automation subsystem's auto_approve setting defaults to true, bypassing task-path hardening fixes. This allows a single approved automation_create call to create a durable, recurring, fully auto-approved agent that runs mutating tools without human approval. If allow_shell is enabled, this leads to recurring silent remote code execution. The issue is fixed in version 0.9.0.
A regular expression denial of service (ReDoS) vulnerability exists in eml-parser versions prior to 3.0.4 in the Received-header parsing function. The vulnerability arises from a dynamically constructed regex with multiple greedy capture groups followed by a normalized date literal that may not match the original header line, causing catastrophic backtracking with O(n^4) complexity. This leads to high CPU usage and can hang parser workers on crafted email headers. The issue is fixed in version 3.0.4.
A vulnerability in containerd's image manifest processing causes the containerd daemon to crash when handling images with a malformed digest in a subject-annotated descriptor. This can disrupt container operations, especially in Kubernetes environments where repeated image pull retries can repeatedly crash containerd on worker nodes. The issue is fixed in containerd versions 2.2.10, 2.3.7, and 2.4.2. Users should update to these versions or restrict image pulls to trusted registries as a workaround.
The Model Context Protocol (MCP) Python SDK versions 1.9.1 through 1.29.1 and 2.0.0 through 2.1.1 contain a vulnerability in their OAuth client implementation. The SDK does not properly validate the authorization server issuer metadata and does not bind stored client credentials to a specific authorization server. This allows a malicious or compromised MCP server to redirect OAuth credentials to an attacker-controlled authorization server, potentially exposing client secrets and authorization codes. The issue affects OAuth clients using certain providers and connecting to untrusted MCP servers. Fixed in versions 1.30.0 and 2.2.0, the fix includes strict issuer validation and credential binding. Users should upgrade and rotate credentials if exposure is suspected.
Mistune versions prior to 3.3.4 contain a quadratic-time denial-of-service vulnerability in the parse_link_href function. This occurs due to an unbounded parenthesis scan triggered by empty-label links, causing excessive CPU usage when rendering crafted markdown inputs. The issue is fixed in version 3.3.4.
Mistune versions prior to 3.3.4 contain a quadratic-time denial-of-service vulnerability in the inline image parsing logic. The vulnerability arises because certain guards intended to limit processing time are bypassed for image syntax, causing excessive CPU usage when parsing crafted markdown input with repeated image openers. This can cause a single unauthenticated request to consume 100% CPU on a worker, significantly degrading service availability. The issue is fixed in version 3.3.4.
A vulnerability in tiny-secp256k1 versions >=2.1.0 <2.2.5 and >=2.2.2 <2.2.5 allows an invalid tweak operation to be accepted due to a stale buffer comparison after a wasm failure. Specifically, the three-argument form of xOnlyPointAddTweakCheck ignores the wasm failure return and compares an unchanged input buffer, causing it to incorrectly validate an invalid derivation when the tweak results in the point at infinity. This flaw is fixed in version 2.2.5.
A vulnerability in fzf's zsh completion script allows local users on multi-user hosts to pre-create a FIFO path in /tmp as a symlink to victim-writable files, causing those files to be overwritten with attacker-influenced content. This can lead to arbitrary file overwrite and potential code execution at the victim's next login. The issue arises because the script uses a predictable FIFO path based on the shell PID and does not properly check the success of removing or creating the FIFO. Kernel protections such as fs.protected_symlinks may block exploitation on modern systems. A fix is available in version 0.74.5.
The fzf-tmux script in fzf versions prior to 0.74.5 improperly validates layout size arguments in attached form options (-l/-u), allowing bash arithmetic expansion to execute arbitrary commands. Additionally, unquoted tmux popup geometry options enable injection of tmux flags, leading to command execution via environment variable sourcing. This local vulnerability requires attacker-controlled input to layout arguments and affects the invoking user. A fix is available in version 0.74.5.
The npm package webhook-easy version 1.1.0 contains malicious code that executes arbitrary JavaScript fetched from a remote, attacker-controlled URL. This code decrypts and evaluates the fetched content at runtime, enabling remote code execution. The package also includes shadow dependencies that mimic Node.js core modules, potentially introducing additional malicious behavior. This activity is unrelated to the package's stated purpose and represents a supply chain compromise.
CVE-2026-133435 is a vulnerability in Red Hat Build of Keycloak where case-insensitive database collation causes realm URLs to be resolved regardless of letter casing. This allows remote attackers to bypass upstream reverse proxy access controls that depend on case-sensitive path matching, potentially exposing restricted internal authentication endpoints. The internal authentication mechanisms of Keycloak remain unaffected. The CVSS score is 3.7, indicating low severity.
sqlite-mcp versions prior to 0.1.2 allow bypassing read-only mode protections via statement chaining in execute_query and SQL injection in describe_table. This enables unauthorized write access to databases intended to be read-only, reading arbitrary SQLite files, and creating new SQLite files where the server process can write. The server lacks built-in authentication and listens on all interfaces by default, increasing exposure risk. The issue is fixed in version 0.1.2 by disabling ATTACH, enforcing query-only mode, rejecting multi-statement queries, and parameterizing inputs.