We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filing a public issue instead of reporting this as a private vulnerability, since this malware is a publicly known and an urgent issue.
sage uses a compromised version of tj-actions/changed-files. The compromised action appears to leak secrets the runner has in memory.
The action is included in:
Output of an affected runs:
Please review.
Learn about the compromise on StepSecurity of Semgrep.
The text was updated successfully, but these errors were encountered:
@kwankyu @tobiasdiez : I think we need to react quickly to this.
Sorry, something went wrong.
See #39722 (comment)
No branches or pull requests
Filing a public issue instead of reporting this as a private vulnerability, since this malware is a publicly known and an urgent issue.
sage uses a compromised version of tj-actions/changed-files. The compromised action appears to leak secrets the runner has in memory.
The action is included in:
Output of an affected runs:
Please review.
Learn about the compromise on StepSecurity of Semgrep.
The text was updated successfully, but these errors were encountered: