Monday 16 November
Global

Your region, kept on this device.

Git releases fixes for six security vulnerabilities, including code execution risks

Severity
High
Sources
1

has published fixes for six vulnerabilities, including arbitrary code execution during recursive clones, path traversal via a malicious server's advertised HEAD, and heap or stack memory corruption during merges, signature stripping and binary patch handling. GitHub says it has already deployed fixes across github.com and its Enterprise Cloud services, and that has patched releases. Administrators should update Git and any applications that bundle it, including automation that processes repositories for users.

For IT people · Written by AI from 1 source · Wrong?

What to do

  1. Update Git to version 2.56.1, or the patched release for your maintenance series.
  2. Update any applications that bundle their own copy of Git.
  3. GitHub Enterprise Server administrators should upgrade to 3.19.15, 3.20.11, 3.21.9 or 3.22.4 as soon as possible.
  4. If you cannot update immediately, avoid recursive clones of untrusted repositories and avoid merging untrusted content or processing untrusted binary patches or fast-import streams.

Written by AI from the sources, checked against them

Full story timeline · 1 update

  1. Tue 10 NovemberGit security vulnerabilities announcedGitHub Security Blog

Who reported · 1 outlet

GitHub Security Blog

Who and what is in it

Report a problem