VulnerabilityPublished 5 Sep 2025

CVE-2025-58401: Pierre-Adrien Vasseur Obsidian GitHub Copilot Plugin · Cleartext Storage of Sensitive Information

Affects Pierre-Adrien Vasseur Obsidian GitHub Copilot PluginSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.1.7 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score

6.8Medium

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

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: Low

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

Attack Vector: Local: The vulnerable component 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 remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Sep 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

Upgrade Pierre-Adrien Vasseur Obsidian GitHub Copilot Plugin to 1.1.7.

Affected software

Product	Affected	Fixed in
Pierre-Adrien Vasseur Obsidian GitHub Copilot Plugin	Affected <1.1.7	Fixed in 1.1.7

AI-suggested

European organizations should immediately update the Obsidian GitHub Copilot Plugin to version 1.1.7 or later, where the vulnerability is addressed. If you cannot patch yet, users should avoid storing GitHub API tokens in the plugin or use tokens with minimal scopes to limit potential damage. Organizations should enforce the use of short-lived tokens or OAuth flows that do not require persistent token storage. Implement endpoint security controls to prevent unauthorized local access, including disk encryption and strict user access controls. Regularly audit and rotate GitHub API tokens, especially those used with the plugin. Monitoring GitHub account activity for unusual operations can help detect exploitation. Additionally, educating developers about the risks of storing sensitive credentials in cleartext and encouraging the use of secure credential vaults or environment variables can reduce exposure. Finally, organizations should consider restricting plugin usage to trusted environments and integrating security scanning tools that detect insecure credential storage in development tools.

Description

Obsidian GitHub Copilot Plugin versions prior to 1.1.7 store Github API token in cleartext form. As a result, an attacker may perform unauthorized operations on the linked Github account.

Impact

For European organizations, this vulnerability can lead to unauthorized access to GitHub repositories, which are often used to store critical source code and infrastructure-as-code configurations. An attacker exploiting this vulnerability could exfiltrate proprietary code, inject malicious code, or disrupt development workflows by deleting or modifying repositories. This could result in intellectual property theft, supply chain compromise, and operational disruption. Organizations relying on the Obsidian GitHub Copilot Plugin for developer productivity may face increased risk of insider threats or malware that targets local systems to extract tokens. Additionally, compromised GitHub accounts could be used to launch further attacks such as phishing campaigns or distribution of malicious software, impacting the broader European digital ecosystem. The medium severity rating suggests that while exploitation requires local access, the consequences can be significant if tokens have extensive privileges. Given the widespread use of GitHub in European software development, the vulnerability could affect a broad range of sectors including finance, manufacturing, and government agencies.

References

Community reviews

Loading reviews…