<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/127650>127650</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            SecurityGroup archive: Chromium issue 42410026 LLVM security incident - July 12
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            SecurityArchive
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          smithp35
      </td>
    </tr>
</table>

<pre>
    This is an archival issue from the Security Group's Chromium bug-tracker which has now been archived. Capturing the contents of the Chromium issue in a PDF in case link.

This is https://issuetracker.google.com/u/1/issues/42410026 LLVM security incident - July 12
Published in https://llvm.org/docs/SecurityTransparencyReports.html#id2

[LLVM security incident - July 12 \[42410026\] - Issue Tracker.pdf](https://github.com/user-attachments/files/18847337/LLVM.security.incident.-.July.12.42410026.-.Issue.Tracker.pdf)
</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJyMkkFvnD4QxT-NuVhYZmwWOHDYZMVf_yqVojbq3RiD3RiMbJNov30FWbdJD21PMJLnzW_ePBGCmRalWlTeofKSiS1q59swm6hXVma9G67tkzYBm4DFgoWX2rwIi00Im8KjdzOOWuGvSm7exCv-z7ttRVAFfK-9m802436b8uiFfFYev2ojNdYi4MW94l6pJKkGgu_FGjdvlumQlG6JaokBu_Gof-q9jTYLFvjx0u0_UgSFrVmeCaJnRM8JWMe4BsTOCDoE3dF3AyGTc5NVRLoZQbch6Ir0IiDoOPCCUjjhh4dvn3FIy5lFmkEtEef402avuABEz49bb03QathJPk609mUmzk8IusHJXTj59OTFElbh1SKvX9TqfAxEx9kiYGaAty1Qefe38RiV96i8S7hHdcE5_v-w6Om26zqMqLwgqD_STSbqrU8WBOVzEaOQet5dR9CNxh5mFHXNK8YqBN3OQxIPSTwkJzsPKYAkEpKTg4G8Z4AmG1o2NKwRmWqLijV1U7ATz3RbVvSkeMEqTmVVCc4ZrQYKp4KPI61HnpkWKJQUirooaVM0hAnOGoCay6bpq5NEnKpZGEuS6dlxzbaA6lTSzIpe2XDEHCBd4fwWPQSwZ9-3e2veb1NAnFoTYvglFk20qk2NR8pTchE7_x7Of85Ptnnb_uEs-_zbJ1-9-65kfJ_T23IvLfwIAAD__0L1OiM">