Multiple security vulnerabilities affect PostgreSQL versions prior to 17.12-1.oe2403sp4, including missing authorization checks, use-after-free, type confusion, buffer over-reads, and improper input validation. These flaws can allow database users or object creators to execute arbitrary code as the operating system user running the database, disclose server memory contents, or bypass security policies. The vulnerabilities impact PostgreSQL client programs and server components. A security update fixing these issues is available in version 17.12-1.oe2403sp4.
Miren Runtime versions prior to 0.11.1 contain a critical authentication bypass vulnerability in the RPC server's TLS client certificate verification. The server requests client certificates but fails to verify that they chain to the cluster's Certificate Authority. This flaw allows an attacker who can reach the RPC port (default :8443) to present a forged, self-signed certificate with a matching issuer Distinguished Name and gain cluster superuser access without valid credentials. The vulnerability enables full control over the cluster, including manipulation of entities, applications, and resources. A patch is available in version 0.11.1 that enforces proper client certificate chain verification. Until patched, restricting network access to the RPC port to trusted networks is recommended.
A vulnerability in atomic-server allows any authenticated agent to set the internalId property on a resource it owns without validation. The /download handler uses this internalId directly as a filesystem path without sanitization or containment checks, enabling arbitrary file read on the host. This includes sensitive files such as /etc/passwd and critically the server's root agent private key, which can lead to full server compromise. The flaw exists because the commit apply path does not restrict writable properties and the download handler trusts the stored internalId value. The vulnerability affects versions from 0.30.0 through 0.40.1. No official patch link is provided, but remediation involves sanitizing and confining the path and restricting client-settable properties.
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.
This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
CVE-2026-84869 is a critical vulnerability in ScreenConnect that allows attackers to execute malicious files on managed service provider technician workstations without user confirmation. The flaw enables malicious guests during remote support sessions to send files and trigger their execution with elevated privileges. In a documented incident, attackers installed a rogue remote access client in about nine seconds. Over 688,000 delivery attempts were observed across 42 MSP servers from 29 IP addresses between October and November. The attack involves batch scripts, PowerShell commands, and disguised ScreenConnect clients connecting to attacker-controlled infrastructure. Organizations are advised to update technician clients to version 26.6.5 or later and investigate suspicious file transfers and executions.
A vulnerability exists in Oracle Agile PLM version 9.3.6 (component: Web Client) that allows an unauthenticated attacker with network access via HTTP to potentially compromise the product. Exploitation requires user interaction by a person other than the attacker. Successful exploitation can lead to unauthorized read and write access to certain Oracle Agile PLM data. The vulnerability has a CVSS 3.1 base score of 6.1, indicating a medium severity impact on confidentiality and integrity.
A vulnerability exists in Oracle Agile PLM version 9.3.6, specifically in the Web Client component. This flaw allows an unauthenticated attacker with network access via HTTP to potentially compromise the system, requiring user interaction from a third party. Successful exploitation can lead to unauthorized read, update, insert, or delete access to certain Oracle Agile PLM data. The vulnerability has a CVSS 3.1 base score of 6.1, indicating a medium severity with confidentiality and integrity impacts.
A client-side open redirect vulnerability exists in the FreeIPA web UI component reset_password.html. This issue could allow an attacker to redirect users to arbitrary external URLs via crafted links. The vulnerability is identified as CWE-601 and affects version 4.0 of the product.
The Zephyr WebSocket client validates the server's handshake response in on_header_value() in subsys/net/lib/websocket/websocket.c. The comparison was performed as strncmp(at, str, length), where length is the length of the value the server sent rather than the length of the expected value, so the check only asked whether the received value was a prefix of the expected base64(SHA-1(key || GUID)). A server that returned a handful of correct characters passed, and a response carrying an empty Sec-WebSocket-Accept: header caused strncmp() to be called with a count of zero, which returns 0 and set ctx->sec_accept_ok with no comparison performed at all. The header-value callback also cleared ctx->sec_accept_present after the first chunk, so a value split across receive-buffer boundaries was only ever examined in part.
ctx->sec_accept_ok is the sole WebSocket-specific gate in websocket_connect(); the client does not check the HTTP status code or the Upgrade:/Connection: headers. Any HTTP response containing an empty or prefix-matching Sec-WebSocket-Accept header therefore completed the handshake, after which the socket is finalized as a WebSocket and all further peer bytes are parsed as frames. The affected path is driven directly by remote input through subsys/net/lib/http/http_parser.c, and is reached by every user of websocket_connect(), including MQTT over WebSocket (subsys/net/lib/mqtt/mqtt_transport_websocket.c) and subsys/net/lib/ocpp/ocpp.c.
The Sec-WebSocket-Accept exchange is not a secret-based authentication -- an endpoint or on-path attacker that sees the request can compute the expected value -- so the impact is bounded to parties that never observed the handshake request: a caching or transparent intermediary replaying a canned response, an off-path attacker injecting a spoofed response, or a non-WebSocket endpoint the client was induced to talk to. For those, the per-connection binding that RFC 6455 requires the client to enforce provided no protection at all, letting a single crafted response convince the device it holds a live WebSocket session and causing it to send application data to, and accept frames from, an unverified peer. There is no memory-safety consequence.
The fix compares each delivered chunk against the expected value at the position reached so far, refuses a chunk that would overrun it, and accepts only once every byte of the expected value -- and no more -- has been matched; on_header_field() now also clears the flag for any other header so a partial value cannot be continued across an intervening header.
thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in the fetchClientSecret Next.js server action that allows unauthenticated attackers to create Stripe checkout sessions for other teams. Attackers can invoke the action with a forged Team object containing a victim's stripeCustomerId to obtain Growth plan Checkout session client secrets with attacker-influenced return URLs.
@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response finishes or errors. When a client completes an upload and then disconnects before the handler writes the reply, for example while the handler scans, hashes or forwards the file, the response only emits a close event, the cleanup hook never runs, and the saved files are left on disk. An unauthenticated client can repeat this cheaply to exhaust disk space and deny service to applications that save uploaded files to disk. The issue is fixed in @fastify/multipart 10.1.4, and users should upgrade to 10.1.4 or later. As a workaround, avoid saving request files for untrusted clients, or clean the saved files from a close handler on the raw response so removal also happens when the client disconnects.
@fastify/proxy-addr determines which network hops are trusted proxies and backs Fastify's trustProxy setting, so that forwarded headers can be believed. In versions 3.0.0 through 5.1.2, when trustProxy is configured with a zoned IPv6 link-local address, the trust comparison checks only the address bits and ignores the zone identifier, so a host on another link of a multi-homed server that carries the same link-local address is trusted as well. Such an attacker can spoof the X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto headers, making the client IP, host and protocol reported by Fastify attacker-chosen values and defeating IP allowlists, rate limiting and audit logging. Exploitation requires a multi-homed server whose trustProxy is a zoned link-local address and an attacker directly on one of its other links; the default configuration and global, private or loopback trust entries are not affected. The issue is fixed in @fastify/proxy-addr 5.1.3, and users should upgrade to 5.1.3 or later. As a workaround, avoid trusting a zoned link-local address on a multi-homed host and trust a global, private or loopback proxy address instead.
Cyrus SASL versions through 2.1.28 have an authentication bypass vulnerability in the SRP server mechanism. The flaw occurs because the server does not reject certain client public values, allowing unauthenticated clients to authenticate as any user without a password. This vulnerability can lead to full compromise of confidentiality and integrity of sessions.
The gateio-client package on PyPI contains malicious code that exfiltrates basic host information such as IP address and username upon installation or import. The package overrides the install command to execute this malicious behavior. It serves no legitimate purpose beyond this data exfiltration.
This is a Request for Comments (RFC) open for community review until December 11, 2026, proposing a design for a cloud mirror system searchable by AI assistants where the server never stores the user's encryption key. The design aims to enhance data confidentiality by encrypting messages client-side and limiting server knowledge to token hashes and encrypted keys. It acknowledges limitations such as potential key exposure on a compromised server, deterministic search tag leakage, and lack of end-to-end encryption with AI providers. The RFC solicits feedback on cryptographic design choices, key rotation, token lifetimes, attestation, and other architectural questions.
OpenTelemetry JavaScript is the OpenTelemetry JavaScript client. From 0.204.0 until 0.222.0, @opentelemetry/instrumentation-http writes the raw query string from incoming HTTP requests to the url.query server-span attribute without applying the redactedQueryParams protection used for outgoing spans. Services receiving signed URLs or other credentials in query parameters can therefore export still-valid secrets to tracing backends, where observability infrastructure and users with span-read access may read them. The redactedQueryParams option does not protect incoming spans in affected versions. This issue is fixed in version 0.222.0.
Authentication bypass by spoofing vulnerability in Apache APISIX.
On a route where multi-auth falls back from wolf-rbac to another successful authenticator, client-supplied Wolf identity headers can remain in the request. A downstream service that relies on those documented headers may therefore receive an identity that was not established by the successful authenticator.
This issue affects Apache APISIX: from 3.8.0 through 3.19.0.
Users are recommended to upgrade to version 3.20.0, which fixes the issue.
Multiple security vulnerabilities have been identified and fixed in the OpenSSH implementation used by Red Hat Enterprise Linux 8.4. These include local man-in-the-middle attacks on X11 forwarding, client-side denial of service due to double free errors, sftp client file location control by attackers, security bypasses in forwarding and tunneling options, information disclosure via compression side-channels, credential disclosure through failed GSSAPI authentication, denial of service via oversized decompressed packets, and command injection via unvalidated usernames. Red Hat has released an important security update addressing these issues.
Akaunting 3.3.0 contains a stored cross-site scripting vulnerability in custom invoice payment terms. An authenticated Manager can save a crafted custom payment-term value. When an authorized user opens Invoice Settings for the same company, Akaunting inserts the stored value into a client-side event-handler expression, causing attacker-controlled JavaScript to execute in the victim's authenticated origin.