PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-46699 conda-forge CVE debrief

CVE-2026-46699 is a high-severity vulnerability in conda-smithy, a tool for combining conda recipes with configurations for building on freely hosted CI services. The vulnerability, caused by the use of mutable GitHub usernames as identifiers for repository invitation routing, allows unintended write access to feedstock repositories through GitHub username takeover. This issue was addressed in version 3.61.0, which fixes the root cause by using stable, immutable GitHub user IDs instead. Users of conda-smithy, especially those using versions prior to 3.61.0, should be aware of this vulnerability and take necessary precautions.

Vendor
conda-forge
Product
conda-smithy
CVSS
HIGH 7.6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-06-18
Original CVE updated
2026-06-23
Advisory published
2026-06-18
Advisory updated
2026-06-23

Who should care

Users of conda-smithy, especially those using versions prior to 3.61.0, should be aware of this vulnerability as it allows unintended write access to feedstock repositories through GitHub username takeover. Affected operators, platform administrators, vulnerability management teams, and security teams should review the official advisory and take necessary precautions to prevent exploitation.

Technical summary

A vulnerability in conda-smithy, prior to version 3.61.0, 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 by implementing stable, immutable GitHub user IDs for repository invitation routing, thereby preventing unintended write access to feedstock repositories.

Defensive priority

High priority should be given to updating conda-smithy to version 3.61.0 or later to prevent unintended write access to feedstock repositories. Additionally, reviewing and updating GitHub repository invitation routing and monitoring feedstock repositories for suspicious activity are recommended.

Recommended defensive actions

  • Update conda-smithy to version 3.61.0 or later
  • Review and update GitHub repository invitation routing to use stable, immutable GitHub user IDs
  • Monitor feedstock repositories for any suspicious activity
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was reported through the conda-forge automated webservices and was addressed in version 3.61.0 of conda-smithy. The NVD entry for this CVE is currently Deferred. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify affected deployments and review official advisories for specific guidance.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-46699 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-46699

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-46699 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-46699

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.