# CVE-2026-53942: Conda Organization Infrastructure is a centralized location for infrastructure codes.


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-pf87-fcg3-wjfh

## What is CVE-2026-53942?

CVE-2026-53942 is a critical vulnerability in conda infrastructure, published on 23 Oct 2026. 

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-53942?


## How do I fix CVE-2026-53942?

No fix has been published for CVE-2026-53942 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53942 being exploited?

There is no known exploitation of CVE-2026-53942 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53942 and fix it if it is affected.

What it is: CVE-2026-53942 is a critical vulnerability in conda infrastructure, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-53942 in the wild and no public exploit code.

Affected product: conda infrastructure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53942/ (Markdown: https://insights.sbomify.com/CVE-2026-53942/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53942
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53942
- OSV: https://osv.dev/vulnerability/CVE-2026-53942

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53942/
Summaries are generated and may contain mistakes; the official description above is the record.