Skip to content

Fix code injection vulnerability in release workflow#119

Draft
Copilot wants to merge 2 commits intoalert-autofix-19from
copilot/sub-pr-117-again
Draft

Fix code injection vulnerability in release workflow#119
Copilot wants to merge 2 commits intoalert-autofix-19from
copilot/sub-pr-117-again

Conversation

Copy link
Contributor

Copilot AI commented Feb 28, 2026

Addresses remaining code injection vulnerability in .github/workflows/release-with-sbom.yml where a GitHub expression was embedded directly in a shell script.

Changes

  • Moved ${{ steps.create_release.outputs.url }} to environment variable RELEASE_URL
  • Updated echo command to reference $RELEASE_URL instead of inline GitHub expression
- name: Release complete
  env:
    RELEASE_VERSION: ${{ steps.version.outputs.version }}
    RELEASE_URL: ${{ steps.create_release.outputs.url }}
  run: |
    echo "✅ Release process complete"
    echo "Version: v$RELEASE_VERSION"
    echo "Release URL: $RELEASE_URL"

This follows the same pattern as RELEASE_VERSION and eliminates the code injection attack surface by isolating GitHub expressions from shell execution context.


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

… variable

Co-authored-by: anoncam <46797044+anoncam@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix code scanning alert for code injection issues Fix code injection vulnerability in release workflow Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants