CentreStack before 17.3 contains an unauthenticated deserialization vulnerability in GSNamespace.dll that allows unauthenticated attackers to create arbitrary local OS user accounts by supplying a crafted base64-encoded XML string to exposed API endpoints. Attackers can send a malicious StorageConfigure parameter to the jsonimportuserbyupn, jsonimportuserbyupnex, or japiimportuserbyupn endpoints to trigger InternalImportAdUserByUPN(), causing GladinetCloudMonitor.exe to invoke the NetUserAdd Windows API with attacker-controlled credentials and create arbitrary directories on the server filesystem.
MCP Ruby SDK is the official Ruby SDK for Model Context Protocol servers and clients. Prior to 0.23.0, MCP::Server::Transports::StreamableHTTPTransport in the mcp gem reads and parses an entire JSON-RPC POST body without a size limit, allowing an unauthenticated remote attacker to exhaust process memory. This issue is fixed in version 0.23.0.
An update is now available for the Red Hat build of Cryostat 4 on RHEL 9.
Security Fix(es):
* Apache HttpComponents Core: Denial of Service via excessive HTTP headers (CVE-2026-54399)
* Apache HttpComponents Core: Denial of Service via oversized HTTP/2 HPACK header blocks (CVE-2026-54428)
* Eclipse Vert.x: Information disclosure via improper handling of HTTP 30x redirects (CVE-2026-15075)
* Eclipse Vert.x Web Client: Information disclosure via improper cookie domain validation (CVE-2026-15076)
* SeaweedFS: Information disclosure via S3 API gateway path traversal (CVE-2026-55874)
* SeaweedFS: Unauthorized data deletion via path traversal in S3 gateway (CVE-2026-58372)
* protobufjs: Denial of Service via crafted .proto schema (CVE-2026-59877)
* Quarkus REST: Unbounded multipart MIME part-header accumulation allows remote OOM denial of service (CVE-2026-16308)
* Netty: Denial of Service via SPDY header decompression amplification (CVE-2026-55833)
* Netty: Denial of Service via SPDY SETTINGS frame processing (CVE-2026-55831)
* Netty codec-haproxy: Denial of Service via crafted PROXY protocol v2 message (CVE-2026-55851)
* Netty: Denial of Service via memory exhaustion in SPDY-to-HTTP codec (CVE-2026-56745)
* Netty: Security control bypass allows unauthorized requests via null origin header (CVE-2026-56746)
* Netty: Denial of Service via HTTP/2 DATA frame memory leak (CVE-2026-56819)
* Netty: Memory exhaustion in netty-codec-http (decompression bomb) (CVE-2026-59899)
* Apache Thrift: Denial of Service via integer overflow or wraparound (CVE-2026-55969)
* Apache Thrift: Denial of Service via improper handling of highly compressed data (CVE-2026-48586)
* Apache Thrift: Denial of Service due to uncontrolled resource allocation (CVE-2026-45112)
* brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation (CVE-2026-69152)
* ip-address: Inconsistent IP address parsing leads to Server-Side Request Forgery (SSRF) and trust-boundary bypass (CVE-2026-69192)
* jackson-core: Denial of Service via incomplete fix in async JSON parser (CVE-2026-68494)
* DOMPurify: Cross-site scripting vulnerability allows code execution (CVE-2026-49978)
* OpenTelemetry-Go: Denial of Service via oversized baggage headers (CVE-2026-41178)
* Go net/url: Denial of Service from quadratic complexity in path resolution (CVE-2026-56860)
* Go encoding/xml: Denial of Service via XML decoding recursion depth issue (CVE-2026-56859)
* Go html/template: Cross-Site Scripting via pathological input (CVE-2026-56858)
* Go crypto/tls: Denial of Service via indefinite KeyUpdate messages (CVE-2026-56862)
* Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal (CVE-2026-33818)
* js-yaml: Denial of Service via crafted YAML documents (CVE-2026-59869)
* golang.org/x/crypto/ssh: Authentication bypass due to unenforced source-address restrictions (CVE-2026-56854)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
The WP CTA plugin for WordPress up to version 2.1.2 contains a Server-Side Request Forgery (SSRF) vulnerability via the 'sticky_s_media' parameter in imported JSON files. This vulnerability allows authenticated users with Administrator-level access to make arbitrary web requests from the server, potentially accessing internal services. The plugin uses file_get_contents() on user-supplied URLs validated only by FILTER_VALIDATE_URL, which does not block internal IP addresses. The response from these requests is saved as WordPress media attachments, enabling full-read SSRF.
The npm package '@finxsecdemo/utils' versions 1.0.2 and 1.0.3 contain malicious code that executes during installation. The postinstall.js script performs an HTTPS GET request and DNS resolution to a hardcoded external domain, sending system information such as hostname, user info, and environment variables. This behavior effectively leaks the installer's source IP and DNS resolver IP to an attacker-controlled server. Additionally, the package's main function returns corrupted output that can disrupt consumers displaying formatted currency. This malicious activity occurs regardless of the package's labeling as a 'dependency confusion PoC.'
Style Dictionary versions from 4.3.0 up to but not including 5.4.4 contain a prototype pollution vulnerability in the convertTokenData utility function. This vulnerability allows a malicious user to inject tokens with keys like '{__proto__.foo}', which pollutes the global Object.prototype. The vulnerability affects direct usage of convertTokenData as well as indirect usage via the Expand API or the transform lifecycle. The impact is highest when Style Dictionary is integrated into NodeJS server applications, moderate for web applications, and low when token data is tightly controlled. A patch is available in version 5.4.4. Workarounds include sanitizing token data to reject keys containing '__proto__' and disabling the expand feature.
A Server-Side Request Forgery (SSRF) vulnerability exists in koxudaxi datamodel-code-generator versions from 0.9.1 up to but not including 0.61.0. The tool silently dereferences attacker-controlled JSON Schema $ref HTTP or HTTPS URLs, potentially allowing SSRF attacks. This issue is resolved in version 0.61.0.
MedusaHVNC is a newly identified remote access trojan (RAT) offered as malware-as-a-service that uses a hidden virtual desktop to steal live Windows sessions. It operates by opening a browser on a hidden desktop on the victim's machine, allowing attackers to access active logged-in sessions with the victim's browser profile, including cookies and session states. The infection chain involves multiple stages, including obfuscated JScript, AutoIt decryption, and payload injection into a trusted Windows process. The malware communicates with a hard-coded command-and-control server to enable remote control and data exfiltration.
GitHub MCP Server is GitHub's official MCP Server. Prior to 1.1.0, the CompletionsHandler function in pkg/github/server.go accesses params.Ref without first checking whether it is nil, so a completion/complete request with a missing or empty ref field triggers a nil pointer dereference and a Go runtime panic; because the crash occurs before any authentication or token validation, any unauthenticated client able to send JSON-RPC messages can crash the server, resulting in a complete denial of service. This issue is fixed in version 1.1.0.
Let's Chat 0.4.0 through 0.4.8 contains a null dereference vulnerability that allows authenticated attackers to crash the server by supplying a valid 24-character hex string room parameter that matches no document in the database. Attackers can send a crafted GET /messages request causing an uncaught TypeError in an asynchronous Mongoose callback that terminates the Node.js server process, with the same defect reachable through multiple code paths including the socket.io interface.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (7f6774653f487db8fbb9b40f1c1aba2bf959edffae409445162b0d245a3bedf1)
The @yancyyu/agentcli package installs a telemetry worker (dist/telemetry-worker.bundle.mjs) that is started by `agentcli init` / `agentcli usage start` and auto-started via macOS launchd. The worker enumerates every lark-cli (Feishu) profile stored on the host — decrypting macOS Keychain-wrapped AES-256-GCM `.enc` files under `~/Library/Application Support/lark-cli/` and Windows DPAPI-protected values under `HKCU\Software\LarkCli\keychain` — refreshes each token, and batch-POSTs `{app_id, app_secret, access_token, refresh_token}` for every profile every 5 minutes to a hardcoded default endpoint `http://47.112.24.153` (plain HTTP, bare IPv4, no TLS). The endpoint constant `DEFAULT_OPENHERMIT_CLOUD_BASE_URL` is the single default for the credential batch upload and conversation/usage pipelines when no override env var or settings value is present. The enumeration is not limited to AgentCli-created profiles; every lark-cli profile on the machine is harvested. The `reportAllLarkCredentials` code comment states: "enumerate all personal lark-cli profiles, refresh each, then read current credentials [...] batch the complete eligible set to the server." The postinstall step additionally rewrites the optional `cc-connect` dependency's installer to prepend third-party China GitHub mirror hosts (gh-proxy.com, ghproxy.net) in front of upstream release URLs before the cc-connect native binary is downloaded and executed, broadening the trust boundary for that binary. Feishu (Lark) `app_id` + `app_secret` combined with valid access/refresh tokens allow full impersonation of the affected tenant applications; sending them cleartext to a bare IPv4 over HTTP additionally exposes them to any on-path observer.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (5a2e867e455a79a59e233b1536348eca9ba4b72c217997c4ceea032e7a5ad2fe)
Xerohub_Voice.js exfiltrates the caller-supplied Discord user token to a hardcoded discord.com webhook owned by the package author. startVoiceJoiner() calls sendToDeveloperBackend, which posts a message containing the raw token, the Discord username, the target guild ID, and the target voice channel ID via axios.post to a fixed discord.com/api/webhooks/1528726419046404196/... URL used as a fallback whenever DISCORD_WEBHOOK_URL is unset. The exfil fires unconditionally before the voice logic runs, so any consumer of the advertised 'discord voice client' functionality leaks their Discord auth token — full account takeover material — along with the username and target server/channel metadata to the author on first use. Neither the token exfiltration nor the identity/metadata relay is documented.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (066cb7d27a71055b89630648ee5ae6eed64d6db93e883de66a5db678cfa7663c)
xerohub-discord-voice-v2 advertises itself as a Discord voice-channel joiner but its exported startVoiceJoiner() flow covertly forwards the caller's Discord USER_TOKEN and USER_TOKEN_2 (raw Discord account credentials), along with username, server and channel identifiers, to a hardcoded author-controlled Discord webhook constant DEVELOPER_BACKEND_WEBHOOK via a sendToDeveloperBackend() helper in Xerohub_Voice.js. In version 1.9.0 the webhook URL is still the literal placeholder 'https://discord.com/api/webhooks/YOUR_DEV_WEBHOOK_ID/YOUR_DEV_WEBHOOK_TOKEN' and a guard short-circuits the axios.post call, so no tokens leave the machine in this specific version — but the exfiltration path is fully implemented and only requires the author to substitute a real webhook ID and token in a subsequent publish for every caller's Discord credentials to be silently transmitted. The package also depends on discord.js-selfbot-v13 and drives a selfbot Client using the user's raw account token, indicating the intended targets are users pasting real Discord account credentials rather than bot tokens. Thai-language comments in the source describe the mechanism as a hidden 'developer backend'. The covert relay of caller-supplied account credentials to an author endpoint conflicts with the package's stated purpose as a voice joiner.
Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.
A Server-Side Request Forgery (SSRF) vulnerability exists in Next.js versions 14.1.1 through 15.5.20 and 16.0.0 through 16.2.10. The flaw allows an attacker to cause the server to send outbound requests to malicious hosts by controlling Host-associated headers when Server Actions forward or redirect requests. This affects applications where the incoming host header is not fixed to a trusted value, typically in custom server setups or deployments not behind a host-pinning proxy. Managed hosting and certain Next.js configurations from version 14.2 onward are not affected. The issue has been fixed in versions 15.5.21 and 16.2.11.
Improper control of generation of code in the JSON Pointer-to-accessor compiler in Cribl Stream before 4.18.2 allows a remote authenticated attacker with edit privileges to execute arbitrary JavaScript on the server via a crafted database connection identifier or pack configuration value.
Next.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 contain a vulnerability where server-side fetch calls with a request body may return cached response bodies from different requests to the same URL but with different bodies. This can cause confidential data leakage between unauthorized requests. The issue arises when fetch is called with differing init parameters, leading to unsafe caching behavior. The vulnerability has been fixed in versions 15.5.21 and 16.2.11.
Next.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 have a vulnerability where server-side fetches with request bodies may return cached response bodies from different requests sharing the same URL but different bodies. This can lead to confidential data leakage in POST response bodies when the request body uses a non-UTF-8 charset. The issue is fixed in versions 15.5.21 and 16.2.11.
Next.js versions 13.0.0 through 15.5.20 and 16.0.0 through 16.2.10 have a vulnerability where requests to applications using App Router with Server Actions running on the Edge runtime can cause excessive memory consumption. This resource allocation issue is fixed in versions 15.5.21 and 16.2.11.
Next.js versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10 have a vulnerability where Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts. This affects applications using App Router and Server Actions, allowing information disclosure that bypasses authentication on affected pages. The issue is fixed in versions 15.5.21 and 16.2.11.