Security readout for executives and security teams
Plain-English summary
This flaw let an outside contributor trigger shell command execution in a GitHub Actions release-preparation workflow by opening a specially titled pull request. The risk is mainly CI/CD compromise for the MaaAssistantArknights repository, not direct compromise of deployed user systems.
Executive priority
Treat as high priority for affected maintainers because it impacts CI/CD integrity and could let untrusted contributors run commands in automation. Prioritize patching before accepting external release-themed pull requests.
Technical view
The vulnerable workflow inlined github.event.pull_request.title into a run shell command during pull_request opened, reopened, and ready_for_review events. A non-draft fork PR whose title began with Release v could execute commands on the ubuntu-latest runner in generate-changelog. Fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
Likely exposure
Exposure is limited to MaaAssistantArknights repositories or forks using the vulnerable dev-v2 release-preparation.yml before the fixed commit. Organizations not running this workflow pattern are not indicated as affected by the sources.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. Exploitation required opening or reopening a qualifying non-draft fork pull request with a matching title pattern against the affected workflow.
Researcher notes
The key boundary failure is untrusted PR metadata crossing into shell execution. Evidence supports CWE-78 and CWE-94. The bundle identifies the trigger conditions and fixed commit, but does not provide confirmed exploitation, exposed secrets, or downstream package compromise.
Mitigation direction
- Apply commit cafc3946059e6337d2089d4fec8b6885ba17c332 or a vendor release containing it.
- Check the GitHub security advisory for any updated vendor guidance.
- Remove direct shell interpolation of pull request titles in workflows.
- Review forks or long-lived branches for copied vulnerable workflow logic.
Validation and detection
- Confirm the repository includes commit cafc3946059e6337d2089d4fec8b6885ba17c332 or equivalent workflow changes.
- Inspect release-preparation.yml for pull request title use inside run shell commands.
- Review recent GitHub Actions runs from fork pull requests with titles beginning Release v.
- Check whether generate-changelog ran on opened, reopened, or ready_for_review pull_request events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-55576 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/MaaAssistantArknights/MaaAssistantArknights/security/advisories/GHSA-pqx2-5g66-f5w8CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/MaaAssistantArknights/MaaAssistantArknights/commit/cafc3946059e6337d2089d4fec8b6885ba17c332CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.