CVE-2026-88778 is a high-severity vulnerability in Citrix NetScaler ADC and Gateway involving predictable exact values derived from previous values. This weakness can affect versions before 14.1-73.37 and 13.1-64.23 for ADC and Gateway products, including certain FIPS and NDcPP variants. The vulnerability is classified under CWE-342, indicating issues with predictable values that may weaken security mechanisms.
AzuraCast versions prior to 0.23.6 have a vulnerability where the Liquidsoap API endpoint lacks the RequireInternalConnection middleware and incorrectly derives the AutoDJ flag from header presence instead of a validated value. This allows users with View station permission to inject arbitrary now-playing metadata, disrupt live broadcasts, and disclose filesystem paths.
http4k's Digest authentication module (org.http4k:http4k-security-digest) before versions 6.48.0.0, 5.42.0.0 and 4.51.0.0 defaults the nonceVerifier parameter of ServerFilters.DigestAuth and DigestAuthProvider to { true }, so every nonce is accepted regardless of its value, age, or prior use. Applications relying on this default have no replay protection on Digest authentication: an attacker who can capture a valid 'Authorization: Digest' response (for example by observing network traffic or reading logs) can replay it indefinitely against the same protected resource.
http4k (Maven package org.http4k:http4k-core) before 6.49.0.0, 5.42.0.0 and 4.51.0.0 uses substring (Contains) matching on the Host header by default in reverseProxy() and reverseProxyRouting() when dispatching to configured virtual hosts. If these functions are deployed as a public-facing inbound HTTP handler with two or more configured virtual hosts, a remote attacker can supply a Host header that merely contains a configured vhost name (for example Host: admin.evil.com for a vhost configured as "admin") and be routed to that vhost, bypassing routing-based authorization. The intended outbound-dispatch and test-time uses, where the Host value is set by the calling application, are not affected.
The miniOrange OTP Login, Verification and SMS Notifications plugin for WordPress is vulnerable to Authentication Bypass via the mo_wp_login_intent parameter in all versions up to, and including, 5.5.5. This is due to a missing password-intent guard in the skip_pass_fallback-enabled configuration branch of the mo_by_pass_login() function, which treats administrator role membership alone as sufficient authentication whenever the unauthenticated, unverified POST parameter mo_wp_login_intent is submitted with the value otp, causing mo_get_user() to skip wp_authenticate_username_password() and resolve a WP_User purely from a username lookup. This makes it possible for unauthenticated attackers to log in as any existing administrator account by supplying only a known username and an empty password alongside mo_wp_login_intent=otp, with no password or OTP verification required. Exploitation is conditional on a site administrator having simultaneously enabled the following plugin options: WP Login OTP, Login with Only OTP, Allow Users to Login with Username and Password, and Admin OTP Bypass.
Netty's HTTP/3 codec versions 4.2.0.Final through 4.2.17.Final do not enforce the RFC 9114 requirement that the :authority pseudo-header and the literal host header, when both are present, must have the same value. This flaw allows a remote unauthenticated attacker to send a HEADERS frame with conflicting authority values, potentially bypassing routing, virtual-host, and access-control decisions. The issue is fixed in version 4.2.18.Final.
Nodemailer versions 5.0.0 through 10.0.1 have a vulnerability in their DNS caching mechanism where the cache key is only the DNS host, but cache entries also store a caller-specific TLS servername. This causes the wrong SNI value to be sent when multiple TLS transports resolve the same host with different servernames, leading to incorrect certificate validation. An attacker able to prime the cache can cause a victim to connect to the attacker's TLS host and accept a malicious certificate, potentially exposing SMTP credentials. The issue is fixed in Nodemailer version 10.0.2.
Adminer versions from 5.5.1 through 6.0.1 contain a server-side request forgery (SSRF) vulnerability due to improper parsing of the login 'server' string. This allows a remote unauthenticated attacker to craft a server value that bypasses privileged-port restrictions and causes the server to initiate TCP connections to arbitrary internal hosts and ports before authentication. This vulnerability enables blind internal port scanning and was fixed in version 6.0.2.
A stored cross-site scripting (XSS) vulnerability exists in Hugo versions 0.75.0 through 0.165.x. The issue arises because the syntax highlighter does not properly escape the lineAnchors option before passing it to Chroma, which inserts the value directly into HTML attributes. This allows an attacker to inject arbitrary JavaScript into the generated pages if untrusted Markdown content is published. The vulnerability is fixed in version 0.166.0 by HTML-escaping the lineAnchors value before use.
Grav CMS 2.0.14 through 2.0.24 contains a privilege escalation vulnerability in the group and account blueprints. The access map is gated by a `security@: admin.super` guard that is resolved by the field's exact path, so a submitted flat dot-notation key such as `access.admin.super` (instead of the nested `access[admin][super]`) matches no blueprint rule, survives BlueprintSchema::filterArray() and flattening, and is written by FlexObject::update() via setNestedProperty(), which splits on `.` and reconstructs the nested value. An authenticated backend operator using the flex accounts backend who holds admin.users but not admin.super can therefore grant admin.super to their own account or to a group they belong to and escalate to full super-admin, gaining control over configuration, plugin and theme installation, the file manager, and all accounts. Fixed in 2.0.25, which drops any dotted key whose ancestor path is disabled or marked validate.ignore.
SiYuan v3.8.3 fails to HTML-escape the data-subtype attribute when generating gutter-button markup (app/src/protyle/gutter/button.ts, assigned via innerHTML in app/src/protyle/gutter/index.ts) from content pasted as plain-text Markdown containing a Kramdown inline attribute list (IAL). Because the shared Lute renderer parses Kramdown IAL from text/plain input, an attacker-supplied Markdown snippet using entity-encoded quotes in data-subtype breaks out of the attribute value when the gutter markup is re-parsed by the browser, injecting additional attributes such as autofocus and onfocus. If a victim pastes the crafted Markdown and the affected gutter control receives focus, the injected handler executes; in the Electron desktop application, where the main BrowserWindow enables Node integration and disables context isolation, this results in JavaScript execution with renderer Node.js privileges (remote code execution). Fixed in v3.8.4.
Capgo (capgo.app) is affected by an authorization flaw in the app icon update path. The PUT /app/:id endpoint accepts a user-controlled `icon` value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's own image namespace (e.g. org/{owner_org}/{app_id}/...). Updating apps.icon_url fires the on_app_update trigger, whose worker reads record.icon_url and calls cleanStoredImageMetadata(), which runs with service-role credentials (supabaseAdmin()) and downloads and re-uploads the referenced storage object with upsert: true. As a result, an authenticated holder of an app-limited write API key can cause the privileged worker to rewrite an out-of-scope private image object (for example an organization logo) that the key cannot read or write directly under Supabase Storage RLS. All versions are affected; no patched version was available at the time of the advisory.
OpenClaw is an npm-distributed application. In versions >= 2026.4.25 and < 2026.8.1, the workspace environment-variable filter did not block variables ending in `_ENDPOINT`, so an untrusted workspace `.env` file could set AZURE_SPEECH_ENDPOINT. Azure Speech preferred that value over the configured region, so when a synthesis or voice-list request was made, the attacker-selected endpoint received the operator's Azure Speech key in the request header, allowing the key to be reused against the operator's Azure Speech resource. Exploitation requires an operator to start OpenClaw in attacker-controlled workspace content with Azure Speech configured with a key and region and no trusted endpoint override set. The issue is fixed in 2026.8.1.
OpenClaw (npm package 'openclaw') versions >= 2026.3.28 and < 2026.8.1 allow an untrusted workspace .env file to set the CLOUDSDK_PYTHON_ARGS environment variable. When an operator starts OpenClaw in attacker-controlled workspace content and then runs the Gmail setup flow, that value is inherited when gcloud is launched, and the gcloud launcher passes it as arguments to the trusted Python interpreter. A crafted CLOUDSDK_PYTHON_ARGS value can therefore cause Python to execute attacker-supplied code with the OpenClaw host user's permissions, allowing credentials to be read, files to be modified, or other processes to be started. This issue is fixed in version 2026.8.1; as a workaround, run Gmail setup only from trusted workspaces and clear inherited CLOUDSDK_* variables beforehand.
CVE-2026-92842 is a medium severity heap-based buffer overflow vulnerability in PHP related to the convert.base64-encode, convert.quoted-printable-encode, and convert.quoted-printable-decode stream filters. The issue arises because the filters accept a line-break-chars option whose length is tracked separately from the string itself. The filter constructors duplicate the value using pestrdup(), which stops at the first NUL byte but retains the original length. This discrepancy allows the filter to read past the allocated buffer when emitting a line break, potentially leaking adjacent heap memory into the output.
CVE-2026-91765 is a high-severity vulnerability in the PHP SOAP XML parser where the cleanup_xml_node() function recurses without a depth limit. This allows an unauthenticated attacker to send a SOAP request with extremely deep nesting, causing stack exhaustion and crashing the SoapServer process. The unbounded recursion also affects the SOAP value decoder and WSDL node search helper.
GLPI is a free asset and IT management software package. From 0.70 until 10.0.26 and 11.0.8, a technician can manipulate the authtype value through the API to change another user's authentication method. Under configurations using the legacy API REST interface or SSO logins, this can change a super-administrator's authentication method and enable account takeover. This issue is fixed in versions 11.0.8 and 10.0.26.
CVE-2026-67222 is a vulnerability in RabbitMQ server versions from 3.13.0 up to but not including 3.13.15, 4.0.20, 4.1.11, and 4.2.6. It involves the improper handling of the auth_mechanism value in the Shovel or Federation plugins, which can cause permanent consumption of Erlang VM atoms and lead to a node crash. Exploitation requires specific plugin usage and permissions. The issue has been fixed in the stated versions.
RabbitMQ versions from 3.13.0 up to but not including 3.13.15, and versions 4.0.20, 4.1.11, and 4.2.6 contain a vulnerability in the stream protocol. The FrameMax value negotiated during the Tune handshake was stored but not validated against inbound frame lengths, allowing a remote client to send oversized frames. This can cause excessive memory usage and lead to denial of service. The issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
CVE-2026-67409 is a vulnerability in RabbitMQ server versions from 3.13.0 up to but not including 3.13.18, and similarly in 4.0.x, 4.1.x, 4.2.x, and 4.3.x prior to fixed versions. The issue arises because the JWKS key fetching mechanism does not validate HTTP response status codes when retrieving signing keys from the OAuth2 provider. As a result, error responses with valid JSON but missing keys cause all cached signing keys to be destroyed, leading to persistent denial of OAuth2/JWT authentication until a successful refresh occurs. This can cause a denial of service affecting all users relying on OAuth2 authentication.