Eclipse Parsson Denial of Service vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2023-4043: 0.76% estimated exploitation activity in the next 30 days; percentile 55.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

3 Nov 2023, 09:32 UTC

Last modified by the source

14 Nov 2023, 21:48 UTC

Source last checked

26 Oct 2026, 16:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g8p6-p27c-52fx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-4043

Advisory: Eclipse Parsson Denial of Service vulnerability
IDs: CVE-2023-4043, GHSA-g8p6-p27c-52fx
Record: https://patchnext.com/advisories/cve-2023-4043 (revision 1, source checked 26 Oct 2026, 16:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.parsson:project 1.1.4, 1.0.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.parsson:project: affected >= 1.1.0, < 1.1.4; < 1.0.5; fixed in 1.1.4, 1.0.5

## Suggested inspection (read-only)
- Maven org.eclipse.parsson:project: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.parsson:project.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g8p6-p27c-52fx (GitHub-reviewed advisory GHSA-g8p6-p27c-52fx lists affected ranges: Maven org.eclipse.parsson:project >=1.1.0 =0 <1.0.5)

Commands are suggestions: review each one before running it.