Budibase versions 3.39.4 before 3.40.0 contain an authorization regression in the S3 attachment upload endpoint that allows BASIC users to obtain S3 PutObject presigned URLs by sending POST requests to the attachments endpoint. The route was changed from a BUILDER permission check to a TABLE/WRITE check, which BASIC users hold by default. Attackers can specify arbitrary S3 buckets in the request body to generate presigned URLs for writing to any bucket accessible by the stored IAM credentials, enabling unauthorized file uploads.
NextAuth.js provides authentication for Next.js. From next-auth 5.0.0-beta.0 until 5.0.0-beta.32, applications that gate access by checking only for the existence of the auth object returned by the auth() wrapper can fail open when Auth.js has a server configuration error. In middleware, Route Handlers, React Server Components, and other auth() entry points, a non-OK session response is parsed into a truthy error object instead of null, so checks such as !!auth and if (req.auth) evaluate to true for unauthenticated requests. A provider missing both the issuer and authorization endpoint triggers InvalidEndpoints, and an unset AUTH_SECRET or another server configuration error can produce the same behavior. There is no impact while configuration is valid, but after a deployment becomes misconfigured, routes protected only by session existence silently grant access to every visitor. This issue is fixed in next-auth 5.0.0-beta.32.
Summarize versions prior to 0.15.1 have a vulnerability in the hover summary feature that allows malicious web pages to dispatch synthetic mouseover events on attacker-controlled links. This causes the extension to make authenticated daemon requests using stored tokens without verifying the trustworthiness of the events. Attackers can exploit this to route authenticated requests through the daemon to local or private network URLs, potentially accessing sensitive internal endpoints when users interact with the malicious content. The issue is fixed in version 0.15.1.
A memory leak vulnerability exists in honojs node-server versions prior to 2.0.10. When a WebSocket upgrade request with a missing or malformed Sec-WebSocket-Key header is sent to an upgradeWebSocket route, the IncomingMessage object is retained indefinitely due to a missing cleanup path. This allows an unauthenticated attacker to cause unbounded memory growth and potentially make the service unavailable. The issue is fixed in version 2.0.10.
Starlette's HTTPEndpoint dispatches HTTP methods by lowercasing the method name and using getattr without restricting to known HTTP verbs. If an HTTPEndpoint subclass is registered via Route without specifying allowed methods, any HTTP method, including non-standard ones, can invoke attributes on the endpoint. This allows attackers to call internal methods not intended as HTTP handlers, potentially bypassing authorization checks. The issue affects Starlette versions from 0.4.3 up to but not including 0.5.5 and frameworks built on it like FastAPI. A fix is available in version 0.5.5 by explicitly specifying allowed HTTP methods in Route registrations.
NLTK's WordNet Browser application contains a reflected cross-site scripting (XSS) vulnerability in the lookup route. The flaw arises because attacker-controlled input is reflected into the HTML response without proper escaping, allowing injection of arbitrary JavaScript. This affects users running the local or self-hosted WordNet Browser HTTP service. Exploitation requires a crafted URL that triggers script execution in the browser context of the application.
OpenClaw CLI versions up to 2026.3.1 contain an authentication bypass vulnerability in the plugin route `/api/channels/*` due to a mismatch in path canonicalization depth. This allows specially encoded alternate-path requests to evade authentication checks while still resolving to protected routes. The issue is fixed in version 2026.3.2 with improved canonicalization and stricter auth enforcement.
OpenClaw CLI versions up to 2026.3.24 contain a vulnerability where sender policy resolution incorrectly downgrades a route-level group allowlist policy to open, allowing unintended interaction with bots. This affects Google Chat spaces and Zalouser groups, permitting any member of an allowlisted group to interact with the bot despite intended sender-level restrictions. The issue is fixed in version 2026.3.28.
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.3.24 contain an authorization bypass vulnerability on the HTTP /v1/models endpoint. This endpoint accepts bearer tokens but does not enforce the required operator.read scope, unlike the WebSocket RPC path which correctly enforces scope checks. As a result, operators with only operator.approvals scope can enumerate model metadata via HTTP, bypassing intended access controls. This inconsistency weakens least-privilege enforcement for operators. The issue is fixed in OpenClaw 2026.3.24.
OpenClaw CLI versions prior to 2026.3.22 contain a vulnerability in the Synology Chat multi-account configuration where webhook paths can collide. This collision allows route ownership to be replaced, bypassing direct message (DM) policy separation between accounts. The issue is fixed in version 2026.3.22 and later.
The OpenClaw CLI has a vulnerability in its HTTP /sessions/:sessionKey/history route that allows bypassing the operator read scope check. This route authenticated bearer tokens but did not enforce the operator.read permission, unlike the WebSocket chat.history route. This flaw was fixed in version 2026.3.25 by requiring operator scopes and rejecting unauthorized history reads.
A vulnerability in openclaw-cli allows scoped Gateway clients with operator.write scope to bypass admin command scope gates via inherited external chat.send routes. This enables execution of commands requiring higher privileges such as operator.approvals or operator.admin. The issue affects versions from 2026.1.29 up to but not including 2026.5.18. A patch is available in version 2026.5.18. Until upgraded, avoid granting operator.write tokens to clients that can deliver commands into sessions with external routes unless fully trusted.
OpenClaw CLI versions before 2026.4.20 contain a vulnerability in the assistant-media route where trusted-proxy callers were authenticated but the enforcement of operator scopes was missing. This allowed callers without the required operator.read scope to access assistant-media files and metadata within allowed media roots. The route still required gateway authentication and media-root checks, limiting the impact. The issue is fixed in version 2026.4.20.
OpenClaw CLI versions up to 2026.4.21 have a vulnerability where the Gateway Control UI bootstrap config endpoint does not require Gateway authentication, potentially exposing sensitive configuration fields. This issue is fixed in version 2026.4.22 by enforcing authentication on the bootstrap config route, aligning it with other authenticated Control UI reads.
OpenClaw CLI versions before 2026.4.23 have a vulnerability where webhook route secrets backed by SecretRef remain cached after rotation and reload, allowing old secrets to remain valid until a plugin or gateway restart. This weakens credential rotation by permitting continued use of stale secrets for webhook authentication. The issue is fixed in version 2026.4.23, which reloads route secrets on each request, immediately invalidating rotated secrets without requiring restarts. The severity is medium, as exploitation requires prior possession of a valid secret.
OpenClaw CLI had a security hardening update addressing canvas route access in mixed-trust or network-visible deployments. Previously, fallback authorization behavior could allow broader access than intended. The update requires explicit token or session-capability authorization and removes shared-IP fallback paths, tightening access controls. The risk is mainly for deployments exposing canvas routes beyond loopback or trusted hosts. Versions up to 2026.2.19-2 are vulnerable, with a patch targeted for 2026.2.21.