Privilege escalation in Presto

Exploitation

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

CVSS

7.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS

• CVE-2020-15087: 1.06% estimated exploitation activity in the next 30 days; percentile 64.52 (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.

Affected This affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver. Impact Authenticated users can bypass authorization checks by directly accessing internal APIs. This impacts Presto server installations with secure internal communication configured. This does not affect installations that have not configured secure internal communication, as these installations are inherently insecure. Patches This issue has been fixed starting with PrestoSQL version 337. Workarounds This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers. References See the Presto documentation for Secure Internal Communication. For more information If you have any questions or comments about this advisory: Join the #security channel on Slack. Contact the security team at security@trino.io

Published by the source

30 Jun 2020, 16:33 UTC

Last modified by the source

2 Feb 2023, 05:04 UTC

Source last checked

26 Oct 2026, 16:07 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f6pc-crhh-cp96

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

# Patch Next advisory brief: CVE-2020-15087

Advisory: Privilege escalation in Presto
IDs: CVE-2020-15087, GHSA-f6pc-crhh-cp96
Record: https://patchnext.com/advisories/cve-2020-15087 (revision 1, source checked 26 Oct 2026, 16:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.prestosql:presto-server 337. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.prestosql:presto-server: affected < 337; fixed in 337

## Suggested inspection (read-only)
- Maven io.prestosql:presto-server: 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 io.prestosql:presto-server.
- 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-f6pc-crhh-cp96 (GitHub-reviewed advisory GHSA-f6pc-crhh-cp96 lists affected ranges: Maven io.prestosql:presto-server >=0 <337)

Commands are suggestions: review each one before running it.