19 vulnerabilities across 15 products scored HIGH or above on October 30, 2026.
- π΄ CRITICAL: 1
- π HIGH: 18
Exploit Status Upgrades
The following CVEs from previous bulletins have been upgraded based on new exploit intelligence:
- [UPGRADED] CVE-2026-115893 (bytecodealliance/wasmtime) β F1: theoretical β poc, AAS: 9.1 β 11.6 (HIGH β HIGH). Originally in 2026-10-23 bulletin.
π΄ [CRITICAL] clickhouse/clickhouse
1 CVE | CVSS 4.0: 9.5 | AAS 12.1
cpe:2.3:a:clickhouse:clickhouse:*:*:*:*:*:*:*:*
ClickHouse Server is affected by a critical remote code execution vulnerability (CVE-2026-116366, CVSS 9.5) that allows an unauthenticated attacker with network access to execute arbitrary code under certain conditions. A functional exploit is available, significantly increasing the risk of active exploitation. Organizations running ClickHouse Server should immediately consult the vendor security changelog at clickhouse.com and apply available patches or mitigations without delay.
- π΄ CVE-2026-116366 (CVSS 4.0: 9.5)
π [HIGH] chamilo/chamilo-lms
1 CVE | CVSS 3.1: 8.9 | AAS 11.1
cpe:2.3:a:chamilo:chamilo-lms:*:*:*:*:*:*:*:*
Chamilo LMS versions 2.0.0 through 2.0.1 are affected by a high-severity stored cross-site scripting vulnerability (CVE-2026-45144, CVSS 8.9) in which user-editable profile fields are rendered without sanitization, allowing any authenticated user to inject malicious HTML and JavaScript viewable by other users and administrators. Self-registration, when enabled, allows anonymous attackers to obtain the student role needed to exploit this flaw. Organizations running Chamilo LMS should upgrade to version 2.0.1 or later immediately and review the referenced commit for patch details.
- π CVE-2026-45144 (CVSS 3.1: 8.9)
π [HIGH] givanz/vvveb
1 CVE | CVSS 3.1: 9.8 | AAS 10.9
cpe:2.3:a:givanz:vvveb:*:*:*:*:*:*:*:*(< 1.0.8.7)
Vvveb CMS versions prior to 1.0.8.7 are affected by a critical authentication bypass vulnerability (CVE-2026-110799, CVSS 9.8) in the password reset functionality, where insufficient validation of user and token parameters allows an attacker to take over arbitrary accounts without authentication. This flaw is exploitable and could lead to full compromise of any Vvveb-powered site. Administrators should upgrade to version 1.0.8.7 immediately and review account activity for signs of unauthorized access.
- π CVE-2026-110799 (CVSS 3.1: 9.8)
π [HIGH] gravity_forms/gravity_forms
1 CVE | CVSS 3.1: 9.8 | AAS 10.6
cpe:2.3:a:gravity_forms:gravity_forms:*:*:*:*:*:*:*:*
The Gravity Forms plugin for WordPress versions up to and including 3.1.2 is affected by a critical PHP Object Injection vulnerability (CVE-2026-103039, CVSS 9.8) through Post Custom Fields configured with the List input type, where submitted values are passed to an unrestricted deserialization function instead of the plugin’s hardened alternative. Successful exploitation could allow an attacker to inject arbitrary PHP objects, potentially leading to remote code execution depending on available gadget chains in the WordPress environment. Site administrators using Gravity Forms should update beyond version 3.1.2 immediately and audit any Post Custom Field configurations using the List input type.
- π CVE-2026-103039 (CVSS 3.1: 9.8)
π [HIGH] flowiseai/flowise
1 CVE | CVSS 4.0: 9.0 | AAS 10.5
cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*
Flowise versions through 3.1.4 are affected by a high-severity sandbox escape vulnerability (CVE-2026-119978, CVSS 9.0) that allows authenticated users to execute arbitrary operating system commands by abusing allowlisted modules to break out of the vm2 sandbox when the ALLOW_BUILTIN_DEP configuration is enabled. An attacker can submit crafted JavaScript through the custom function API to write and load malicious code, gaining command execution as the Flowise process user. Organizations running Flowise should upgrade beyond version 3.1.4, disable ALLOW_BUILTIN_DEP if not required, and restrict access to the custom function API endpoint.
- π CVE-2026-119978 (CVSS 4.0: 9.0)
π [HIGH] canonical/lxd
1 CVE | CVSS 4.0: 10.0 | AAS 10.3
cpe:2.3:a:canonical:lxd:*:*:*:*:*:*:*:*
Canonical LXD versions 4.0.14, 5.0.10, 5.21.8, and 6.9 are affected by a critical certificate validation flaw (CVE-2026-112816, CVSS 10.0) in the HTTPS listener that allows an unauthenticated attacker to impersonate any trusted client using a crafted certificate chain, granting full access to the cluster and all managed virtual machines. This vulnerability impacts any network-exposed LXD deployment and represents a complete compromise of the container and VM management plane. Administrators should immediately upgrade to LXD 4.0.15, 5.0.11, 5.21.9, or 6.10.1 and audit cluster access logs for unauthorized authentication events.
- π CVE-2026-112816 (CVSS 4.0: 10.0)
π [HIGH] funnelkit/funnelkit_automations
1 CVE | CVSS 3.1: 9.8 | AAS 10.1
cpe:2.3:a:funnelkit:funnelkit_automations:*:*:*:*:*:*:*:*(< 3.8.7)
FunnelKit Automations (formerly WP Marketing Automations) for WordPress versions up to and including 3.8.6.1 are affected by a critical unauthenticated PHP Object Injection vulnerability (CVE-2026-39738, CVSS 9.8) that requires no authentication to exploit, potentially enabling remote code execution depending on available gadget chains in the WordPress installation. This is a widely used marketing automation plugin and the unauthenticated attack vector makes exposed sites especially high risk. Site administrators should update FunnelKit Automations beyond version 3.8.6.1 immediately and review server logs for indicators of exploitation.
- π CVE-2026-39738 (CVSS 3.1: 9.8)
π [HIGH] ladybirdbrowser/ladybird
1 CVE | CVSS 3.1: 8.8 | AAS 10.1
cpe:2.3:a:ladybirdbrowser:ladybird:*:*:*:*:*:*:*:*(< 209579c96473c75bd5eba9701fcadb841a045964)
The Ladybird web browser is affected by a high-severity use-after-free vulnerability (CVE-2026-119332, CVSS 8.8) in the JavaScript engine’s FinalizationRegistry cleanup logic, where an attacker-controlled callback can trigger iterator invalidation leading to use of freed memory during garbage collection finalization. Exploitation through crafted web content could allow arbitrary code execution in the context of the browser process. Users and developers building on Ladybird should update to commit 209579c or later immediately.
- π CVE-2026-119332 (CVSS 3.1: 8.8)
π [HIGH] internlm/lmdeploy
1 CVE | CVSS 4.0: 9.3 | AAS 9.9
cpe:2.3:a:internlm:lmdeploy:*:*:*:*:*:*:*:*(>= 0.9.0)
InternLM LMDeploy versions 0.9.0 through 0.18.0 are affected by a critical unauthenticated remote code execution vulnerability (CVE-2026-119706, CVSS 9.3) in the /update_weights API endpoint, where attacker-supplied base64-encoded pickle data is deserialized without validation, allowing arbitrary operating system command execution as the API server process. Any network-accessible LMDeploy deployment is at immediate risk, and the exploit requires no authentication. Organizations running LMDeploy should upgrade beyond version 0.18.0, restrict network access to the API server, and audit logs for suspicious requests to the /update_weights endpoint.
- π CVE-2026-119706 (CVSS 4.0: 9.3)
π [HIGH] sqlite/sqlite
4 CVEs | CVSS 4.0: 8.5 | AAS 9.8
cpe:2.3:a:sqlite:sqlite:*:*:*:*:*:*:*:*
SQLite through version 3.54.1 is affected by four vulnerabilities (including CVE-2026-119586, CVSS 8.5), the most severe of which is a command injection flaw in the command-line shell’s .recover command that allows a crafted database to embed malicious dot-commands in schema values, executing arbitrary OS commands when recovery output is piped into sqlite3. Given SQLite’s near-universal deployment across operating systems, applications, and embedded devices, these issues have an exceptionally broad attack surface. Organizations should upgrade SQLite beyond version 3.54.1 and exercise caution when using the .recover command against untrusted database files.
- π CVE-2026-119586 (CVSS 4.0: 8.5)
- π CVE-2026-119374 (CVSS 4.0: 8.5)
- π CVE-2026-119379 (CVSS 4.0: 8.5)
- π CVE-2026-119373 (CVSS 4.0: 8.5)
π [HIGH] dlundquist/sniproxy
1 CVE | CVSS 4.0: 8.7 | AAS 9.3
cpe:2.3:a:dlundquist:sniproxy:*:*:*:*:*:*:*:*
sniproxy through version 0.7.0 is affected by a high-severity denial-of-service vulnerability (CVE-2026-119760, CVSS 8.7) where a remote unauthenticated attacker can crash the daemon by sending a TLS SNI name or HTTP Host header of 254 or 255 characters matching a wildcard backend, then closing the connection to trigger a NULL pointer dereference in resolv_cancel(). This allows trivial, repeatable service disruption of any internet-facing sniproxy deployment. Administrators should upgrade beyond version 0.7.0 and consider implementing connection-level input validation or rate limiting to mitigate exploitation.
- π CVE-2026-119760 (CVSS 4.0: 8.7)
π [HIGH] morpheus65535/bazarr
1 CVE | CVSS 3.1: 10.0 | AAS 9.3
cpe:2.3:a:morpheus65535:bazarr:*:*:*:*:*:*:*:*
Bazarr, the subtitle management companion for Sonarr and Radarr, versions prior to 1.5.7-beta.14 are affected by a critical authentication bypass vulnerability (CVE-2026-61826, CVSS 10.0) in the Plex OAuth API namespace, where missing authentication decorators allow unauthenticated attackers to clear Plex credentials, disable integrations, or persist attacker-controlled API keys without any authorization. This effectively grants full anonymous control over the Bazarr instance and its media server integrations. Users should upgrade to version 1.5.7-beta.14 or later immediately and verify that no unauthorized API keys or credential changes have been made.
- π CVE-2026-61826 (CVSS 3.1: 10.0)
π [HIGH] socfortress/copilot
2 CVEs | CVSS 3.1: 10.0 | AAS 9.3
cpe:2.3:a:socfortress:copilot:*:*:*:*:*:*:*:*
SOCFortress CoPilot prior to version 0.1.77 is affected by two critical vulnerabilities including at least one rated CVSS 10.0 (CVE-2026-61738, CVE-2026-61728), the most severe involving a path traversal flaw in the ScoutSuite GCP report upload endpoint where unsanitized filenames from multipart headers allow authenticated users to write arbitrary files to the server filesystem. Exploitation could lead to remote code execution on the CoPilot backend, compromising the security operations platform itself. Organizations running CoPilot should upgrade to version 0.1.77 or later immediately and audit file upload logs for any suspicious activity.
- π CVE-2026-61738 (CVSS 3.1: 10.0)
- π CVE-2026-61728 (CVSS 3.1: 9.9)
π [HIGH] mqttsnet/thinglinks
1 CVE | CVSS 3.1: 9.9 | AAS 9.2
cpe:2.3:a:mqttsnet:thinglinks:*:*:*:*:*:*:*:*(< 1.4.0)
ThingLinks, an enterprise IoT platform, versions prior to 1.4.0 are affected by a critical remote code execution vulnerability (CVE-2026-62853, CVSS 9.9) in the rule engine’s Groovy script test and registration endpoint, where user-supplied Groovy code is compiled and executed on the server without sandboxing, allowing any authenticated attacker to run arbitrary commands. Given the platform’s role in managing IoT infrastructure, compromise could extend to connected devices and operational technology environments. Organizations should upgrade to ThingLinks version 1.4.0 immediately and restrict access to the script registration endpoint.
- π CVE-2026-62853 (CVSS 3.1: 9.9)
π [HIGH] openvm-org/openvm
1 CVE | CVSS 4.0: 8.7 | AAS 9.1
cpe:2.3:a:openvm-org:openvm:*:*:*:*:*:*:*:*(>= 1.0.0, < 1.7.0)
OpenVM, a modular zkVM framework, versions before 1.7.0 and affected 2.0/2.1 prereleases contain a high-severity proof verification bypass vulnerability (CVE-2026-62334, CVSS 8.7) where the Halo2 verifier contract’s use of staticcall with user-controlled proof data allows an attacker to route execution to a non-verifier function by crafting proof bytes whose leading selector matches another exposed function, causing invalid proofs to be accepted as valid. This directly undermines the integrity of zero-knowledge proof verification and could allow forged state transitions or fraudulent claims on any system relying on OpenVM verification contracts. Teams deploying OpenVM-based verifiers on-chain should upgrade to version 1.7.0 or later immediately and audit any proofs accepted by affected contract versions.
- π CVE-2026-62334 (CVSS 4.0: 8.7)