CVE-2026-31976: Xygeni/xygeni action Xygeni-action V5 Tag Poisoned With Vulnerability

CRITICAL
Advisory Identifier: GHSA-f8q5-h5qh-33mh
CWE-506
Published
Advisory Summary

CVE-2026-31976 is a CRITICAL xygeni-action v5 tag poisoned with vulnerability (CWE-506: Embedded Malicious Code) affecting Xygeni/xygeni action libraries in the GitHub Actions ecosystem. The issue involves xygeni-action v5 tag poisoned with c2 backdoor. Remediation is available by upgrading affected packages to version 6.4.0.

CVE-2026-31976 at a Glance

CVE Identifier CVE-2026-31976
GHSA Identifier GHSA-f8q5-h5qh-33mh
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-506: Embedded Malicious Code
Affected Product Xygeni/xygeni action
Package Ecosystem GitHub Actions
Published Date
Last Updated

How to Fix CVE-2026-31976

To remediate this vulnerability, upgrade all affected Xygeni/xygeni action dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

xygeni/xygeni-action fixed: 6.4.0
Upgrade xygeni/xygeni-action to 6.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for xygeni/xygeni-action

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-31976, inspect your project dependencies for Xygeni/xygeni action:

inspect dependencies for xygeni/xygeni-action

Analyze the terminal output to locate any version of Xygeni/xygeni action in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In Xygeni/xygeni action, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Description 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. The malicious code, disguised as a "scanner version telemetry" step, operates as follows: 1. Registers the CI runner with a C2 server at `91.214.78.178` (via `security-verify.91.214.78.178.nip.io`), transmitting hostname, username, and OS version. 2. Polls the C2 server every 2–7 seconds for 180 seconds, receiving and executing arbitrary shell commands via `eval`. 3. Compresses and base64-encodes command output before exfiltrating it back to the C2 server. The implant runs silently in the background alongside the legitimate scan, suppresses all errors, skips TLS certificate verification, and uses randomized polling intervals to evade detection. ### Impact 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. The severity is set to Critical based on the potential impact. However, several factors reduce the realized risk: the `v5` tag was primarily referenced by Xygeni-owned and Xygeni-affiliated repositories; no external public repositories were found using the compromised tag (though usage in private repositories cannot be ruled out); the exposure window was approximately 6 days; and no confirmed exploitation of downstream users has been established to date. ### Patches The compromised `v5` tag has been removed from the repository. Users should update their workflows to pin to the verified safe commit SHA corresponding to v6.4.0: ```yaml uses: xygeni/xygeni-action@13c6ed2797df7d85749864e2cbcf09c893f43b23 # v6.4.0 ``` Workflows still referencing `@v5` will fail with a reference not found error, as the tag no longer exists. If your workflows ran with `@v5` during the affected window, you should also: - Rotate all secrets that were available to the CI runner (repository secrets, environment secrets, deploy keys, cloud provider tokens). - Audit CI logs for outbound connections to `91.214.78.178` or DNS lookups for `security-verify.91.214.78.178.nip.io`. - Review recent releases and published artifacts for signs of tampering. ### Workarounds As an alternative to using the GitHub Action, you may install and run the Xygeni scanner directly via the CLI installation method documented at https://docs.xygeni.io/xygeni-scanner-cli/xygeni-cli-overview/xygeni-cli-installation. This bypasses the GitHub Action entirely and is not affected by this incident. ### References - GitHub issue: https://github.com/xygeni/xygeni-action/issues/54 - Xygeni incident blog post: (URL to be added upon publication)

CVE-2026-31976 Affected Xygeni/xygeni action Versions

1 component(s)
Fixed Versions:
6.4.0
Product / Package Ecosystem Affected Versions Fixed Version
xygeni/xygeni-action
GitHub Actions
≥ 5
< 6.4.0
6.4.0

References

Frequently Asked Questions

