Trino 310 lifecycle

Current status

end of lifehigh

Trino 310 reached end of life on 6 Oct 2019. Security and bug fixes are no longer provided by the project according to published lifecycle data.

This line is end of life.

Plan your upgrade →

Security: 1 tracked advisories affecting this line. Details below — lifecycle and vulnerability status are separate.

Official lifecycle source: Trino GitHub Releases

Support phase: end of life
End of life: 6 Oct 2019
Latest release: 319
Released: 22 Sept 2019

At a glance

Version line: 310
Initial release: 3 May 2019
Lifecycle phase: end of life
Latest stable: 319
Latest release date: 22 Sept 2019
EOL: 6 Oct 2019
Risk: high
Releases tracked: 10

Lifecycle timeline

Phases from published LifecyclePeriod records. Missing phases are not inferred.

Release
3 May 2019
standard support
3 May 2019 → 6 Oct 2019
Source: Trino GitHub Releases
end of lifecurrent
6 Oct 2019 → —
Source: Trino GitHub Releases

Trino 310 reached end of life on 6 Oct 2019. Security and bug fixes are no longer provided by the project according to published lifecycle data.

Upgrade options

Newer supported Trino version lines from CompatHub lifecycle data. Compatibility and security context use existing evidence only.

You are on Trino 310

End of lifeEOL 6 October 2019

Supported upgrade options

Trino 480
Supported· 170 major versions newer
Upgrade planner →
Trino 470
Supported· 160 major versions newer
Upgrade planner →
Trino 460
Supported· 150 major versions newer
Upgrade planner →

Open full upgrade planner for Trino 310 →

Security

Advisories affecting Trino 310 (OSV.dev evidence). Known exploited status, due dates, and ransomware use from CISA KEV when matched.

Known vulnerabilities: 1
Known exploited: 0
Highest CVSS: —

CVE-2020-15087
Affected:
<337
Fixed in:
337
Source:
OSV source · Advisory

Latest release

319

Released 22 Sept 2019 · stable

https://github.com/trinodb/trino/releases/tag/319

Previous releases

318
26 Aug 2019
317
2 Aug 2019
316
9 Jul 2019

Release history

10 concrete releases tracked for this line.

Version	Release date	Channel	Source
319	22 Sept 2019	stable	Source
318	26 Aug 2019	stable	Source
317	2 Aug 2019	stable	Source
316	9 Jul 2019	stable	Source
315	15 Jun 2019	stable	Source
314	8 Jun 2019	stable	Source
313	1 Jun 2019	stable	Source
312	29 May 2019	stable	Source
311	15 May 2019	stable	Source
310	3 May 2019	stable	Source

Release activity

Total releases: 10
Last 30 days: 0
Last 90 days: 0
Avg. interval: ~16 days
Most recent: 22 Sept 2019

Should I use this version?

Not recommended for new deployments

Upgrade to a currently supported release line. Recommended target: Trino 480.

Version comparison

Compact comparison against the nearest relevant release lines.

	310	480
Status	end of life	standard support
Latest release	319	483
EOL	Oct 2019	Not published
Risk	high	low

Sources

Where this information comes from.

Lifecycle sources

Trino GitHub Releasesfirst party · high confidence
Official source: https://github.com/trinodb/trino/tags
Last verified 2 Sept 2026
OSV.devfirst party
Official source: https://osv.dev
Verification time not recorded
NVD (NIST)first party
Official source: https://nvd.nist.gov
Verification time not recorded
CISA Known Exploited Vulnerabilitiesfirst party
Official source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Verification time not recorded
Trino Java Requirementsfirst party
Official source: https://raw.githubusercontent.com/trinodb/trino/master/pom.xml
Verification time not recorded

Release sources

Trino GitHub Releasesfirst party · high confidence
Official source: https://github.com/trinodb/trino/tags
Last verified 2 Sept 2026

Data coverage

Last checked = last successful upstream check. Latest source update = when upstream content last changed.

Releases tracked: 10
Lifecycle periods: 2
EOL: Known
Provenance records: 3
Data last checked: 2 Sept 2026
Latest source update: 2 Sept 2026