Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this new
pull_requesttrigger runs, thesetup-gradlestep has nocache-read-onlyinput, so its default writable cross-run cache lets untrusted PR builds save Gradle state. This bypasses the mitigation added in parent commit22d09f2for the repository's vulnerable Kotlin plugin: malicious cache metadata can be restored and executed by a later CodeQL run for the same PR, even after the original payload is removed. Configure this workflow's Gradle setup as read-only for PRs and include it in the cache-policy regression test.AGENTS.md reference: AGENTS.md:L24-L26
Useful? React with 👍 / 👎.