Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Microsoft GitHub Repository Windows-driver-samples Workflow Remote Code Execution

Critical

Synopsis

The GitHub public repository at https://github.com/microsoft/Windows-driver-samples has a GitHub Action configured which allows for Remote Code Execution on the GitHub runner: https://github.com/microsoft/Windows-driver-samples/blob/main/.github/workflows/tag-codeowner-on-issue.yml


The vulnerability lies in this part of the GitHub workflow:

        run: |
          python3 - <<EOF
          import os
          import re
          import requests

          issue_body = """${{ github.event.issue.body }}"""
          selected_path = None

The issue body is directly interpolated into a Python here-doc without sanitization. An attacker can then inject arbitrary Python code by crafting a malicious issue body containing string terminators (triple quotes) to break out of the string literal and inject code.

By exploiting this vulnerability, an attacker with an unprivileged GItHub account could exfiltrate secrets available to the workflow run and perform unauthorized operations on the target GitHub repository.

 

 

Solution

Microsoft patched the vulnerable workflow with this following pull request: https://github.com/microsoft/Windows-driver-samples/pull/1355.

Disclosure Timeline

February 24, 2026: Tenable reports the finding to Microsoft.
February 24, 2026: Microsoft confirms case creation for this report.
March 9, 2026: Tenable requests an update on the case status.
March 13, 2026: Microsoft provides an update and confirms the behavior described in the original report.
March 26, 2026: Tenable asks Microsoft if the issue has been fixed as a PR has been issued on the repository.
March 30, 2026: Microsoft confirms the issue has been fixed.

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]