CVE Catalog

CVE-2026-53942

CriticalCVSS 9.9
Published: Translated: NVD NIST

Summary

In conda/conda prior to commit 9c0f238, a GitHub Actions Pwn Request vulnerability remains in .github/workflows/update.yml. It is triggered by comments containing @conda-bot render or @conda-bot recreate, allowing an untrusted PR to reach Jinja2 template rendering in a privileged token context.

Risk Assessment

An attacker could leverage an untrusted comment or PR to execute code in the context of a privileged CI token, potentially compromising the repository or releases. This poses a serious software supply chain risk.

Recommendation

Update the repository to commit 9c0f238 or later, which contains the fix. Also review the permissions of tokens used in workflows.

Related vulnerabilities

Original NVD description (English source)

Conda Organization Infrastructure is a centralized location for infrastructure codes. Prior to commit 9c0f238, a GitHub Actions Pwn Request vulnerability appears to remain present in conda/conda. The affected workflow is .github/workflows/update.yml. It is triggered by issue_comment events containing @conda-bot render or @conda-bot recreate. For the render path, the workflow obtains the pull request head repository and branch from the PR API, checks out that PR-controlled repository/ref using secrets.SYNC_TOKEN, and then runs conda/actions/template-files@7f6830b1428a9bd47f0b068892c77eae95207037. The external template-files action reads its default configuration and templates from the checked-out working directory. In the confirmed finding, that action uses an unsandboxed Jinja2 environment to render attacker-controlled template content. This creates a Pwn Request chain in which an untrusted PR/comment path can reach template rendering in a privileged token context. This issue has been patched via commit 9c0f238.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS