CISA list

● Branch of Go

Go 1.18

Go 1.18 reached end of life on 1 February 2023 and gets no fixes. Move to 1.26.11 or newer.

Data: .

Fix releases of Go 1.18

Releases that end an affected range of a CVE record, newest first. A release gets a page when it fixes three or more records, or one that CISA lists or that EPSS rates 0.50 or more. Records this page cannot place on a branch, named on the page of the platform, are not in it.
ReleaseFixesSigns of exploitation
1.18.92 CVE recordsnone
1.18.81 CVE recordnone
1.18.73 CVE recordsnone
1.18.61 CVE recordnone
1.18.51 CVE recordnone
1.18.49 CVE recordsnone
1.18.34 CVE recordsnone
1.18.21 CVE recordnone
1.18.13 CVE recordsnone

Go 1.18 in dates

WhatWhen
Released15 March 2022
Security fixes end1 February 2023
Newest release1.18.10 (10 January 2023)

What this page says

Since 1 February 2023, the Go vulnerability database has published advisories that name 149 CVE ids. 5 of them are not placed on a branch. Of the others, none gives a range of its own for Go 1.18, and 133 give a range with no start that ends in a newer branch; as the advisory states it, that range covers Go 1.18 too.

A record names the branches the project tested, and a branch that has ended is rarely among them. That does not make Go 1.18 safe. Not tested by the project, treat as affected.

A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.

Sources
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)
  • Package advisories from the Go vulnerability database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0