12 vulnerabilities across 9 products scored HIGH or above on October 21, 2026.

  • 🟠 HIGH: 12

Exploit Status Upgrades

The following CVEs from previous bulletins have been upgraded based on new exploit intelligence:

  • [UPGRADED] CVE-2026-99999 (linux/linux_kernel) — F1: theoretical → poc, AAS: 10.8 → 13.3 (HIGH → CRITICAL). Originally in 2026-10-15 bulletin.

🟠 [HIGH] vllm-project/vllm

1 CVE | CVSS 4.0: 9.2 | AAS 10.2

  • cpe:2.3:a:vllm-project:vllm:*:*:*:*:*:*:*:*

vLLM versions 0.7.3 through 0.30.x contain a critical remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary Python code on the API server. The flaw exists because user-supplied parameters are forwarded to the Transformers AutoProcessor without validation, enabling an attacker who controls a model revision to trigger malicious code execution via the unauthenticated /tokenize endpoint when trust_remote_code is enabled. With a CVSS 4.0 score of 9.2 and a known exploitation path, this is a high-priority issue for any organization running vLLM inference servers, particularly those exposed to untrusted network traffic. Teams should upgrade to vLLM 0.31.0 or later immediately, and as a mitigating step, restrict access to the /tokenize endpoint and review whether trust_remote_code is strictly necessary in their deployments.

Vendor Advisory

🟠 [HIGH] smub/duplicator_–backups&migration_plugin–_cloud_backups,scheduled_backups,&_more

1 CVE | CVSS 3.1: 8.8 | AAS 10.1

  • cpe:2.3:a:smub:duplicator_backups_migration_plugin_cloud_backups_scheduled_backups_more:*:*:*:*:*:*:*:*

The Duplicator and Duplicator Pro plugins for WordPress are vulnerable to PHP Object Injection through unsafe deserialization of database content during migration operations. Duplicator Free versions through 1.5.17 and Duplicator Pro versions through 4.6.10 are affected, with a CVSS 3.1 score of 8.8, as an unauthenticated attacker can plant a malicious serialized object in public site content that executes when an administrator later performs a backup migration or import. Given Duplicator’s massive install base across WordPress sites, any organization using these plugins should update to Duplicator Free 1.5.18 or Duplicator Pro 4.6.11 and later immediately, and exercise caution when migrating packages built from sites that may have been exposed to untrusted input.

Vendor Advisory

🟠 [HIGH] triggerdotdev/trigger.dev

1 CVE | CVSS 4.0: 9.2 | AAS 10.0

  • cpe:2.3:a:triggerdotdev:trigger.dev:*:*:*:*:*:*:*:*

Self-hosted Trigger.dev Docker Compose deployments prior to version 4.5.6 are vulnerable to a complete authentication bypass due to hardcoded default secrets shipped in the example environment file. An unauthenticated attacker can forge valid magic link tokens using the known MAGIC_LINK_SECRET to log in as any user, and then pivot through runner containers to reach Postgres, Redis, and ClickHouse backends with their own default credentials, compromising all tenant data across the platform. With a CVSS 4.0 score of 9.2 and a trivially exploitable attack path, organizations running self-hosted Trigger.dev should upgrade to 4.5.6 immediately, rotate all secrets including MAGIC_LINK_SECRET and database credentials, and audit access logs for any unauthorized magic link authentication events.

Vendor Advisory

🟠 [HIGH] lovell/sharp

1 CVE | CVSS 4.0: 8.9 | AAS 9.7

  • cpe:2.3:a:lovell:sharp:*:*:*:*:*:*:*:*

Sharp, the widely used Node.js image processing library, versions prior to 0.35.4 bundle a vulnerable libheif dependency that enables remote code execution on glibc-based Linux systems when processing maliciously crafted AVIF or HEIF images. Any application that accepts untrusted image uploads and uses sharp for resizing, conversion, or manipulation is at risk, as an attacker simply needs to submit a crafted image file to trigger the underlying libheif decoding flaw. With a CVSS 4.0 score of 8.9, teams running sharp in backend image pipelines or user-facing upload services should upgrade to version 0.35.4 or later immediately, and consider restricting AVIF/HEIF input formats as a temporary mitigation where feasible.

Vendor Advisory

