Skip to main content
CVE-2026-133234VulnerabilityPublished

Stoatchat before 0.16.5 contains an unbounded JXL image decoding vulnerability in revolt_files decode_image that

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133234· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.16.5 soon.

Data as of 19 Nov 2026, 19:21 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.5
Patch
Available – fixed in 0.16.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade stoatchat to 0.16.5.

Affected software

ProductAffectedFixed in
stoatchatstoatchatAffected
  • <0.16.5
Fixed in
  • 0.16.5
crates.iostoatchatpkg:cargo/stoatchatOther threatsAffected
  • <0.16.5
Fixed in
  • 0.16.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version 0.16.5 or later of Stoatchat addresses this vulnerability. Users should upgrade to version 0.16.5 or newer to remediate the issue. No other mitigation or temporary workaround is documented.

Description

Stoatchat versions before 0.16.5 have a vulnerability in the JXL image decoding function used by the revolt_files decode_image component. This flaw allows unauthenticated attackers to cause excessive memory allocation by requesting a specially crafted large JXL image (e.g., 12000x12000 pixels) via the /proxy endpoint. Exploitation results in out-of-memory (OOM) conditions that crash the january service, causing denial of service for proxy and embed functionalities.

References

Community reviews

Loading reviews…