VulnerabilityPublished 24 Jul 2025

CVE-2025-40680: Capillary io CapillaryScope · Missing Encryption of Sensitive Data

Affects Capillary io CapillaryScopeSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Capillary io CapillaryScope	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-40680, European organizations should implement the following specific measures: 1) Restrict local user access to the Windows registry keys where CapillaryScope stores sensitive data by applying strict Access Control Lists (ACLs) to limit read permissions only to necessary system accounts. 2) Employ endpoint protection solutions that monitor and alert on unauthorized registry access attempts. 3) Use application whitelisting and privilege management to prevent unauthorized users from running tools that can read registry data. 4) Where possible, isolate systems running CapillaryScope to trusted users only and avoid shared user environments. 5) Monitor logs for unusual local access patterns or attempts to extract credentials. 6) Engage with Capillary io to obtain patches or updates that encrypt sensitive data storage; until then, consider encrypting sensitive configuration data externally or using secure vault solutions integrated with CapillaryScope if supported. 7) Conduct regular audits of local user privileges and registry permissions to ensure compliance with the principle of least privilege. 8) Educate users about the risks of local credential exposure and enforce strong endpoint security policies. These steps go beyond generic advice by focusing on registry access controls, endpoint monitoring, and organizational policies tailored to the specific vulnerability context.

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.

Impact

For European organizations, the impact of CVE-2025-40680 can be significant, especially in sectors where CapillaryScope is deployed for monitoring or proxy management. The exposure of proxy credentials and JWT tokens can lead to unauthorized access to internal or external network resources, potentially enabling attackers to bypass security controls or impersonate legitimate users. This could result in data breaches, unauthorized data exfiltration, or disruption of business processes. Organizations with shared workstations or environments where multiple users have local access are at higher risk. Additionally, if the compromised JWT tokens are used for session management in critical applications, attackers could hijack sessions and escalate privileges. Given the medium severity and local attack vector, the threat is more pronounced in environments with weak endpoint security or insufficient user access controls. The absence of encryption also raises compliance concerns under GDPR and other European data protection regulations, as sensitive authentication data is inadequately protected. Failure to address this vulnerability could lead to regulatory penalties and reputational damage.

CWE-311Missing Encryption of Sensitive Data (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not encrypt sensitive or critical information before storage or transmission.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Clearly specify which data or resources are valuable enough that they should be protected by encryption. Require that any transmission or storage of this data/resource should use well-vetted encryption algorithms.
Architecture and Design
Ensure that encryption is properly integrated into the system design, including but not necessarily limited to: Encryption that is needed to store or transmit private data of the users of the system; Encryption that is needed to protect the system itself from unauthorized disclosure or tampering
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
User Privacy Protection (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V6.1.3 (opens in a new tab)
V6.1.2 (opens in a new tab)
V6.1.1 (opens in a new tab)
Attack patterns
Sniffing Attacks (opens in a new tab)
Sniffing Network Traffic (opens in a new tab)
Lifting Sensitive Data Embedded in Cache (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

incibe.es/en/incibe-cert/notices/aviso/encryption-sensitive-data-capillaryscope-missing (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Jul 2025, 12:47 UTC

WeaknessesCWE-311

Technical details

References

Community reviews

Related threats