What is CVE-2026-31976?
CVE-2026-31976 is a security vulnerability in Xygeni/xygeni action involving xygeni-action v5 tag poisoned with C2 backdoor under CWE-506: Embedded Malicious Code.
Which Xygeni/xygeni action versions are affected?
Affected versions include releases prior to 6.4.0 across affected packages: xygeni/xygeni-action.
What version fixes CVE-2026-31976?
Upgrading to 6.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is xygeni/xygeni-action affected?
Yes, xygeni/xygeni-action is affected in releases prior to 6.4.0. Upgrade your dependency to 6.4.0 or later.
What CWE is associated with CVE-2026-31976?
CVE-2026-31976 is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check GitHub Actions dependencies for CVE-2026-31976?
Run the dependency tree command: 'inspect dependencies for xygeni/xygeni-action'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f8q5-h5qh-33mh",
  "modified" : "2026-03-11T22:18:44Z",
  "published" : "2026-03-11T22:18:44Z",
  "aliases" : [ "CVE-2026-31976" ],
  "summary" : "xygeni-action v5 tag poisoned with C2 backdoor",
  "details" : "### Description\n\nOn 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.\n\nHowever, 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.\n\nThe malicious code, disguised as a \"scanner version telemetry\" step, operates as follows:\n\n1. Registers the CI runner with a C2 server at `91.214.78.178` (via `security-verify.91.214.78.178.nip.io`), transmitting hostname, username, and OS version.\n2. Polls the C2 server every 2–7 seconds for 180 seconds, receiving and executing arbitrary shell commands via `eval`.\n3. Compresses and base64-encodes command output before exfiltrating it back to the C2 server.\n\nThe implant runs silently in the background alongside the legitimate scan, suppresses all errors, skips TLS certificate verification, and uses randomized polling intervals to evade detection.\n\n### Impact\n\nThis 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.\n\nThe severity is set to Critical based on the potential impact. However, several factors reduce the realized risk: the `v5` tag was primarily referenced by Xygeni-owned and Xygeni-affiliated repositories; no external public repositories were found using the compromised tag (though usage in private repositories cannot be ruled out); the exposure window was approximately 6 days; and no confirmed exploitation of downstream users has been established to date.\n\n### Patches\n\nThe compromised `v5` tag has been removed from the repository. Users should update their workflows to pin to the verified safe commit SHA corresponding to v6.4.0:\n\n```yaml\nuses: xygeni/xygeni-action@13c6ed2797df7d85749864e2cbcf09c893f43b23 # v6.4.0\n```\n\nWorkflows still referencing `@v5` will fail with a reference not found error, as the tag no longer exists.\n\nIf your workflows ran with `@v5` during the affected window, you should also:\n\n- Rotate all secrets that were available to the CI runner (repository secrets, environment secrets, deploy keys, cloud provider tokens).\n- Audit CI logs for outbound connections to `91.214.78.178` or DNS lookups for `security-verify.91.214.78.178.nip.io`.\n- Review recent releases and published artifacts for signs of tampering.\n\n\n### Workarounds\n\nAs an alternative to using the GitHub Action, you may install and run the Xygeni scanner directly via the CLI installation method documented at https://docs.xygeni.io/xygeni-scanner-cli/xygeni-cli-overview/xygeni-cli-installation. This bypasses the GitHub Action entirely and is not affected by this incident.\n\n### References\n\n- GitHub issue: https://github.com/xygeni/xygeni-action/issues/54\n- Xygeni incident blog post: (URL to be added upon publication)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "GitHub Actions",
      "name" : "xygeni/xygeni-action"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5"
      }, {
        "fixed" : "6.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/xygeni/xygeni-action/security/advisories/GHSA-f8q5-h5qh-33mh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-31976"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/xygeni/xygeni-action/issues/54"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/xygeni/xygeni-action"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-11T22:18:44Z",
    "nvd_published_at" : "2026-03-11T20:16:17Z"
  }
}