)]}'
{
  "commit": "27aa1c5222c3a528dd14b68bef3cf3bf7a469ee8",
  "tree": "e8e7ecbde2b0885e9fe3730116744a4b71d8cf5d",
  "parents": [
    "fa16f8102e67f9246bb2b456baed3a0e8f0181f5",
    "b4e013bbec9f42687345f152a685cd3518080289"
  ],
  "author": {
    "name": "Jonathan Brouwer",
    "email": "jonathantbrouwer@gmail.com",
    "time": "Sun Apr 26 19:06:28 2026 +0200"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Sun Apr 26 19:06:28 2026 +0200"
  },
  "message": "Rollup merge of #155707 - Manishearth:cstring-vuln, r\u003dMark-Simulacrum\n\nFix minor panic-unsoundness in CString::clone_into\n\n`CString` must always contain a null byte, calling `mem::take` on its inner allocation puts it in an invalid state (causing UB if e.g. it hits `CString::drop`) that can be observed if the allocator panics.\n\nUnfortunately, this solution allocates an intermediate 1-element `Box`. I\u0027m not sure of a clean way to avoid that additional allocation; we could directly `realloc` if we want but it\u0027s tricky. Might be something we can do with `ManuallyDrop`.\n\nI do have a gnarly miri test for this that uses a panicky allocator, but I\u0027m not sure where it would go. Happy to push it up if someone has a suggestion.\n\nBug discovered by Rust Foundation Security using AI. I\u0027m just helping with the patch as a member of wg-security-response. We do not believe this bug needs embargo, it is a soundness fix for hard-to-trigger unsoundness.\n",
  "tree_diff": []
}