CVE-2026-55576

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

August 12, 2026

Advisory Details (2)

Auto-updated Jul 15, 2026
No fix on record yet. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

MaaAssistantArknights :- PR-title expression injection in release-preparation.yml · Advisory · MaaAssistantArknights/MaaAssistantArknights · GitHub

https://github.com/MaaAssistantArknights/MaaAssistantArknights/security/advisories/GHSA-pqx2-5g66-f5w8
GitHub commit

commit cafc3946059e (MaaAssistantArknights/MaaAssistantArknights)

Fix landed in MaaAssistantArknights/MaaAssistantArknights commit cafc3946059e — awaiting tagged release

https://github.com/MaaAssistantArknights/MaaAssistantArknights/commit/cafc3946059e6337d2089d4fec8b6885ba17c332

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 131 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:17 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-01 12:36 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-09-28 08:41 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 75 more
  1. 2026-09-24 08:45 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-09-23 03:14 UTCEG score recompute
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-09-18 04:43 UTCEG score recompute
  7. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-09-13 23:11 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-09-13 07:12 UTCEG score recompute
  14. 2026-09-11 21:44 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-09-08 00:41 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-05 20:46 UTCEG score recompute
  22. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-08-31 03:58 UTCEG score recompute
  27. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-08-30 03:44 UTCEG score recompute
  29. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  30. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-08-28 01:51 UTCEG score recompute
  32. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-08-26 23:53 UTCEG score recompute
  34. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  35. 2026-08-26 00:02 UTCEG score recompute
  36. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  37. 2026-08-25 00:10 UTCEG score recompute
  38. 2026-08-24 12:17 UTCEG score recompute
  39. 2026-08-23 12:12 UTCEG score recompute
  40. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  41. 2026-08-22 00:00 UTCEG score recompute
  42. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-08-21 00:10 UTCEG score recompute
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  45. 2026-08-20 00:13 UTCEG score recompute
  46. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-08-18 21:53 UTCEG score recompute
  48. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  49. 2026-08-17 21:20 UTCEG score recompute
  50. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-16 19:16 UTCEG score recompute
  52. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-08-16 07:08 UTCEG score recompute
  54. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-08-15 07:23 UTCEG score recompute
  56. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  57. 2026-08-14 07:11 UTCEG score recompute
  58. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  59. 2026-08-12 19:19 UTCEG score recompute
  60. 2026-08-12 18:56 UTCEG score recompute
  61. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  62. 2026-08-12 01:33 UTCEG score recompute
  63. 2026-08-11 01:47 UTCEG score recompute
  64. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  65. 2026-08-09 14:07 UTCEG score recompute
  66. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  67. 2026-08-08 02:28 UTCEG score recompute
  68. 2026-08-06 14:49 UTCEG score recompute
  69. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  70. 2026-08-06 02:55 UTCEG score recompute
  71. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  72. 2026-08-05 00:54 UTCEG score recompute
  73. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  74. 2026-08-04 13:01 UTCEG score recompute
  75. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55576?
CVE-2026-55576 is a high-severity vulnerability; its CVE record was published on July 15, 2026. 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.pullrequest.title into a run: shell command during the pullrequest opened, reopened, and readyforreview events, so…
When was the CVE record for CVE-2026-55576 published?
The CVE record for CVE-2026-55576 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 12, 2026; the record at its source may have been updated since.
Is CVE-2026-55576 actively exploited?
CVE-2026-55576 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55576?
CVE-2026-55576 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55576?
No fix for CVE-2026-55576 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-55576

Explore →

Is Your Infrastructure Affected by CVE-2026-55576?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs