Fix workflow input injection vulnerability in test steps#522
Merged
riggi-alekaj merged 1 commit intodevfrom Mar 13, 2026
Merged
Fix workflow input injection vulnerability in test steps#522riggi-alekaj merged 1 commit intodevfrom
riggi-alekaj merged 1 commit intodevfrom
Conversation
bfeshti
previously approved these changes
Mar 11, 2026
riggi-alekaj
dismissed
bfeshti’s stale review
The merge-base changed after approval.
riggi-alekaj
force-pushed
the
patch-injection-vuln
branch
7 times, most recently
from
d48b197 to
f91be89
Compare
riggi-alekaj
force-pushed
the
patch-injection-vuln
branch
from
f91be89 to
50a9bf0
Compare
bfeshti
approved these changes
Mar 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses a high-severity Semgrep finding: workflow inputs (
inputs.RELEASE,inputs.DOCKER_IMAGE_VERSION) were interpolated directly intorun:steps, which could allow code injection and secret exfiltration.inputs.RELEASEandinputs.DOCKER_IMAGE_VERSIONviaenv:blocks instead of inline in the script"$ISRELEASE_INPUT") so values are treated as data, not executable code