Discover · github.blog

No picture published by github.blog

Git security vulnerabilities announced

Git.io github.blog

Editor’s note (November 17, 2026): This post has been updated with additional CVE information and updated guidance for GitHub Enterprise Server users. Please see the release information below for the versions that include the fixes.

Today, the Git project is releasing new versions to address six security vulnerabilities. These include arbitrary code execution when cloning a malicious repository, writes to unintended files, and memory corruption when processing merges or binary patches.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Security — person

In the piece

Named in it

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from Git.io

  1. Maintainers don’t need more AI bug reports. They need fixes. Ashley Wolf github.blog
  2. Building the Agent Host Protocol for sessions that continue across devicesConnor Peet github.blog
  3. GitHub availability report: October 2026Jakub Oleksy github.blog
  4. Build once, run on any agent: A practical guide to agent skillsAndrea Griffiths github.blog
  5. Beyond code generation: A developer’s guide to agentic engineeringNick Liffen github.blog
  6. Inside GitHub’s new Git storage architectureKarthik Raman github.blog