CVE intelligence and bounded remediation
CVE-2026-31976 — xygeni-action is the GitHub Action for Xygeni Scanner
xygeni-action is the GitHub Action for Xygeni Scanner. On March 3, 2026, an attacker with access to compromised credentials created a series of pull requests (#46, #47, #48) injecting obfuscated shell code into action.yml. The PRs were blocked by branch protection rules and never merged into the main branch. However, the attacker used the compromised GitHub App credentials to move the mutable v5 tag to point at the malicious commit (4bf1d4e19ad81a3e8d4063755ae0f482dd3baf12) from one of the unmerged PRs. This commit remained in the repository's git object store, and any workflow referencing @v5 would fetch and execute it. This is a supply chain compromise via tag poisoning. Any GitHub Actions workflow referencing xygeni/xygeni-action@v5 during the affected window (approximately March 3–10, 2026) executed a C2 implant that granted the attacker arbitrary command execution on the CI runner for up to 180 seconds per workflow run.
- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Published
- 2026-03-11
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-506
Affected products
- xygeni / xygeni-action
Matched remediation archetype
Supply-chain, dependency, build, and update integrity
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
- Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
- Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.
Remediate safely
- Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
- Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
- Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.