# Denial of service in Apache Mesos

Advisory record · `GHSA-x869-784m-jmj2`

- **Identifiers:** `GHSA-x869-784m-jmj2` · `CVE-2017-7687`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Published:** 13 May 2022
- **Updated:** 28 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.mesos:mesos` (Maven): affected `<1.1.3 || >=1.2.0, <1.2.2 || >=1.3.0, <1.3.1`; fixed in `1.1.3`, `1.2.2`, `1.3.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Mesos (org.apache.mesos:mesos) versions before 1.1.3, from 1.2.0 before 1.2.2, and from 1.3.0 before 1.3.1 are affected. A remote attacker who sends an HTTP request with a malformed URL path can crash libprocess, causing a denial of service on Mesos masters and making the cluster inoperable. Upgrade to version 1.1.3, 1.2.2, or 1.3.1, depending on the release line in use.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.024, the 84th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x869-784m-jmj2)

## Sources

- [GitHub Advisory Database: GHSA-x869-784m-jmj2](https://github.com/advisories/GHSA-x869-784m-jmj2)
- [OSV: GHSA-x869-784m-jmj2](https://osv.dev/vulnerability/GHSA-x869-784m-jmj2)
- <https://nvd.nist.gov/vuln/detail/CVE-2017-7687>
- <https://lists.apache.org/thread.html/2c9ed2b07c2b2831a11d21db3cf8408a71fcf2c300d73ca01bad89df@%3Cdev.mesos.apache.org%3E>
- <http://www.securityfocus.com/bid/101027>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x869-784m-jmj2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x869-784m-jmj2/>. Everything for agents: <https://agentprime.io/llms.txt>.
