CVE-2026-31976
Supply chain via tag poisoning in xygeni-action; CI runner RCE.
Is CVE-2026-31976 being exploited?
Not confirmed. CVE-2026-31976 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.
How severe is CVE-2026-31976?
CVE-2026-31976 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-31976?
Yes. A fix has been recorded for CVE-2026-31976. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-31976 affect?
CVE-2026-31976 affects xygeni-action GitHub Action, GitHub Actions workflows, Xygeni Scanner. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-31976?
Pin to trusted commit; rotate credentials; audit workflows referencing xygeni-action@v5.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote command execution on CI runners via poisoned action tag v5 during the affected window.
Immediate action required