{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40680 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40680 is a medium-severity vulnerability in CapillaryScope, published on 24 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40680 and fix it if it is affected.\n\nWhat it is: CVE-2025-40680 is a medium-severity vulnerability in CapillaryScope, published on 24 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40680 in the wild and no public exploit code.\n\nAffected product: CapillaryScope. 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-40680/ (Markdown: https://insights.sbomify.com/CVE-2025-40680/index.md)","id":"CVE-2025-40680","markdown":"https://insights.sbomify.com/CVE-2025-40680/index.md","name":"CVE-2025-40680","record":{"aliases":["GHSA-3g73-h9cm-2486"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CapillaryScope desktop app","requires_auth":"low_privilege","summary":"Local attackers can read proxy credentials and JWT tokens from the Windows registry due to lack of encryption in CapillaryScope.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"Lack of sensitive data encryption in CapillaryScope v2.5.0 of Capillary io, which stores both the proxy credentials and the JWT session token in plain text within different registry keys on the Windows operating system. Any authenticated local user with read access to the registry can extract these sensitive values.","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":"Encryption of sensitive data in CapillaryScope missing","id":"CVE-2025-40680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-Site Scripting (XSS) in xCally Omnichannel","id":"CVE-2025-40681"},"packages":[],"prev":{"headline":"HTML injection in Isshue from Bdtask","id":"CVE-2025-40679"},"products":["CapillaryScope"],"published":"2025-07-24","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":"2025-07-24","vendors":["Capillary io"]},"summary":"Local attackers can read proxy credentials and JWT tokens from the Windows registry due to lack of encryption in CapillaryScope.","url":"https://insights.sbomify.com/CVE-2025-40680/"}