GEODE-10589 Remediation of GHSA-2m67-wjpj-xhg9#8015
Open
JinwooHwang wants to merge 3 commits into
Open
Conversation
marinov-code
approved these changes
Jul 13, 2026
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 pull request upgrades the jackson-core dependency to mitigate GHSA-2m67-wjpj-xhg9. This critical issue involves a document length constraint bypass where blocking, async, and DataInput parsers could accept oversized JSON documents, weakening denial-of-service protections.
Changes
Updated jackson-core to the latest secure version to ensure StreamReadConstraints and maxDocumentLength are consistently enforced.
Security Impact
Vulnerability: GHSA-2m67-wjpj-xhg9 (CVSS 7.5)
Description: Jackson's parsers previously failed to enforce configured document length constraints on the final in-memory buffer or end-of-input, allowing large documents to bypass configured limits and consume excessive CPU/memory.
Resolution: This update ensures maxDocumentLength validation executes properly across all parser pathways, effectively restoring Denial of Service (DoS) protections.
Verification
Verified that all blocking, async, and DataInput parsers properly throw a StreamConstraintsException when payloads exceed StreamReadConstraints.getMaxDocumentLength().
For all changes, please confirm:
develop)?gradlew buildrun cleanly?