potiuk opened a new issue, #760:
URL: https://github.com/apache/incubator-kie-kogito-docs/issues/760

   Heads-up from ASF Infra. `actions-cool/maintain-one-comment@v3` is used in 
`.github/workflows/pr-preview-publish.yml` (two steps) and 
`.github/workflows/pr-preview-teardown.yml`.
   
   **What happened.** On 2026-05-18 the same attacker who hit 
`actions-cool/issues-helper` repointed every tag of 
`actions-cool/maintain-one-comment` to an imposter commit that reads runner 
memory for CI/CD secrets and exfiltrates them ([StepSecurity 
advisory](https://www.stepsecurity.io/blog/actions-cool-issues-helper-github-action-compromised-all-tags-point-to-imposter-commit-that-exfiltrates-ci-cd-credentials)).
 GitHub TOS-blocked the repo on 2026-05-19, so `@v3` no longer resolves -- 
these steps now fail to fetch the action.
   
   **Good news -- no exposure here.** I checked the run history for both 
workflows: **no runs** during the ~5-hour malicious window (2026-05-18 19:10 -> 
2026-05-19 00:33 UTC). The nearest run (pr-preview-publish, 2026-05-15) was 
three days *before* the compromise, using the legitimate action. So no secrets 
were exposed and no rotation is needed on that evidence.
   
   **Action needed.** Remove or replace these steps. The canonical maintained 
replacement is `peter-evans/create-or-update-comment` (would need adding to the 
ASF allow list), or `actions/github-script` which is in the always-allowed 
`actions/*` namespace and needs no allow-list change. Happy to send a PR. The 
action was removed from the ASF org-wide allow list in 
apache/infrastructure-actions#1035.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to