Repository navigation
fix(deps): update dependency com.fasterxml.jackson.core:jackson-core to v2.18.11 [security] - #493
Open
renovate[bot] wants to merge 1 commit into
Conversation
…to v2.18.11 [security]
renovate
Bot
requested review from
NicoPiel,
gibson9583,
jonbartels,
kpalang,
ssrowe and
tonygermano
October 16, 2026 17:01
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:
2.18.8→2.18.11jackson-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).
jackson-core: ReDoS: quadratic backtracking in NumberInput.PATTERN_FLOAT via looksLikeValidNumber()
CVE-2026-89407 / GHSA-p6pp-m3f8-5c89
More information
Details
Status
FULLY REPRODUCED with a clean, textbook empirical signature: measured runtime grew almost
exactly 4x for every doubling of input size across five consecutive doublings (5,000 → 160,000
characters), confirming O(n²) behavior. A single 160,000-character string (smaller than a typical
HTTP request body) took 74.4 seconds for one call to
NumberInput.looksLikeValidNumber().Affected Component / Version
com.fasterxml.jackson.core:jackson-corejackson-core-2.20.2src/main/java/com/fasterxml/jackson/core/io/NumberInput.java(
PATTERN_FLOATline ~41-42,PATTERN_FLOAT_TRAILING_DOTline ~51, entry pointlooksLikeValidNumber()lines ~646-656)Technical Analysis
PATTERN_FLOATcontains ambiguous, adjacent quantifiers over the identical character class:[0-9]*(optional digits), an optional[.], then[0-9]+(required digits). Java'sbacktracking
Pattern/Matcherengine has no possessive quantifiers or atomic grouping here,so on a non-matching input the engine must explore every possible split point between the
[0-9]*and[0-9]+groups before concluding failure — the classic quadratic-backtrackingshape.
looksLikeValidNumber()compounds the cost by running a second full-string regex(
PATTERN_FLOAT_TRAILING_DOT) whenever the first fails, roughly doubling the constant factorwithout changing the asymptotic class.
Critically, the length gate that applies to this specific path is
StreamReadConstraints.maxStringLength(default 20,000,000), notmaxNumberLength(default 1,000) — the length ceiling the library uses everywhere else for numeric content.
This means inputs up to four orders of magnitude larger than the library's own numeric-length
policy reach this quadratic regex unmodified.
Reproduction Procedure
Same clone/build steps as
jackson-core_1_...md. Then:Full PoC Source (
poc/PoC8_NumberInputReDoS.java)Captured Evidence (actual run output)
This is an unusually clean empirical result: five consecutive doublings each produced a ratio
between 3.78x and 4.14x — matching the theoretical O(n²) prediction (ratio = 4.0x) to within
5% at every single measurement, leaving essentially no ambiguity about the complexity class.
Extrapolating this measured curve, a ~1MB string (well within common request body limits) would
take on the order of hours for a single call.
Impact
Any application that coerces a String-typed JSON field to a number (default
jackson-databindbehavior) is exposed: an attacker who can submit a large numeric-looking string (up to
maxStringLength's default of 20,000,000 characters — far larger than needed given themeasured curve) can pin a request-handling thread for an extended period with a single request.
Because the cost scales quadratically, a handful of concurrent moderately-sized requests
(tens to low hundreds of KB each) is sufficient to exhaust a typical web server's worker thread
pool, denying service to all users.
Remediation
PATTERN_FLOATwithout quantifier ambiguity using possessive quantifiers, e.g.[+-]?(?:[0-9]++(?:\.[0-9]*+)?|\.[0-9]++)(?:[eE][+-]?[0-9]++)?, which also folds in thetrailing-dot case and removes the need for a second full-string scan.
file already contains exactly this pattern for
parseInt, so the library has both theprecedent and the code style available.
maxNumberLength, not the much largermaxStringLength) before callinglooksLikeValidNumber(), closing the four-orders-of-magnitude gap between the two constraints for this specific code path.
StreamReadConstraints.maxStringLengthwell below itsdefault, and set wall-clock timeouts on parse/coercion operations.
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: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.