{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2025-53705 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53705 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53705 is a high-severity memory corruption vulnerability in Ashlar Cobalt, published on 18 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-53705 and fix it if it is affected.\n\nWhat it is: CVE-2025-53705 is a high-severity memory corruption vulnerability in Ashlar Cobalt, published on 18 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-53705 in the wild and no public exploit code.\n\nAffected product: Ashlar Cobalt. 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-53705/ (Markdown: https://insights.sbomify.com/CVE-2025-53705/index.md)","id":"CVE-2025-53705","markdown":"https://insights.sbomify.com/CVE-2025-53705/index.md","name":"CVE-2025-53705","record":{"aliases":["GHSA-pgqv-678f-757m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ashlar-Vellum CAD software","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into opening malicious CO files in Ashlar-Vellum CAD applications.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"argon","vendor":"ashlar"},{"product":"cobalt","vendor":"ashlar"},{"product":"cobalt_share","vendor":"ashlar"},{"product":"lithium","vendor":"ashlar"},{"product":"xenon","vendor":"ashlar"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, and Cobalt Share versions prior to 12.6.1204.204, the affected applications lack proper validation of user-supplied data when parsing CO files. This could lead to an out-of-bounds write. An attacker could leverage this vulnerability to execute arbitrary code in the context of the current process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share Out-of-bounds Write","id":"CVE-2025-53705","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ashlar:cobalt","products":["ashlar:cobalt"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-53706"},"packages":[],"prev":{"headline":"MAXHUB Pivot Weak Password Recovery Mechanism for Forgotten Password","id":"CVE-2025-53704"},"products":["Argon","Cobalt","Cobalt Share","Lithium","Xenon"],"published":"2025-08-18","related":[{"cvss_score":8.4,"headline":"Out-of-bounds write in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share","id":"CVE-2025-65086","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.4,"headline":"Out-of-bounds read in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share","id":"CVE-2025-65087","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.4,"headline":"Out-of-bounds read in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share","id":"CVE-2025-65088","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.4,"headline":"Out-of-bounds Write in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share","id":"CVE-2025-65084","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.4,"headline":"Heap-based Buffer Overflow in Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share","id":"CVE-2025-65085","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.4,"headline":"Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share Out-of-bounds Read","id":"CVE-2025-41392","kev_date_added":null,"published":"2025-08-18"},{"cvss_score":8.4,"headline":"Ashlar-Vellum Cobalt, Xenon, Argon, Lithium, Cobalt Share Heap-based Buffer Overflow","id":"CVE-2025-46269","kev_date_added":null,"published":"2025-08-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"total"},"state":"PUBLISHED","updated":"2025-08-19","vendors":["Ashlar-Vellum"]},"summary":"Attackers can execute arbitrary code by tricking users into opening malicious CO files in Ashlar-Vellum CAD applications.","url":"https://insights.sbomify.com/CVE-2025-53705/"}