🟠 [HIGH] astral-sh/uv

3 CVEs | CVSS 4.0: 8.7 | AAS 9.6

  • cpe:2.3:a:astral-sh:uv:*:*:*:*:*:*:*:*

Astral uv, the popular Python package manager, versions prior to 0.8.22 are affected by 3 vulnerabilities including multiple path traversal and symlink exploitation flaws in source distribution extraction, carrying a maximum CVSS 4.0 score of 8.7. A malicious sdist package published to a registry can use crafted symlink sequences to write arbitrary files outside the intended installation directory when a victim installs it, potentially overwriting critical system or application files. Any development team or CI/CD pipeline using uv for Python dependency management should upgrade to version 0.8.22 or later immediately, and review recently installed packages from untrusted sources for signs of unexpected file modifications.

Vendor Advisory

🟠 [HIGH] openstack/manila

1 CVE | CVSS 3.1: 9.9 | AAS 9.2

  • cpe:2.3:a:openstack:manila:*:*:*:*:*:*:*:* (< 23.0.1)

OpenStack Manila versions prior to 23.0.1 contain a broken access control vulnerability in multiple API operations on public shares, where the service fails to verify that the caller actually owns the share before executing privileged actions. An authenticated tenant can exploit this to grant themselves read/write access to another tenant’s public shares, revoke the legitimate owner’s access rules, or escalate access permissions, effectively compromising cross-tenant data isolation with a CVSS 3.1 score of 9.9. Organizations running OpenStack Manila in multi-tenant environments should upgrade to version 23.0.1 or later as a high priority, audit existing public share access rules for unauthorized modifications, and consider restricting public share creation until the patch is applied.

Vendor Advisory

🟠 [HIGH] jelmer/dulwich

1 CVE | CVSS 4.0: 8.7 | AAS 9.1

  • cpe:2.3:a:jelmer:dulwich:*:*:*:*:*:*:*:*

Dulwich, the pure-Python Git implementation, versions prior to 1.2.9 contain a path validation flaw on Windows that allows arbitrary file writes outside the repository worktree by exploiting DOS drive letter prefixes in Git tree path elements. An attacker can craft a malicious Git repository with specially named tree entries that bypass NTFS path validation, enabling remote code execution when a victim clones or checks out the repository on a Windows system. With a CVSS 4.0 score of 8.7, teams using Dulwich in Windows environments or any tooling that depends on it for Git operations should upgrade to version 1.2.9 or later immediately, and treat any recently cloned repositories from untrusted sources as potentially compromised.

Vendor Advisory

🟠 [HIGH] hkuds/vibe-trading

2 CVEs | CVSS 4.0: 8.7 | AAS 9.1

  • cpe:2.3:a:hkuds:vibe-trading:*:*:*:*:*:*:*:*

HKUDS Vibe-Trading versions 0.1.0 through 0.1.6 are affected by 2 vulnerabilities including multiple indirect prompt injection and unrestricted command execution flaws, with a maximum CVSS 4.0 score of 8.7. An attacker can plant malicious instructions in documents or web pages that the AI trading agent processes, which are then passed directly to shell execution as root through BashTool and BackgroundRunTool with no sandboxing, allow-listing, or user approval, enabling full system compromise and server-side request forgery. Anyone running Vibe-Trading should upgrade to version 0.1.7 or later immediately, ensure the agent is never run with root privileges, and isolate it from production infrastructure until the patched version is deployed and verified.

Vendor Advisory

🟠 [HIGH] sveltejs/kit

1 CVE | CVSS 4.0: 8.7 | AAS 9.1

  • cpe:2.3:a:sveltejs:kit:*:*:*:*:*:*:*:*

SvelteKit versions 2.10.0 through 2.x contain a path traversal vulnerability in the Vite preview server on Windows that allows unauthenticated attackers to read arbitrary files accessible to the server process, including source code, configuration files, and credentials. Any development or staging environment where the Vite preview server is exposed to network access or shared through a tunnel is at risk, carrying a CVSS 4.0 score of 8.7. Teams using SvelteKit on Windows should upgrade to version 3.0.0 or later, ensure preview servers are not accessible beyond localhost, and audit whether any sensitive files may have been exposed through network-reachable preview instances.

Vendor Advisory