{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32958 exists.","fix":"No fix has been published for CVE-2025-32958 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32958 is a critical vulnerability in AdeptLanguage Adept, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32958 and fix it if it is affected.\n\nWhat it is: CVE-2025-32958 is a critical vulnerability in AdeptLanguage Adept, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32958 exists.\n\nAffected product: AdeptLanguage Adept. 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-2025-32958/ (Markdown: https://insights.sbomify.com/CVE-2025-32958/index.md)","id":"CVE-2025-32958","markdown":"https://insights.sbomify.com/CVE-2025-32958/index.md","name":"CVE-2025-32958","record":{"aliases":["GHSA-8c7v-vccv-cx4q"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Adept programming language","requires_auth":"none","summary":"Attackers can extract the GITHUB_TOKEN from build artifacts to push malicious code or rewrite releases in the Adept repository.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Adept is a language for general purpose programming. Prior to commit a1a41b7, the remoteBuild.yml workflow file uses actions/upload-artifact@v4 to upload the mac-standalone artifact. This artifact is a zip of the current directory, which includes the automatically generated .git/config file containing the run's GITHUB_TOKEN. Seeing as the artifact can be downloaded prior to the end of the workflow, there is a few seconds where an attacker can extract the token from the artifact and use it with the Github API to push malicious code or rewrite release commits in the AdeptLanguage/Adept repository. This issue has been patched in commit a1a41b7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-03","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-03T11:36:11Z","kind":"github_poc","ref":"https://github.com/pvharmo2/gha-lab-b1fe4918c0","stars":0,"title":"Authorized security-research lab: reproduction of CVE-2025-32958 (GHSA-8c7v-vccv-cx4q) — GITHUB_TOKEN leaked into workflow artifacts by Adept's remoteBuild.yml (snapshot of AdeptLanguage/Adept @ 6a64554)"}],"tier":"weaponised"},"has_fix":false,"headline":"Adept exposed the GITHUB_TOKEN in workflow run artifact","id":"CVE-2025-32958","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"CUBA Vulnerable to Denial of Service (DoS) in the File Storage","id":"CVE-2025-32959"},"packages":[],"prev":{"headline":"baserCMS: unsafe File Upload Leading to Remote Code Execution (RCE)","id":"CVE-2025-32957"},"products":["Adept"],"published":"2025-04-21","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["AdeptLanguage"]},"summary":"Attackers can extract the GITHUB_TOKEN from build artifacts to push malicious code or rewrite releases in the Adept repository.","url":"https://insights.sbomify.com/CVE-2025-32958/"}