Trino 320 lifecycle

Current status

end of lifehigh

Trino 320 reached end of life on 19 Feb 2020. 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: 19 Feb 2020
Latest release: 329
Released: 23 Jan 2020

At a glance

Version line: 320
Initial release: 6 Oct 2019
Lifecycle phase: end of life
Latest stable: 329
Latest release date: 23 Jan 2020
EOL: 19 Feb 2020
Risk: high
Releases tracked: 10

Lifecycle timeline

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

Release
6 Oct 2019
standard support
6 Oct 2019 → 19 Feb 2020
Source: Trino GitHub Releases
end of lifecurrent
19 Feb 2020 → —
Source: Trino GitHub Releases

Trino 320 reached end of life on 19 Feb 2020. 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 320

End of lifeEOL 19 February 2020

Supported upgrade options

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

Open full upgrade planner for Trino 320 →

Security

Advisories affecting Trino 320 (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

329

Released 23 Jan 2020 · stable

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

Previous releases

328
11 Jan 2020
327
20 Dec 2019
326
27 Nov 2019

Release history

10 concrete releases tracked for this line.

Version	Release date	Channel	Source
329	23 Jan 2020	stable	Source
328	11 Jan 2020	stable	Source
327	20 Dec 2019	stable	Source
326	27 Nov 2019	stable	Source
325	13 Nov 2019	stable	Source
324	2 Nov 2019	stable	Source
323	24 Oct 2019	stable	Source
322	17 Oct 2019	stable	Source
321	15 Oct 2019	stable	Source
320	6 Oct 2019	stable	Source

Release activity

Total releases: 10
Last 30 days: 0
Last 90 days: 0
Avg. interval: ~12 days
Most recent: 23 Jan 2020

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.

	320	480
Status	end of life	standard support
Latest release	329	483
EOL	Feb 2020	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