CVE-2026-18401— FasterXML Jackson-core 资源管理错误漏洞
一分钟漏洞结论
影响对象
FasterXML jackson-core
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
FasterXML Jackson-core是FasterXML组织开源的一个JSON处理库。 FasterXML Jackson-core 2.15.0至2.18.5版本、2.19.0至2.21.0版本和3.0.0至3.0.x版本存在资源管理错误漏洞，该漏洞源于非阻塞（异步）JSON解析器未强制执行StreamReadConstraints中定义的maxNumberLength约束，可能导致攻击者提交任意长度数字令牌，造成过度内存分配和CPU耗尽，导致拒绝服务。
影响版本矩阵 6
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| FasterXML | jackson-core | 2.15.0≤ 2.18.5 |
affected |
2.18.6 |
unaffected | ||
2.19.0< 2.21.1 |
affected | ||
2.21.1 |
unaffected | ||
3.0.0< 3.1.0 |
affected | ||
3.1.0 |
unaffected |
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-18401 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
jackson-core: Number length constraint bypass in non-blocking (async) JSON parser leads to potential denial of service
来源: CVE Program / CVE List V5
Vulnerability Description
The non-blocking (asynchronous) JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints (default: 1000 characters). An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length, leading to excessive memory allocation and potential CPU exhaustion, resulting in a denial of service.
The synchronous parser enforces this limit correctly, so the constraint is applied inconsistently depending on which parsing API the application uses.
Root cause: the async parsing path in NonBlockingUtf8JsonParserBase and related classes never invokes the number length validation methods. Number parsing methods such as _finishNumberIntegralPart() accumulate digits into the TextBuffer without any length check, then call _valueComplete() to finalize the token. _valueComplete() does not call resetInt() or resetFloat(), which are the methods in ParserBase where validateIntegerLength() and validateFPLength() are performed. Because that validation step is skipped, maxNumberLength is never enforced on the async code path.
Impact: an attacker sending a JSON document containing an arbitrarily long number to an application using the async parser (for example a Spring WebFlux or other reactive application) can cause unbounded allocation in the TextBuffer and an OutOfMemoryError. If the application subsequently calls getBigIntegerValue() or getDecimalValue(), the JVM may additionally be tied up in O(n^2) BigInteger parsing, causing CPU-based denial of service.
No privileges or user interaction beyond the ability to submit data for parsing are required.
This issue affects com.fasterxml.jackson.core:jackson-core from version 2.15.0 through 2.18.5 and from 2.19.0 through 2.21.0, and tools.jackson.core:jackson-core from 3.0.0 through 3.0.x.
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-72hv-8253-57qq records the lower bound of the affected 2.x range as 2.0.0.
来源: 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:L/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.5版本、2.19.0至2.21.0版本和3.0.0至3.0.x版本存在资源管理错误漏洞，该漏洞源于非阻塞（异步）JSON解析器未强制执行StreamReadConstraints中定义的maxNumberLength约束，可能导致攻击者提交任意长度数字令牌，造成过度内存分配和CPU耗尽，导致拒绝服务。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
| 厂商 | 产品 | 影响版本 | CPE | 订阅 |
|---|---|---|---|---|
| FasterXML | jackson-core | 2.15.0 ~ 2.18.5 | - |
|
| FasterXML | jackson-core | 3.0.0 ~ 3.1.0 | - |
|
二、漏洞 CVE-2026-18401 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-18401 的情报信息
请登录查看更多情报信息。
CVE-2026-18401 补丁与修复 (2)
CVE-2026-18401 厂商安全公告 (1)
IV. Related Vulnerabilities
V. Comments for CVE-2026-18401
暂无评论