CVE-2025-49843: conda-smithy · Incorrect Default Permissions
Affects conda-smithySource CVE Database V5
Not known to be exploited · CVSS 2.7 Low : upgrade to 3.47.1 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.47.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade conda-smithy to 3.47.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIconda-smithypkg:pypi/conda-smithyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade conda-smithy to version 3.47.1 or later immediately to ensure the patch addressing the incorrect default permissions is applied. 2. Review and audit file permission settings on all CI configuration files and build artifacts generated by conda-smithy, ensuring they adhere strictly to the principle of least privilege (e.g., permissions set to 0o600 or more restrictive). 3. Implement strict access controls and user isolation in shared CI environments, such as containerization or dedicated build agents per user/project, to minimize the risk of unauthorized file access. 4. Regularly monitor and log access to sensitive configuration files within CI pipelines to detect anomalous or unauthorized access attempts. 5. Educate development and DevOps teams about secure file permission practices and the risks associated with misconfigured CI/CD tools. 6. Where feasible, encrypt sensitive configuration files or secrets at rest and in transit within CI workflows to add an additional layer of protection. 7. Conduct periodic security reviews of CI/CD pipeline configurations and dependencies to identify and remediate similar permission or configuration issues proactively.
Description
conda-smithy is a tool for combining a conda recipe with configurations to build using freely hosted CI services into a single repository. Prior to version 3.47.1, the travis_headers function in the conda-smithy repository creates files with permissions exceeding 0o600, allowing read and write access beyond the intended user/owner. This violates the principle of least privilege, which mandates restricting file permissions to the minimum necessary. An attacker could exploit this to access configuration files in shared hosting environments. This issue has been patched in version 3.47.1.
References
- github.com/conda-forge/conda-smithy/security/advisories/GHSA-h9v8-rrqg-3m95 (opens in a new tab)
- github.com/conda-forge/conda-smithy/commit/24cc0a55a363479e797c825be3a7f2603ef374a1 (opens in a new tab)
- github.com/conda-forge/conda-smithy/blob/1dc21086a476f6aeb6c1bad8bf58474bf3a8f8f0/conda_smithy/ci_register.py (opens in a new tab)