Trino 300 lifecycle

Current status

end of lifehigh

Trino 300 reached end of life on 3 May 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: 3 May 2019
Latest release: 309
Released: 25 Apr 2019

At a glance

Version line: 300
Initial release: 22 Jan 2019
Lifecycle phase: end of life
Latest stable: 309
Latest release date: 25 Apr 2019
EOL: 3 May 2019
Risk: high
Releases tracked: 10

Lifecycle timeline

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

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

Trino 300 reached end of life on 3 May 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 300

End of lifeEOL 3 May 2019

Supported upgrade options

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

Open full upgrade planner for Trino 300 →

Security

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

309

Released 25 Apr 2019 · stable

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

Previous releases

308
12 Apr 2019
307
4 Apr 2019
306
17 Mar 2019

Release history

10 concrete releases tracked for this line.

Version	Release date	Channel	Source
309	25 Apr 2019	stable	Source
308	12 Apr 2019	stable	Source
307	4 Apr 2019	stable	Source
306	17 Mar 2019	stable	Source
305	8 Mar 2019	stable	Source
304	27 Feb 2019	stable	Source
303	14 Feb 2019	stable	Source
302	7 Feb 2019	stable	Source
301	31 Jan 2019	stable	Source
300	22 Jan 2019	stable	Source

Release activity

Total releases: 10
Last 30 days: 0
Last 90 days: 0
Avg. interval: ~10 days
Most recent: 25 Apr 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.

	300	480
Status	end of life	standard support
Latest release	309	483
EOL	May 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