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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 5
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-23 14:57
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-23 19:42
- StatusReceived → PublishedNVD modified 2026-10-23 14:57
- StatusPublished → ReceivedNVD modified 2026-10-23 15:17
- First seenCVSS 9.9 · condaNVD modified 2026-10-23 14:57
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.