Is tools.jackson.core:jackson-core 3.0 vulnerable?
Maven · 5 releases from 3.0.0 to 3.0.4 · latest tools.jackson.core:jackson-core is 3.3.0 · checked 18 Nov 2026
Yes: 6 known advisories
Yes. tools.jackson.core:jackson-core 3.0.4, the last 3.0 release, is affected by 6 known security advisories (5 high, 1 medium), including CVE-2026-89425, CVE-2026-89407, CVE-2026-68494. Upgrade to 3.1.7 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=tools.jackson.core:jackson-core -DdepVersion=3.1.7 -DforceVersion=trueIs your project on an affected tools.jackson.core:jackson-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting tools.jackson.core:jackson-core 3.0.4
jackson-core: UTF8DataInputJsonParser._reportInvalidToken() missing maxErrorTokenLength limit -> unbounded StringBuilder growth (DoS)
- Affected
- >=3.0.0 <3.1.7 · >=3.2.0 <3.2.3
- Fixed in
- 3.1.7, 3.2.3
jackson-core: ReDoS: quadratic backtracking in NumberInput.PATTERN_FLOAT via looksLikeValidNumber()
- Affected
- >=3.0.0 <3.1.7 · >=3.2.0 <3.2.2
- Fixed in
- 3.1.7, 3.2.2
jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for GHSA-72hv-8253-57qq)
- Affected
- >=3.0.0 <3.1.4
- Fixed in
- 3.1.4
Jackson Core: Document length constraint bypass in blocking, async, and DataInput parsers
- Affected
- >=3.0.0 <3.1.1
- Fixed in
- 3.1.1
jackson-core has Nesting Depth Constraint Bypass in `UTF8DataInputJsonParser` potentially allowing Resource Exhaustion
- Affected
- >=3.0.0 <3.1.0
- Fixed in
- 3.1.0
jackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition
- Affected
- >=3.0.0 <3.1.0
- Fixed in
- 3.1.0
Every tools.jackson.core:jackson-core 3.0.x release
Affected: 3.0.0 to 3.0.4. Latest tools.jackson.core:jackson-core: 3.3.0.
| Version | Known advisories |
|---|---|
| tools.jackson.core:jackson-core 3.0.4 | CVE-2026-89425, CVE-2026-89407, CVE-2026-68494, GHSA-2m67-wjpj-xhg9, CVE-2026-29062, CVE-2026-18401 |
| tools.jackson.core:jackson-core 3.0.3 | CVE-2026-89425, CVE-2026-89407, CVE-2026-68494, GHSA-2m67-wjpj-xhg9, CVE-2026-29062, CVE-2026-18401 |
| tools.jackson.core:jackson-core 3.0.2 | CVE-2026-89425, CVE-2026-89407, CVE-2026-68494, GHSA-2m67-wjpj-xhg9, CVE-2026-29062, CVE-2026-18401 |
| tools.jackson.core:jackson-core 3.0.1 | CVE-2026-89425, CVE-2026-89407, CVE-2026-68494, GHSA-2m67-wjpj-xhg9, CVE-2026-29062, CVE-2026-18401 |
| tools.jackson.core:jackson-core 3.0.0 | CVE-2026-89425, CVE-2026-89407, CVE-2026-68494, GHSA-2m67-wjpj-xhg9, CVE-2026-29062, CVE-2026-18401 |
Which of your client projects are still on tools.jackson.core:jackson-core 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact tools.jackson.core:jackson-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other tools.jackson.core:jackson-core versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.