{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60639 exists.","fix":"No fix has been published for CVE-2025-60639 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60639 is a medium-severity vulnerability in n/a, published on 16 Oct 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-60639 and fix it if it is affected.\n\nWhat it is: CVE-2025-60639 is a medium-severity vulnerability in n/a, published on 16 Oct 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-60639 exists.\n\nAffected product: n/a. 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-60639/ (Markdown: https://insights.sbomify.com/CVE-2025-60639/index.md)","id":"CVE-2025-60639","markdown":"https://insights.sbomify.com/CVE-2025-60639/index.md","name":"CVE-2025-60639","record":{"aliases":["GHSA-6cmv-xcmf-v4pm"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ATLAS-EPIC","requires_auth":"none","summary":"Hardcoded credentials in ATLAS-EPIC allow attackers to gain unauthorized access to the system.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Hardcoded credentials in gsigel14 ATLAS-EPIC commit f29312c (2025-05-26).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-60639","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Deserialization in n/a","id":"CVE-2025-60641"},"packages":[],"prev":{"headline":"NSSF panic due to nil pointer dereference when expiry field is omitted in NSSAIAvailability POST","id":"CVE-2025-60638"},"products":["n/a"],"published":"2025-10-16","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-04","vendors":["n/a"]},"summary":"Hardcoded credentials in ATLAS-EPIC allow attackers to gain unauthorized access to the system.","url":"https://insights.sbomify.com/CVE-2025-60639/"}