{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihp7lodk77gvb5py6oy4j3a4yfskryawqtgl2shc6dmfczr4yepku",
    "uri": "at://did:plc:2ikdxjcpbsuoe6mv3qawmazg/app.bsky.feed.post/3mknee5m3vnt2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreidv2l37jbs6mtcku4ihymsuoprtecekflyh54acqnzeoib54vd4zm"
    },
    "mimeType": "image/png",
    "size": 1360667
  },
  "path": "/security/securing-the-git-push-pipeline-responding-to-a-critical-remote-code-execution-vulnerability/",
  "publishedAt": "2026-04-28T15:30:00.000Z",
  "site": "https://github.blog",
  "tags": [
    "Security",
    "CVE",
    "GHES",
    "Securing the git push pipeline: Responding to a critical remote code execution vulnerability",
    "The GitHub Blog"
  ],
  "textContent": "How we validated, fixed, and investigated a critical vulnerability in under two hours, and confirmed no exploitation.\n\nThe post Securing the git push pipeline: Responding to a critical remote code execution vulnerability appeared first on The GitHub Blog.",
  "title": "Securing the git push pipeline: Responding to a critical remote code execution vulnerability"
}