GHSA-p2xq-vcm7-xjj6 — mesos
HIGHGHSA-p2xq-vcm7-xjj6 is a high-severity (CVSS 7.5) Buffer Overflow vulnerability in org.apache.mesos:mesos. A fix is available for org.apache.mesos:mesos — see the affected versions and patch details below.
Stack Overflow in Apache Mesos
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-p2xq-vcm7-xjj6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.apache.mesos:mesos☕org.apache.mesos:mesos☕org.apache.mesos:mesos☕org.apache.mesos:mesosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
When parsing a JSON payload with deeply nested JSON structures, the parser in Apache Mesos versions pre-1.4.x, 1.4.0 to 1.4.2, 1.5.0 to 1.5.1, 1.6.0 to 1.6.1, and 1.7.0 might overflow the stack due to unbounded recursion. A malicious actor can therefore cause a denial of service of Mesos masters rendering the Mesos-controlled cluster inoperable.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.mesos:mesos | all versions | 1.4.3org.apache.mesos:mesos:1.4.3 |
| ☕Maven | org.apache.mesos:mesos | ≥ 1.5.0&&< 1.5.2 | 1.5.2org.apache.mesos:mesos:1.5.2 |
| ☕Maven | org.apache.mesos:mesos | ≥ 1.6.0&&< 1.6.2 | 1.6.2org.apache.mesos:mesos:1.6.2 |
| ☕Maven | org.apache.mesos:mesos | ≥ 1.7.0&&< 1.7.1 | 1.7.1org.apache.mesos:mesos:1.7.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.mesos:mesos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.mesos:mesos to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2xq-vcm7-xjj6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p2xq-vcm7-xjj6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p2xq-vcm7-xjj6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p2xq-vcm7-xjj6 in your dependencies?
O3 Security finds GHSA-p2xq-vcm7-xjj6 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.