Threat Intelligence Database

The Cryostat 4 on RHEL 9 container images have been updated to fix several bugs. Users of Cryostat 4 on RHEL 9 container images are advised to upgrade to these updated images, which contain backported patches to fix these bugs and add these enhancements. Users of these images are also encouraged to rebuild all container images that depend on these images. Security Fix(es): * golang.org/x/image: Denial of Service via malformed WEBP image parsing (CVE-2026-33813) * follow-redirects: Information disclosure via cross-domain redirects (CVE-2026-40895) * io.quarkus:quarkus-vertx-http: Authorization bypass via semicolons in HTTP requests (CVE-2026-39852) * github.com/jackc/pgx: Memory-safety vulnerability (CVE-2026-33815, CVE-2026-33816) * github.com/go-jose/go-jose: Go JOSE: Denial of Service via crafted JSON Web Encryption (JWE) object (CVE-2026-34986) * lodash: Arbitrary code execution via untrusted input in template imports (CVE-2026-4800) * netty: Denial of Service via HTTP/2 CONTINUATION frame flood (CVE-2026-33871) * io.netty/netty-codec-http: Request smuggling via incorrect parsing of HTTP/1.1 chunked transfer encoding extension values (CVE-2026-33870) * path-to-regexp: Denial of Service via crafted regular expressions (CVE-2026-4926) * undici: HTTP Request Smuggling and Denial of Service due to duplicate Content-Length headers (CVE-2026-1525) * google.golang.org/grpc: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation (CVE-2026-33186) * undici: Denial of Service via unbounded memory consumption during WebSocket permessage-deflate decompression (CVE-2026-1526) * undici: Denial of Service via invalid WebSocket permessage-deflate extension parameter (CVE-2026-2229) * undici: Denial of Service via crafted WebSocket frame with large length (CVE-2026-1528) * io.vertx/vertx-core: static handler component cache can be manipulated to deny the access to static files (CVE-2026-1002) You can find images updated by this advisory in the Red Hat Container Catalog (see the References section).

A TCP client can perform a TLS handshake and present the server name extension with a server name that is accepted by a server wildcard name, e.g.if the server is configured with a certificate accepting *.example.com, any XYZ.example.com where xyz is a valid name can be used.

In Eclipse Vert.x versions [4.0.0, 4.5.21] and [5.0.0, 5.0.4], when "directory listing" is enabled, file and directory names are inserted into generated HTML without proper escaping in the href, title, and link attributes. An attacker who can create or rename files or directories within a served path can craft filenames containing malicious script or HTML content, leading to stored cross-site scripting (XSS) that executes in the context of users viewing the affected directory listing.

LowVulnerabilityGermanyFranceUnited Kingdom+2#cve#cve-2025-11966#cwe-79

A vulnerability in the Eclipse Vert.x toolkit causes a memory leak in TCP servers configured with TLS and SNI support. When processing an unknown SNI server name assigned the default certificate instead of a mapped certificate, the SSL context is erroneously cached in the server name map, leading to memory exhaustion. This flaw allows attackers to send TLS client hello messages with fake server names, triggering a JVM out-of-memory error.

A vulnerability in the Eclipse Vert.x toolkit results in a memory leak due to using Netty FastThreadLocal data structures. Specifically, when the Vert.x HTTP client establishes connections to different hosts, triggering the memory leak. The leak can be accelerated with intimate runtime knowledge, allowing an attacker to exploit this vulnerability. For instance, a server accepting arbitrary internet addresses could serve as an attack vector by connecting to these addresses, thereby accelerating the memory leak.