{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-46699 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-46699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46699 is a high-severity authentication bypass vulnerability in conda-forge conda-smithy, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46699 and fix it if it is affected.\n\nWhat it is: CVE-2026-46699 is a high-severity authentication bypass vulnerability in conda-forge conda-smithy, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-46699 in the wild and no public exploit code.\n\nAffected product: conda-forge conda-smithy. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46699/ (Markdown: https://insights.sbomify.com/CVE-2026-46699/index.md)","id":"CVE-2026-46699","markdown":"https://insights.sbomify.com/CVE-2026-46699/index.md","name":"CVE-2026-46699","record":{"aliases":["GHSA-g95q-3cmj-fvh8"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"conda-smithy","requires_auth":"none","summary":"Attackers can gain write access to conda-forge feedstock repositories by taking over GitHub usernames used for invitation routing.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in conda-smithy","id":"CVE-2026-46699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"@actual-app/sync-server's missing authorization on GET /secret/:name allows non-admin OpenID users to enumerate admin-configured bank-sync secrets","id":"CVE-2026-46700"},"packages":[],"prev":{"headline":"Fediverse Embeds: Public-nonce SSRF via ftf_get_site_info AJAX action","id":"CVE-2026-46698"},"products":["conda-smithy"],"published":"2026-06-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["conda-forge"]},"summary":"Attackers can gain write access to conda-forge feedstock repositories by taking over GitHub usernames used for invitation routing.","url":"https://insights.sbomify.com/CVE-2026-46699/"}