Pwn request in Conda infrastructure workflow exposes SYNC_TOKEN
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-94.
Summary
Conda Organization Infrastructure before commit 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55 is affected. The update workflow checks out pull request code with a privileged token and renders attacker-controlled templates in an unsandboxed Jinja2 environment, a code injection flaw (CWE-94). A remote attacker with low privileges can reach this path by commenting on a pull request with a render or recreate command.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| conda | infrastructure | before 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55 | 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55 | Patch available | CNA |
- infrastructure Vendorconda Affected before 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55 Fixed in 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55 Patch available CNA
Remediation
Commit 9c0f238 patches this issue. Use infrastructure code that includes that commit.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA infrastructure (conda) Fixed in 9c0f23857282ff5cf7a6b3ad6bf0dd6f9974be55
Timeline
- 2026-10-23 Threatist record created from CVE-2026-53942
References
More conda vulnerabilities
- TI-2026-38909 Conda: Entry-point path traversal in noarch:python install (arbitrary file write) — canonical Python implementation CVSS 3.1HIGH 8.8
- TI-2025-23835 Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors CVSS 4.0HIGH 8.2
- TI-2025-23836 Conda-build Vulnerable to Path Traversal via Malicious Tar File CVSS 4.0MEDIUM 5.6
- TI-2025-39776 (conda) Constructor: Excessive permissions during and after installation CVSS 3.1HIGH 7.8
- TI-2025-23837 Conda-build vulnerable to supply chain attack vector due to pyproject.toml referring to dependencies not present in PyPI CVSS 4.0HIGH 7.2
- TI-2024-30877 Miniconda3 macOS installers before 23.11.0-1 contain a local privilege escalation… CVSS 3.1HIGH 7.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences