CVE-2026-55576 MaaAssistantArknights CVE debrief

Who should care

Users of MaaAssistantArknights, especially those using the dev-v2 workflow, should be aware of this vulnerability and take immediate action to mitigate the risk. This includes reviewing and updating the .github/workflows/release-preparation.yml file to prevent similar vulnerabilities in the future and monitoring for any suspicious activity related to the generate-changelog job.

Technical summary

The vulnerability is caused by the inlining of attacker-controlled github.event.pull_request.title into a run: shell command during specific events in the .github/workflows/release-preparation.yml file. This allows a non-draft fork PR whose title starts with 'Release v' to execute shell commands on the ubuntu-latest runner during the generate-changelog job. The vulnerability exists in MaaAssistantArknights, a one-click tool for daily Arknights tasks, specifically in the dev-v2 workflow.

Defensive priority

High priority should be given to patching this vulnerability, as it has a CVSS score of 8.8 and is classified as HIGH severity.

Recommended defensive actions

• Patch the vulnerability by applying the fix provided in commit cafc3946059e6337d2089d4fec8b6885ba17c332.
• Review and update the .github/workflows/release-preparation.yml file to prevent similar vulnerabilities in the future.
• Monitor for any suspicious activity related to the generate-changelog job.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The vulnerability was reported by an unknown source and is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332. The CVE record was published on 2026-07-15T22:17:26.157Z and last modified on 2026-07-16T13:52:58.290Z. Evidence of the vulnerability's existence and impact is limited, and defenders should verify the affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.