Repository navigation
[SECURITY] Update dependency tools.jackson.core:jackson-core to v3.2.3 - #175
Merged
specmatic-builder merged 1 commit intoOct 5, 2026
Conversation
specmatic-builder
deleted the
renovate/maven-tools.jackson.core-jackson-core-vulnerability
branch
October 4, 2026 01:27
specmatic-builder
force-pushed
the
renovate/maven-tools.jackson.core-jackson-core-vulnerability
branch
from
October 5, 2026 00:40
c36dbc3 to
4f0c687
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.2.2→3.2.3jackson-core: UTF8DataInputJsonParser._reportInvalidToken() missing maxErrorTokenLength limit -> unbounded StringBuilder growth (DoS)
CVE-2026-89425 / GHSA-7hhh-6rmp-j9qf
More information
Details
Status
FULLY REPRODUCED. A malformed token fed through
createParser(DataInput)produced a20,000,109-character exception message from a 20-million-character attacker payload, while the
identical payload fed through
createParser(InputStream)produced a correctly bounded367-character message.
Affected Component / Version
com.fasterxml.jackson.core:jackson-corejackson-core-2.20.2src/main/java/com/fasterxml/jackson/core/json/UTF8DataInputJsonParser.java(
_reportInvalidToken(int, String, String), lines ~2763-2780 in the 2.20.2 tree)Technical Analysis
UTF8DataInputJsonParser._reportInvalidToken()builds the offending-token description for itsexception message by appending identifier characters one at a time to a bare
StringBuilder:There is no check against
ErrorReportConfiguration.getMaxErrorTokenLength()(default 256)anywhere in this loop. By contrast, the sibling
UTF8StreamJsonParserimplementation of thesame logic does enforce it:
ReaderBasedJsonParserandNonBlockingUtf8JsonParserBasealso correctly enforce the limit —this is a defect isolated to the
DataInput-backed implementation specifically, confirmed bydirect comparison of all four parser implementations in this tree.
This path is additionally left with no fallback control: because of
[core#1570]-relatedlogic in
JsonFactory, configuringmaxDocumentLengthcausesDataInput-sourced parsercreation to be rejected outright, so a document-length backstop cannot coexist with this input
source, and the identifier-character accumulation never passes through
ReadConstrainedTextBuffer, somaxStringLengthdoes not apply either. There is noconfiguration an application can set to mitigate this specific path.
Reproduction Procedure
Same clone/build steps as
jackson-core_1_...md. Then:Full PoC Source (
poc/PoC6_UnboundedErrorTokenStringBuilder.java)Captured Evidence (actual run output)
The same 20-million-character malformed token, fed to the two parser variants, produces a
367-character message via the correctly-bounded
InputStreampath and a 20,000,109-charactermessage via the vulnerable
DataInputpath — a difference of roughly 54,500x for identicalinput, confirming the missing bound is the sole cause of the difference.
Impact
Any application creating parsers via
JsonFactory.createParser(DataInput)overattacker-supplied input (a fully public, documented API) is exposed to unbounded memory growth
from a single malformed token. Scaling the payload from the 20MB demonstrated here to
gigabytes (well within a typical unbounded request body) would drive the accumulated
StringBuilder— which additionally undergoes byte-to-char expansion and internal doubling —to consume many times the raw payload size, realistically triggering
OutOfMemoryErroranddenying service to the whole JVM process. Critically, no available configuration mitigates
this:
maxDocumentLengthcannot be set forDataInputsources at all, andmaxStringLengthdoes not apply to this code path.
Remediation
maxErrorTokenLengthcheck to the append loop inUTF8DataInputJsonParser._reportInvalidToken(), appending"..."and breaking when thelimit is reached — mirroring the three other parser implementations exactly.
exception message length is bounded by
maxErrorTokenLengthplus a small constant.ParserMinimalBaseto prevent this class of per-implementation drift recurring.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot. Specmatic specific configuration is managed here.