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.
CVE-2026-46699
This high-severity CVE scores 7.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.6
- EG Score
- 7.6(medium)
- EPSS
- 10.2%
- KEV
- Not listed
Published
June 18, 2026
Last Modified
June 23, 2026
Advisory Details (2)
Auto-updated Jun 18, 2026Logical Privilege Escalation via Username Recyclability in conda-forge Infrastructure leading to supply chain vuln · Advisory · conda-forge/conda-smithy · GitHub
https://github.com/conda-forge/conda-smithy/security/advisories/GHSA-g95q-3cmj-fvh8commit 3b0bcd92ebd6 (conda-forge/conda-smithy)
Patch available: conda-forge/conda-smithy v3.61.0 (contains commit 3b0bcd92ebd6)
https://github.com/conda-forge/conda-smithy/commit/3b0bcd92ebd6f41edd341401d84583a20911c587Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 76× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 22:44 UTCEG score recompute
- 2026-07-15 09:49 UTCEG score recompute
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 20:44 UTCEG score recompute
- 2026-07-14 07:38 UTCEG score recompute
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 18:38 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 05:43 UTCEG score recompute
- 2026-07-12 16:48 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 03:49 UTCEG score recompute
- 2026-07-11 14:55 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 02:00 UTCEG score recompute
- 2026-07-10 12:42 UTCEG score recompute
- 2026-07-09 23:47 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 10:53 UTCEG score recompute
- 2026-07-08 21:44 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 08:49 UTCEG score recompute
- 2026-07-07 19:52 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 06:00 UTCEG score recompute
Show 51 moreShow fewer
- 2026-07-06 17:02 UTCEG score recompute
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 04:05 UTCEG score recompute
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 15:10 UTCEG score recompute
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:15 UTCEG score recompute
- 2026-07-04 13:20 UTCEG score recompute
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 00:25 UTCEG score recompute
- 2026-07-03 11:30 UTCEG score recompute
- 2026-07-02 22:28 UTCEG score recompute
- 2026-07-02 09:34 UTCEG score recompute
- 2026-07-01 20:38 UTCEG score recompute
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 07:44 UTCEG score recompute
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 18:49 UTCEG score recompute
- 2026-06-30 05:54 UTCEG score recompute
- 2026-06-29 16:59 UTCEG score recompute
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 04:02 UTCEG score recompute
- 2026-06-28 15:03 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 02:08 UTCEG score recompute
- 2026-06-27 13:14 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-27 00:19 UTCEG score recompute
- 2026-06-26 11:24 UTCEG score recompute
- 2026-06-25 21:40 UTCEG score recompute
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-25 08:44 UTCEG score recompute
- 2026-06-24 19:48 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-24 06:52 UTCEG score recompute
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 17:57 UTCEG score recompute
- 2026-06-23 05:02 UTCEG score recompute
- 2026-06-22 16:00 UTCEG score recompute
- 2026-06-22 03:05 UTCEG score recompute
- 2026-06-21 14:05 UTCEG score recompute
- 2026-06-21 01:10 UTCEG score recompute
- 2026-06-20 12:12 UTCEG score recompute
- 2026-06-19 23:16 UTCEG score recompute
- 2026-06-19 10:20 UTCEG score recompute
- 2026-06-18 21:24 UTCEG score recompute
- 2026-06-18 21:23 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-284
Frequently asked(5)
What is CVE-2026-46699?
When was CVE-2026-46699 disclosed?
Is CVE-2026-46699 actively exploited?
What is the CVSS score of CVE-2026-46699?
How do I remediate CVE-2026-46699?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-46699
Is Your Infrastructure Affected by CVE-2026-46699?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.