CVE-2026-133990 is a vulnerability in Cockpit-HQ Cockpit versions 2.14.0 and 2.14.1 affecting the cron.php file in the Web Worker component. It allows remote attackers to bypass authentication by manipulating the token argument. Exploitation requires a high level of complexity and is considered difficult. Public exploit code is available, but no vendor response or patch has been provided.
@fastify/express versions before 4.0.10 have a vulnerability where the request URL passed to Express middleware can differ from the path dispatched by Fastify's router. This mismatch occurs due to double decoding of encoded characters and special request targets, causing path-scoped middleware like authentication or rate-limiting to be bypassed. An unauthenticated attacker can exploit this to reach protected route handlers without triggering middleware protections. The issue is fixed in version 4.0.10.
@fastify/express versions 4.0.0 through 4.0.9 have a vulnerability in case-insensitive routing where Unicode characters equivalent to ASCII letters bypass path-scoped middleware protections. This allows unauthenticated clients to reach handlers meant to be protected by authentication, authorization, or rate-limiting middleware if case-insensitive routing is enabled and the mount path contains affected letters. The issue is fixed in version 4.0.10.
@fastify/express versions 4.0.0 through 4.0.9 contain a vulnerability where path-scoped Express middleware mount paths are concatenated improperly with Fastify plugin prefixes. This causes a mismatch between the Express mount path and the Fastify route, resulting in Express middleware being silently skipped. Applications using such middleware for authentication or authorization may expose protected routes to unauthenticated clients. The issue is fixed in version 4.0.10.
@fastify/express versions 4.0.5 through 4.0.9 contain an improper authentication vulnerability due to a mismatch in route matching between the plugin and Fastify's router. This allows unauthenticated requests with empty dynamic segments to bypass middleware protections and reach protected handlers. The issue is fixed in version 4.0.10.
@fastify/express versions 4.0.7 through 4.0.9 contain an improper authentication vulnerability due to incorrect handling of regular-expression mount paths with parameterized plugin prefixes. This causes Express middleware responsible for authentication or authorization to be bypassed, exposing protected routes to unauthenticated clients. The issue is fixed in version 4.0.10.
@fastify/rate-limit versions 11.1.0 through 11.2.2 contain a vulnerability where a manual flow for limiting failed login attempts can be bypassed due to non-atomic operations. This allows an attacker to exceed the configured limit of failed login attempts in bursts. The issue is fixed in version 11.3.0 by making the slot reservation atomic.
@fastify/swagger-ui versions 2.1.0 through 6.1.4 have an authentication bypass vulnerability where static asset files served from a local directory are not protected by authentication hooks. This allows unauthenticated clients to access specification files intended to be behind authentication. The exposure is read-only and limited to files in the served directory. The issue is fixed in version 6.1.5.
@fastify/middie versions up to 9.3.7 have an authentication bypass vulnerability due to a path matching discrepancy between middie and Fastify's router. This allows unauthenticated clients to access handlers protected by middleware without special configuration. The issue is fixed in version 9.3.8.
CVE-2026-133988 is a medium severity vulnerability in Chaterm versions 0.12.0, 0.12.1, and 0.12.2 on Windows. It involves the Auto-Update Mechanism downloading code without performing an integrity check, which could allow remote attackers to deliver malicious code. The attack complexity is high and exploitation is difficult. No vendor response or patch is currently available.
Parse Server versions 2.5.0 before 8.6.121 and 9.0.0 before 9.11.1-alpha.1 contain a vulnerability where a failure to serialize an object after a beforeSave trigger can cause the server process to terminate. This occurs when a remote attacker updates an object with a dot notation key below a non-object field, such as a timestamp, leading to an uncaught exception and server crash.
Parse Server versions before 8.6.122 and 9.0.0 before 9.11.1-alpha.2 contain an authorization flaw that allows clients with write permissions to modify certain fields using dot notation keys. This bypasses beforeSave trigger protections on fields such as Object, Array, GeoPoint, Polygon, Bytes (on MongoDB), and ACL during create and update operations, potentially circumventing Cloud Code authorization checks.
SiYuan versions 3.8.0 through 3.8.9 contain an information disclosure vulnerability in the LAN sync feature. An unauthenticated attacker on the local network can impersonate a peer and cause the client to send sensitive device metadata, including sync scope ID, device name, OS, app version, and TLS client certificate, before verifying the server's authenticity. This vulnerability is fixed in version 3.8.10.
SiYuan versions 3.8.0 through 3.8.9 contain an incorrect authorization vulnerability in the serveAssets route. This flaw allows unauthenticated attackers to read password-protected document assets by exploiting name collisions. Specifically, if a visible document references an asset with the same relative name, an attacker can retrieve the protected file's contents via a GET request on public-publish instances where Basic Auth is disabled. The issue is fixed in version 3.8.10.
SiYuan versions 3.6.0 before 3.6.2 and 3.7.3 before 3.8.10 have a missing authorization vulnerability in the /api/block/getDOMText endpoint. This flaw allows anonymous users to retrieve cached OCR text of unpublished, non-encrypted assets when publish authentication is disabled, due to lack of access checks on referenced image paths.
SiYuan versions 3.8.0 through 3.8.9 contain an incorrect authorization vulnerability that allows anonymous attackers to access confidential indexed asset text. Attackers can exploit this by requesting specific API endpoints on public host documents to retrieve sensitive file contents. The issue is fixed in version 3.8.10.
SiYuan versions 3.6.0 up to but not including 3.8.10 contain an information disclosure vulnerability. Authenticated users with Reader privileges can exploit block-reference footnote resolution in Markdown export to access protected documents. This includes documents that are hidden, disabled, or password-protected, allowing disclosure of their body text without needing the publish password. The issue is fixed in version 3.8.10.
SiYuan note-taking software versions prior to 3.8.10 contain an authentication bypass vulnerability. This flaw allows unauthenticated attackers to gain Administrator privileges by exploiting the handling of the X-Forwarded-For header when requests are proxied through a trusted loopback reverse proxy. By sending requests with the Host header set to localhost and X-Forwarded-For set to 127.0.0.1, attackers can access private note history via the /history/*path endpoint if no lock-screen password is configured. The issue is fixed in version 3.8.10.
A stored cross-site scripting (XSS) vulnerability exists in the Grav Form plugin versions from 1.1.0 up to but not including 9.1.40. The vulnerability arises because the Form::uploadFiles() function only sanitizes files with a last extension of .svg, allowing files with extensions like .svg.foo to bypass sanitization. This can lead to script execution in an administrator's session, potentially enabling an attacker to create a super-admin account on Grav 2.x with Admin2.
Grav API plugin versions from 1.0.16 up to but not including 1.1.11 contain an authorization bypass vulnerability. This flaw allows scoped API key holders to override page permission rules because the system checks the owning account's authority instead of the API key's scopes. Attackers with keys minted on super-admin accounts can perform unauthorized edits, deletions, or reads on pages that normally deny those actions. Similarly, media-scoped keys can modify media on pages that are intended to be read-only. The vulnerability has a medium severity score of 5.3 and was fixed in version 1.1.11.