CVE-2026-133234
Stoatchat before 0.16.5 contains an unbounded JXL image decoding vulnerability in revolt_files decode_image that allows unauthenticated atta
CVSS
7.5
Alta
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 19 de nov. de 2026 · Última mod.: 19 de nov. de 2026 · CWE-789
Ainda não há histórico EPSS suficiente.
Stoatchat before 0.16.5 contains an unbounded JXL image decoding vulnerability in revolt_files decode_image that allows unauthenticated attackers to exhaust memory via the january /proxy endpoint. Attackers can request a small hosted JXL file declaring 12000x12000 pixels through /proxy to trigger huge allocations, OOM-killing january and denying proxy and embed service.
- github.comhttps://github.com/stoatchat/stoatchat
- github.comhttps://github.com/stoatchat/stoatchat/blob/v0.16.2/crates/core/files/src/implementation/media_impl.rs#L94-L99
- github.comhttps://github.com/stoatchat/stoatchat/commit/1b9997b8876b9251dd20b85a0809ae278cb5583e
- github.comhttps://github.com/stoatchat/stoatchat/releases/tag/v0.16.5
- github.comhttps://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p
- www.vulncheck.comhttps://www.vulncheck.com/advisories/stoatchat-before-0.16.5-memory-exhaustion-via-january-proxy-jxl-decoding
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-103025——
———bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. Prior to 0.17.3, imagemeta.Decode could exhaust memory when parsing PNG zTXt chunks whose keyword is "Raw profile type iptc": the declared chunk length can drive an allocation far larger than the input file, and the embedded zlib stream is decompressed without an output limit. The advisory reports a 42-byte input causing a 256 MB allocation and a 127 KB input inflating to 460 MB. The oversized-allocation path's memory effect depends on platform overcommit and configured GOMEMLIMIT or cgroup limits, while the decompression path reliably creates resident memory. Applications that decode untrusted PNGs with IPTC metadata processing can therefore suffer denial of service through memory exhaustion. This issue is fixed in 0.17.3.6hCVE-2026-62255——
———HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, cram_index_load does not verify that the number of reference sequences in a CRAM .crai index does not exceed the CRAM header reference count. A malformed index can drive unbounded index-array allocation, and when the number of references in the index is within two of INT_MAX, the growth calculation can wrap, read beyond a heap buffer, and use the resulting value as a pointer for an unchecked memory write. Any region query can trigger the flaw, causing denial of service or memory corruption. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24.5hCVE-2026-1083236.5 MÉD—
——0Tanium addressed an uncontrolled resource consumption vulnerability in Tanium Client.12hCVE-2026-1318446.5 MÉD41.1%
——12Poppler through 26.11.0 contains an uncontrolled memory allocation vulnerability in the libcurl-based remote file loader that trusts unvalidated HEAD Content-Length values in CurlCachedFileLoader::init(). Malicious HTTP servers can return an enormous Content-Length so CachedFile resizes its chunk cache accordingly, aborting pdfinfo or PDFDocFactory-based applications with std::bad_alloc for denial of service.1dCVE-2026-651675.5 MÉD6.5%
——2NVIDIA TensorRT contains a vulnerability where a user could cause memory allocation with excessive size value by crafting a malicious TRT engine. A successful exploit of this vulnerability might lead to denial of service.2dCVE-2026-911417.5 ALT50.4%
——15A vulnerability in the default configuration of vsomeip allows a remote, unauthenticated attacker to trigger massive memory allocations by sending a small TCP packet with a large, attacker-declared SOME/IP length field. This can lead to immediate service termination via OOM-kill on memory-constrained systems or total host memory exhaustion through repeated connections.2d