Lucene search
+L

20 matches found

RedhatCVE
RedhatCVE
•added 2026/08/10 10:47 a.m.•15 views

CVE-2026-18401

A flaw was found in jackson-core. The non-blocking asynchronous JSON parser does not properly enforce the maximum number length constraint. A remote attacker can exploit this by submitting a specially crafted JSON document containing an arbitrarily long number to an application using the...

6.9CVSS5.9AI score0.00408EPSS
SaveExploits0References6
IBM Security Bulletins
IBM Security Bulletins
•added 2026/08/07 10:55 a.m.•18 views

Security Bulletin: Jackson-Core Async JSON Parser Bypasses Number Length Constraint Leading to Denial of Service

Summary Jackson-core's non-blocking async JSON parser fails to enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters, unlike the synchronous parser which correctly applies the limit. An attacker can submit JSON containing arbitrarily long numbers through...

5.3AI score
SaveExploits0Affected Software1
SUSE CVE
SUSE CVE
•added 2026/08/06 1:27 a.m.•26 views

SUSE CVE-2026-18401

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

5.3CVSS6AI score0.00408EPSS
SaveExploits0References6
NVD
NVD
•added 2026/08/04 3:16 p.m.•25 views

CVE-2026-68494

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength into a new setIntLength helper and invoked it...

8.7CVSS0.00463EPSS
SaveExploits0References7
NVD
NVD
•added 2026/08/04 3:16 p.m.•44 views

CVE-2026-18401

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS0.00408EPSS
SaveExploits0References3
osv_ubuntu
osv_ubuntu
•added 2026/08/04 3:16 p.m.•20 views

UBUNTU-CVE-2026-68494

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength into a new setIntLength helper and invoked it...

8.7CVSS7.4AI score0.00463EPSS
SaveExploits0References9
osv_ubuntu
osv_ubuntu
•added 2026/08/04 3:16 p.m.•21 views

UBUNTU-CVE-2026-18401

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS6AI score0.00408EPSS
SaveExploits0References5
CVE
CVE
•added 2026/08/04 2:39 p.m.•367 views

CVE-2026-68494

This CVE notes an incomplete fix for CVE-2026-18401 in jackson-core’s non-blocking parser, leaving a remaining bypass for number-length constraints when data is streamed in many small chunks. The issue arises in the async parser path (MINOR_NUMBER_INTEGER_DIGITS) where validateIntegerLength() is ...

8.7CVSS7.4AI score0.00463EPSS
SaveExploits0References7
EUVD
EUVD
•added 2026/08/04 2:39 p.m.•23 views

EUVD-2026-52703

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength into a new setIntLength helper and invoked it...

8.7CVSS6AI score0.00463EPSS
SaveExploits0References7
Vulnrichment
Vulnrichment
•added 2026/08/04 2:39 p.m.•20 views

CVE-2026-68494 jackson-core: Async parser maxNumberLength bypass via chunked digit accumulation (incomplete fix for CVE-2026-18401 / GHSA-72hv-8253-57qq)

The fix released in jackson-core 2.18.6 and 2.21.1 for CVE-2026-18401 GHSA-72hv-8253-57qq, number length constraint bypass in the non-blocking parser is incomplete. This record covers the remaining bypass. The earlier fix wired validateIntegerLength into a new setIntLength helper and invoked it...

8.7CVSS7.2AI score0.00463EPSS
SaveExploits0References7
attackerkb
attackerkb
•added 2026/08/04 2:23 p.m.•23 views

CVE-2026-18401

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS5.7AI score0.00408EPSS
SaveExploits0References4Affected Software1
Cvelist
Cvelist
•added 2026/08/04 2:23 p.m.•66 views

CVE-2026-18401 jackson-core: Number length constraint bypass in non-blocking (async) JSON parser leads to potential denial of service

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS0.00408EPSS
SaveExploits0References3
EUVD
EUVD
•added 2026/08/04 2:23 p.m.•19 views

EUVD-2026-52699

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS5.7AI score0.00408EPSS
SaveExploits0References3
Vulnrichment
Vulnrichment
•added 2026/08/04 2:23 p.m.•14 views

CVE-2026-18401 jackson-core: Number length constraint bypass in non-blocking (async) JSON parser leads to potential denial of service

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS6AI score0.00408EPSS
SaveExploits0References3
osv_cve
osv_cve
•added 2026/08/04 2:23 p.m.•48 views

CVE-2026-18401 jackson-core: Number length constraint bypass in non-blocking (async) JSON parser leads to potential denial of service

The non-blocking asynchronous JSON parser in jackson-core does not enforce the maxNumberLength constraint defined in StreamReadConstraints default: 1000 characters. An attacker able to submit JSON to an application that uses the async parser API can supply a number token of arbitrary length,...

6.9CVSS6.1AI score0.00408EPSS
SaveExploits0References7
CVE
CVE
•added 2026/08/04 2:23 p.m.•208 views

CVE-2026-18401

The CVE describes a vulnerability in jackson-core’s non-blocking (async) JSON parser where maxNumberLength is not enforced, unlike the synchronous parser. Root cause: the async parsing path in NonBlockingUtf8JsonParserBase does not invoke number length validation; _finishNumberIntegralPart() accu...

6.9CVSS6.1AI score0.00408EPSS
SaveExploits0References3
IBM Security Bulletins
IBM Security Bulletins
•added 2026/05/04 12:24 p.m.•23 views

Security Bulletin: Jackson-core Async JSON Parser Bypasses maxNumberLength Constraint Leading to DoS

Summary The non-blocking async JSON parser in jackson-core bypasses the maxNumberLength constraint default: 1000 characters defined in StreamReadConstraints. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and...

5.8AI score
SaveExploits0Affected Software1
IBM Security Bulletins
IBM Security Bulletins
•added 2026/04/20 2:17 p.m.•17 views

Security Bulletin: DevOps Test Performance contains a vulnerability related to use of the jackson-core library

Summary Due to use of the jackson-core library, DevOps Test Performance and Rational Performance Tester contain a potential Denial of Service DoS vulnerability. Vulnerability Details ID:WS-2026-0003 DESCRIPTION: The non-blocking async JSON parser in jackson-core bypasses the maxNumberLength...

5.8AI score
SaveExploits0Affected Software1
Github Security Blog
Github Security Blog
•added 2026/02/28 2:01 a.m.•651 views

jackson-core: Number Length Constraint Bypass in Async Parser Leads to Potential DoS Condition

Summary The non-blocking async JSON parser in jackson-core bypasses the maxNumberLength constraint default: 1000 characters defined in StreamReadConstraints. This allows an attacker to send JSON with arbitrarily long numbers through the async parser API, leading to excessive memory allocation and...

6.9CVSS6AI score0.00408EPSS
SaveExploits0References5Affected Software2
Snyk
Snyk
•added 2026/02/28 2:01 a.m.•33 views

Allocation of Resources Without Limits or Throttling

Overview Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in which the non-blocking async JSON parser can be made to bypass the maxNumberLength constraint default: 1000 characters defined in StreamReadConstraints. An attacker can cause...

8.7CVSS6AI score
SaveExploits0References2
Rows per page
Query Builder