
jackson-databind + jackson-core 26 条安全公告自查:按坐标逐条求交集给出真正到位的版本(2.18.11/2.21.7/2.22.3/3.1.7/3.2.3,2.21.6 已不够);扫源码降噪告诉你真中几条;含 1 条 GitHub 全局库未收录、Dependabot 不报的(jackson-core 那条,升了 databind 也照样中) CVE-2026-54515 / CVE-2026-54512
A self-check tool for all 26 security advisories covering jackson-databind + jackson-core. Zero-dependency single jar, no network access.
It answers three questions that Dependabot cannot:
CVE-2026-68498 in jackson-core (see the "v0.3.0" section).@JsonView / polymorphic types / case-insensitive matching…), reducing "you have an affected version installed" to "you actually hit that feature."java -jar jackson-check.jar ./target ./src
On 09-30 and 10-01, FasterXML published 4 more high-severity advisories (all 7.5, all denial of service):
| ID | Coordinate | Subject | Trigger condition |
|---|---|---|---|
| CVE-2026-91776 | jackson-databind | Every unknown type id leaves an entry in a process-lifetime cache; memory only grows | @JsonTypeInfo(use = Id.NAME, defaultImpl = …) + attacker can control the type id + mapper is reused long-term |
| CVE-2026-91777 | jackson-databind | When forward references are resolved in reverse order, the number of comparisons is about N²/2 (N=2000 → 2,003,000 comparisons) | Deserializing untrusted JSON into a collection or Map annotated with @JsonIdentityInfo |
| CVE-2026-89425 | jackson-core | A malformed token is concatenated in full into the exception message, not subject to maxErrorTokenLength | Only the createParser(DataInput) path; the advisory states no configuration can mitigate it |
| CVE-2026-89407 | jackson-core | Quadratic backtracking in the NumberInput.looksLikeValidNumber() regex (measured 74.4 seconds on 160,000 characters) | Binding a string in JSON to a numeric field (databind's default behavior); this path is constrained by maxStringLength (default 20 million) rather than maxNumberLength (default 1000) |
The fixed versions for both coordinates share the same numbers: 2.18.11 / 2.21.7 / 2.22.3 / 3.1.7 / 3.2.3 (all downloadable from Central; 89407 is fixed in 3.2.2 on the 3.2 line, while 89425 requires 3.2.3 — take the higher one).
So the 2.18.10 / 2.21.6 / 2.22.2 / 3.1.6 / 3.2.2 printed by v0.2.0 / v0.3.0 have been insufficient since 09-30. Older versions' jars won't know about this — please switch to v0.4.0 and rescan.
⚠️ These four are not Dependabot blind spots: they entered the GitHub global advisory database on the day they were published, and Dependabot will alert on them normally. v0.4.0 incorporates them only to keep the answer to "which version should I upgrade to" correct.
🔴 Also correcting a claim from v0.2.0: the statement in the "v0.2.0" section below that "those 4 are not included in the GitHub global advisory database, and Dependabot won't report them" held as of 09-14 but no longer holds as of 2026-09-28 — all four have been added to the global database (ASSERT2 in
gen_rules.pyrerun on 10-05: databind-side blind spots 4 → 0). The only one still not found isjackson-core'sCVE-2026-68498.
jackson-core is a different coordinate, and scanning databind won't find itThe entire decision table in v0.2.x had only one artifactId: jackson-databind. So the 7 advisories FasterXML published in the
jackson-core repository could not be found by this tool at all —
and it wouldn't report any error because of that; it would just silently skip every jackson-core-*.jar.
"Not scanned" and "you're safe" look exactly the same in the report.
v0.3.0 changes the decision granularity from advisory × groupId × range to advisory × groupId × artifactId × range,
and decisions, intersection computation, and "this coordinate was not scanned" are all keyed by the full coordinate.
The one to pay most attention to — CVE-2026-68498 (high 7.5, 2026-09-12):
StreamReadConstraints.maxNameLength (default 50,000 characters) does not take effect on the character-input path.
When ReaderBasedJsonParser accumulates a property name, it calls the string length limit (default 100 million, about 2000 times larger),
and the real name validation only runs after the entire key has been scanned — by which point about 200MB has already been allocated.
A single oversized JSON key is enough, and the default configuration is vulnerable.
>= 2.16.0, <= 2.18.9 → 2.18.10 · >= 2.19.0, <= 2.21.5 → 2.21.6 ·
>= 2.22.0, <= 2.22.1 → 2.22.2 · 3.x (tools.jackson.core) <= 3.1.5 → 3.1.6 · <= 3.2.1 → 3.2.2UTF8StreamJsonParser revalidates every time the buffer is expanded.
Parsing from byte[] / InputStream is unaffected; only parsing from String / Reader / char[] is affected.validateNameLength exists only in the fixed version of ReaderBasedJsonParser,
and is absent in the vulnerable versions (reproduced on all three lines: 2.18.9→2.18.10 · 2.21.5→2.21.6 · 3.1.5→3.1.6).⚠️ Tool capability boundaries, written here to avoid misinterpretation: This tool can determine jar versions, but cannot determine how you call it — for the most common pattern,
readValue(someStringVariable, …), text scanning cannot tell whether that variable is aStringor abyte[]. So "no trigger condition found" does not mean you are unaffected, and the report prints it that way too.
🔴 Do not read this as "Dependabot is completely blind to jackson-core": Of the 7
jackson-coreentries, onlyCVE-2026-68498cannot be found in the GitHub global advisory database; the other 6 are all recorded, and Dependabot alerts on them normally. This one is re-verified byASSERT-C2ingen_rules.pyon every rerun, and generation is refused if the number changes.
🔴 This section is a record from 09-14, and two points are now outdated (see "v0.4.0" above): ① These 4 were recorded in the global database on 2026-09-28, and Dependabot now reports them; ② The "fix everything at once" versions are no longer 2.18.10 / 2.21.6 / 3.1.6. The original text is kept, not deleted.
FasterXML published 4 new entries on the Security page of its own repository:
| ID | Severity | Topic | Fixed version |
|---|---|---|---|
| CVE-2026-68497 | high 7.5 | No upper limit on digit length when binding strings to javax.xml.datatype.Duration / XMLGregorianCalendar → CPU DoS (with the default mapper) | 2.18.10 / 2.21.6 / 2.22.2 / 3.1.6 / 3.2.2 |
| CVE-2026-19032 | medium 5.3 | java.nio.file.Path deserialization does not restrict the URI scheme, allowing any registered FileSystemProvider to be driven | Same as above |
| CVE-2026-83557 | medium 5.6 | The default PolymorphicTypeValidator deny list is missing Comparable | Same as above |
| CVE-2026-77310 | medium 5.3 | CVE-2026-54514 was fixed incompletely: the InetAddress branch still performs DNS resolution immediately | 2.18.9 / 2.21.5 / 2.22.1 / 3.1.5 / 3.2.1 |
Item-by-item testing: