Crash when decoding malformed HTTP requests or malformed JSON payload

Exploitation

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

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2018-1330: 3.74% estimated exploitation activity in the next 30 days; percentile 89.88 (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.

When parsing a malformed JSON payload, libprocess in Apache Mesos versions 1.4.0 to 1.5.0 might crash due to an uncaught exception. Parsing chunked HTTP requests with trailers can lead to a libprocess crash too because of the mistakenly planted assertion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.

Published by the source

14 May 2022, 01:38 UTC

Last modified by the source

30 Jan 2023, 05:00 UTC

Source last checked

26 Oct 2026, 16:02 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-95q3-pppp-r683

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

# Patch Next advisory brief: CVE-2018-1330

Advisory: Crash when decoding malformed HTTP requests or malformed JSON payload
IDs: CVE-2018-1330, GHSA-95q3-pppp-r683
Record: https://patchnext.com/advisories/cve-2018-1330 (revision 1, source checked 26 Oct 2026, 16:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.mesos:mesos 1.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.mesos:mesos: affected >= 1.4.0, < 1.6.0; fixed in 1.6.0

## Suggested inspection (read-only)
- Maven org.apache.mesos:mesos: 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.apache.mesos:mesos.
- 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-95q3-pppp-r683 (GitHub-reviewed advisory GHSA-95q3-pppp-r683 lists affected ranges: Maven org.apache.mesos:mesos >=1.4.0 <1.6.0)

Commands are suggestions: review each one before running it.