目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1359 元

100%
请我们喝杯咖啡

CVE-2026-68494— FasterXML Jackson-core 资源管理错误漏洞

一分钟漏洞结论

影响对象
FasterXML jackson-core
利用判断
存在公开或 AI PoC，应优先验证
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。

FasterXML Jackson-core是FasterXML组织开源的一个JSON处理库。 FasterXML Jackson-core 2.15.0版本至2.18.7版本、2.19.0版本至2.21.3版本、2.22.0版本、3.0.0版本至3.1.3版本和3.2.0版本存在资源管理错误漏洞，该漏洞源于非阻塞解析器在解析数字时未正确调用validateIntegerLength()函数，导致数字长度限制被绕过，攻击者通过分块流式发送JSON数据而不发送终止符，可使内存不断累积，最终导致拒绝服务。

CVSS 8.7 · High EPSS 0.62% · P48

影响版本矩阵 6

厂商产品 版本范围状态
FasterXML jackson-core 2.15.0< 2.18.8 affected
2.18.8 unaffected
2.19.0< 2.21.4 affected
2.21.4 unaffected
3.0.0< 3.1.4 affected
3.1.4 unaffected
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2026-68494 基础信息

漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗

尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。

Vulnerability Title
jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for CVE-2026-18401 / GHSA-72hv-8253-57qq)
来源: CVE Program / CVE List V5
Vulnerability Description
The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 (GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser) is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength() into a new _setIntLength() helper and invoked it wherever the integer portion of a number is decided: a terminator byte arrives, a '.' or 'e'/'E' is seen, or input ends inside a fully buffered value. It was not invoked on the attacker-relevant path where the parser runs out of input while still inside the MINOR_NUMBER_INTEGER_DIGITS minor state and returns NOT_AVAILABLE to the caller. As a result, an attacker who streams JSON to a non-blocking parser in many small chunks, without ever sending a terminator byte, keeps the parser inside MINOR_NUMBER_INTEGER_DIGITS indefinitely. _textBuffer.expandCurrentSegment() grows the accumulator on every chunk while validateIntegerLength() is never called. The accumulator is bounded only by maxStringLength (20 MiB by default) rather than by maxNumberLength (1000 by default), an amplification of roughly 20,000x over the documented limit. Because Java char values occupy two bytes, a single connection can be driven to approximately 40 MiB of heap before the validator finally fires when the value completes. The equivalent fraction-path code is correct: _finishFloatFraction() calls _setFractLength() before its NOT_AVAILABLE return. The missing call affects the integer-digit paths in _startPositiveNumber(), _startNegativeNumber() and _finishNumberIntegralPart() in NonBlockingUtf8JsonParserBase. Impact: reactive frameworks such as Spring WebFlux/Reactor, Quarkus, Helidon and Vert.x feed inbound HTTP or gRPC bytes to the async parser as they arrive, which is precisely the chunked-feed shape required. Operators who set StreamReadConstraints.maxNumberLength expecting it to cap memory per number value do not get that guarantee; memory accumulates per concurrent connection and attacker-controlled concurrency can exhaust the JVM heap. The synchronous parsers (UTF8StreamJsonParser, ReaderBasedJsonParser) and the async parser operating on complete input are not affected. Exploitation requires only the ability to stream data to a parsing endpoint; no privileges or user interaction are needed. This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.7, and from 2.19.0 through 2.21.3, and tools.jackson.core:jackson-core from 3.0.0 through 3.1.3. Versions prior to 2.15.0 are not affected, because StreamReadConstraints -- which defines the maxNumberLength setting -- was first introduced in jackson-core 2.15.0, so no such constraint exists to be bypassed in earlier releases. Note that GHSA-r7wm-3cxj-wff9 states the affected 2.x range without a lower bound. The 2.22.x and 3.2.x release lines are not affected: those branches were created after the fix commit landed on 2026-05-21 and therefore contain it from their initial releases (2.22.0, tagged 2026-06-03, and 3.2.0, tagged 2026-06-08).
来源: CVE Program / CVE List V5
CVSS Information
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
来源: CVE Program / CVE List V5
Vulnerability Type
不加限制或调节的资源分配
来源: CVE Program / CVE List V5
Vulnerability Title
FasterXML Jackson-core 资源管理错误漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
FasterXML Jackson-core是FasterXML组织开源的一个JSON处理库。 FasterXML Jackson-core 2.15.0版本至2.18.7版本、2.19.0版本至2.21.3版本、2.22.0版本、3.0.0版本至3.1.3版本和3.2.0版本存在资源管理错误漏洞，该漏洞源于非阻塞解析器在解析数字时未正确调用validateIntegerLength()函数，导致数字长度限制被绕过，攻击者通过分块流式发送JSON数据而不发送终止符，可使内存不断累积，最终导致拒绝服务。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
FasterXML jackson-core 2.15.0 ~ 2.18.8 -
FasterXML jackson-core 3.0.0 ~ 3.1.4 -

二、漏洞 CVE-2026-68494 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级
Qwen3.6-35B-A3B · 9606 chars
Pro+ 专属包含：
漏洞复现靶场录像（真实沙箱构建 + 触发，独家）
漏洞原理深度分析
触发条件与影响面
完整可执行 POC 代码
利用链与缓解建议
POC 打包下载
每月 100+ 条 AI 生成额度

三、漏洞 CVE-2026-68494 的情报信息

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

CVE-2026-68494 补丁与修复 (4)

CVE-2026-68494 厂商安全公告 (2)

CVE-2026-68494 其他参考 (1)

IV. Related Vulnerabilities

Same product: jackson-core
Same vendor: FasterXML
Same weakness: CWE-770

V. Comments for CVE-2026-68494

暂无评论

发表评论