CISA list

Docker Engine versions

Docker Engine: update to 29.10.0 or 25.0.19. 28, 27, 26.1, 26.0 and 24.0 and older have reached end of life in the lifecycle data.

Data: .

Which Docker Engine branch to run

The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records we cannot place on a branch are counted at the end of the page.

Which Docker Engine branch to run
BranchStatusNewest safe releaseUpgrade to
295 CVE records that this page readsFixes, no end date announced29.10.029.10.0 (this branch)
281 CVE record that this page readsEnded on 13 May 2026None, the branch has ended29.10.0 (move to 29)
271 CVE record that this page readsEnded on 3 May 2025None, the branch has ended29.10.0 (move to 29)
26.11 CVE record that this page readsEnded on 17 February 2025None, the branch has ended29.10.0 (move to 29)
26.02 CVE records that this page readsEnded on 8 June 2024None, the branch has ended29.10.0 (move to 29)
25.05 CVE records that this page readsFixes until 4 December 202625.0.1925.0.19 (this branch)
24.02 CVE records that this page readsEnded on 8 June 2024None, the branch has ended25.0.19 (move to 25.0)
23.05 CVE records that this page readsEnded on 19 May 2025None, the branch has ended25.0.19 (move to 25.0)
20.1010 CVE records that this page readsEnded on 10 December 2023None, the branch has ended25.0.19 (move to 25.0)
19.033 CVE records that this page readsEnded on 8 January 2021None, the branch has ended25.0.19 (move to 25.0)
18.09Ended on 22 August 2019None, the branch has ended25.0.19 (move to 25.0)
18.06Ended on 8 December 2018None, the branch has ended25.0.19 (move to 25.0)
18.05Ended on 18 August 2018None, the branch has ended25.0.19 (move to 25.0)
18.04Ended on 9 June 2018None, the branch has ended25.0.19 (move to 25.0)
18.03Ended on 10 May 2018None, the branch has ended25.0.19 (move to 25.0)
18.02Ended on 21 April 2018None, the branch has ended25.0.19 (move to 25.0)
17.12Ended on 10 February 2018None, the branch has ended25.0.19 (move to 25.0)
18.01Ended on 7 March 2018None, the branch has ended25.0.19 (move to 25.0)
17.11Ended on 27 January 2018None, the branch has ended25.0.19 (move to 25.0)
17.10Ended on 20 December 2017None, the branch has ended25.0.19 (move to 25.0)
17.09Ended on 17 November 2017None, the branch has ended25.0.19 (move to 25.0)
17.07Ended on 26 October 2017None, the branch has ended25.0.19 (move to 25.0)
17.06Ended on 29 September 2017None, the branch has ended25.0.19 (move to 25.0)
17.05Ended on 28 July 2017None, the branch has ended25.0.19 (move to 25.0)
17.04Ended on 4 June 2017None, the branch has ended25.0.19 (move to 25.0)
17.03Ended on 5 May 2017None, the branch has ended25.0.19 (move to 25.0)

What this page counts

The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.

This page reads 25 CVE records that the CVE Numbering Authorities GitHub and Docker published and that name Docker Engine. The fixes are from the 20 it places on a branch. A record says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.

No release of a branch that has ended is called safe here.

Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.

Some records give a range that starts in an older release and ends in a newer branch. The lifecycle data does not list a branch for every release a range starts at, and such a release gets no row here. A record is placed on the branch of the release that ends its range, and as the record states it, the range also covers the branches the lifecycle data lists between its start and its end. Only a range that runs across branches that have all ended is placed. A range that ends in a release the lifecycle data has no branch for is not placed either. A range that reaches a branch that still gets fixes is not placed either.

A range that holds only pre-releases (alphas, betas and release candidates) is left out. A record whose fix is a release candidate says so in its row, and the release candidate is not listed as a release.

The lifecycle data does not list 25.0.19, the newest release this page gives for 25.0. A CVE record names it as a fix.

The newest record this page places on a branch was published on 7 October 2026. 2 records that this page reads were published after that day and none is placed, so no table here holds a fix from them and no release is called unsafe because of them.

5 records are not placed on a branch, so no branch or release row counts them: 2 give their versions in a form this page does not read exactly; 1 has a range with no start or no end; 2 name a release the lifecycle data has no branch for. They are CVE-2026-41568, CVE-2026-42306, CVE-2026-92543, CVE-2026-115538 and CVE-2026-115539.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • 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)