CVE-2026-46699
Deferred Deferred - Pending Action

GitHub Username Takeover in conda-smithy Feedstock Repositories

Vulnerability report for CVE-2026-46699, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-18

Last updated on: 2026-06-22

Assigner: GitHub, Inc.

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.61.0, a vulnerability in the conda-forge automated webservices allowed unintended write access to feedstock repositories through GitHub username takeover. The root cause is the use of mutable GitHub usernames as identifiers for repository invitation routing, rather than stable, immutable GitHub user IDs. Version 3.61.0 fixes the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-18
Last Modified
2026-06-22
Generated
2026-07-09
AI Q&A
2026-06-19
EPSS Evaluated
2026-07-08
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
conda-smithy conda-smithy to 3.61.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in conda-smithy versions prior to 3.61.0. Conda-smithy is a tool used to combine a conda recipe with configurations to build using freely hosted CI services into a single repository. The vulnerability allowed unintended write access to feedstock repositories through GitHub username takeover. The root cause was the use of mutable GitHub usernames as identifiers for routing repository invitations instead of stable, immutable GitHub user IDs.

Impact Analysis

The vulnerability can lead to unauthorized write access to feedstock repositories. This means an attacker who takes over a GitHub username could potentially modify repository contents, which could compromise the integrity of the software builds and potentially introduce malicious code or disrupt the build process.

Compliance Impact

The vulnerability in conda-smithy prior to version 3.61.0 allowed unintended write access to feedstock repositories through GitHub username takeover. This unauthorized access could potentially lead to unauthorized modification of repository contents, which may impact the integrity and confidentiality of data managed within these repositories.

Such unauthorized access and potential data integrity issues could affect compliance with standards and regulations like GDPR and HIPAA, which require protection of data confidentiality, integrity, and proper access controls. However, the provided information does not specify direct impacts or compliance violations related to these regulations.

Mitigation Strategies

To mitigate this vulnerability, you should upgrade conda-smithy to version 3.61.0 or later, as this version fixes the issue related to unintended write access caused by GitHub username takeover.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46699. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart