Eclipse Parsson
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Eclipse Parsson.
By the Year
In 2026 there have been 1 vulnerability in Eclipse Parsson with an average score of 7.5 out of ten. Parsson did not have any published security vulnerabilities last year. That is, 1 more vulnerability have already been reported in 2026 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 1 | 7.50 |
| 2025 | 0 | 0.00 |
| 2024 | 1 | 7.50 |
| 2023 | 1 | 7.50 |
It may take a day or so for new Parsson vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Eclipse Parsson Security Vulnerabilities
Eclipse Parsson: JSON Parser DOS via No Max Consumption (before 1.1.8)
CVE-2026-9563
7.5 - High
- July 02, 2026
In Eclipse Parsson published Maven Central artifacts before version 1.1.8, the JSON parser did not enforce a default maximum on the number of characters consumed while parsing a single JSON document. Applications that parse attacker- controlled JSON can be forced to consume excessive CPU and memory by processing very large documents, including large arrays, objects, strings, numbers, whitespace, or nested structures, resulting in a denial of service. Eclipse Parsson 1.1.8 introduces a configurable maximum parsing limit with a default limit of 15 million parser-consumed characters.
Resource Exhaustion
Eclipse Parsson 1.0.4/1.1.3 Stack Overflow DoS
CVE-2023-7272
7.5 - High
- July 17, 2024
In Eclipse Parsson before 1.0.4 and 1.1.3, a document with a large depth of nested objects can allow an attacker to cause a Java stack overflow exception and denial of service. Eclipse Parsson allows processing (e.g. parse, generate, transform and query) JSON documents.
Memory Corruption
Eclipse Parsson before 1.1.4, untrusted JSON number parsing causing DoS
CVE-2023-4043
7.5 - High
- November 03, 2023
In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from untrusted sources can lead malicious actors to exploit the fact that the built-in support for parsing numbers with large scale in Java has a number of edge cases where the input text of a number can lead to much larger processing time than one would expect. To mitigate the risk, parsson put in place a size limit for the numbers as well as their scale.
Excessive Iteration
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Eclipse Parsson or by Eclipse? Click the Watch button to subscribe.
