Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-68496— jackson-dataformats-binary: Smile parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service

Quick assessment

Affected
FasterXML jackson-dataformats-binary
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

FasterXML jackson-dataformats-binary 中的 Smile 解析器在解码 JSON 对象属性名时，从未调用 ，因此该格式未强制执行 限制。SmileParser 的 方法通过无约束的 调用不断扩展其内部名称缓冲区，且未执行任何长度验证。因此，能够提交 Smile 文档进行解析的攻击者可以嵌入一个长度无上限的属性名；无论 如何配置，解析器都会将整个名称缓冲在内存中再返回。由于 默认也是禁用的，在默认配置下没有其他机制限制名称长度，因此唯一的限制仅为攻击者的上传容量和可用堆内存，这可能导

CVSS 7.5 · High
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-68496

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
jackson-dataformats-binary: Smile parser does not enforce StreamReadConstraints.maxNameLength, enabling memory-exhaustion denial of service
Source: CVE Program / CVE List V5
Vulnerability Description
The Smile parser in FasterXML jackson-dataformats-binary never invokes StreamReadConstraints.validateNameLength() when decoding JSON object property names, so the maxNameLength limit is not enforced for this format. SmileParser._handleLongFieldName() grows its internal name buffer through an unconstrained _growArrayTo() call and performs no length validation. An attacker who can have a Smile document parsed may therefore embed a single property name of unbounded length; the parser buffers the whole name in memory before returning it, whatever maxNameLength is configured to. Because StreamReadConstraints.maxDocumentLength is also disabled by default, nothing else bounds the name under default settings, so the only limits are the attacker's upload capacity and available heap, leading to memory exhaustion and denial of service. No privileges beyond the ability to submit data to a parsing endpoint are required, and exploitation needs only that the bytes reach SmileFactory parsing, directly or through an ObjectMapper configured with the Smile module. jackson-core's own JSON parsers enforce maxNameLength incrementally during name decoding; this gap is specific to the binary formats. maxNameLength and validateNameLength were introduced in jackson-core 2.16.0, so releases before 2.16.0 do not contain the constraint that is left unenforced. This issue is tracked together with the CBOR parser defect in the same vendor advisory, GHSA-3v8f-v6vx-fmrm, which covers both binary formats. The Smile parser defect (jackson-dataformats-binary issue #726) is CVE-2026-68496; the CBOR parser defect (issue #725) is assigned CVE-2026-68495.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
不加限制或调节的资源分配
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
FasterXML jackson-dataformats-binary 2.16.0 ~ 2.18.9 -
FasterXML jackson-dataformats-binary 3.0.0 ~ 3.1.5 -

II. Public POCs for CVE-2026-68496

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-68496

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-68496 (1)

Vendor Advisories for CVE-2026-68496 (1)

News Coverage for CVE-2026-68496 (1)

Vendor Pages for CVE-2026-68496 (1)

IV. Related Vulnerabilities

Same product: jackson-dataformats-binary
Same vendor: FasterXML
Same weakness: CWE-770

V. Comments for CVE-2026-68496

No comments yet

Leave a comment