VulnerabilityPublished 29 Sep 2025Updated 15 Oct 2025

CVE-2025-61659: magicmonty bash-git-prompt · Insecure Temporary File

Affects magicmonty bash-git-promptSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 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 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/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 29 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

Affected software

Product	Affected	Fixed in
magicmonty bash-git-prompt	Affected =2.6.1	Fixed in–

AI-suggested

To mitigate CVE-2025-61659, European organizations should first update bash-git-prompt to a version that addresses the insecure temporary file usage once available. Until patches are released, users should avoid using vulnerable versions and consider disabling bash-git-prompt in multi-user or sensitive environments. Implement secure temporary file creation practices by using system calls or libraries that generate unpredictable temporary filenames (e.g., mkstemp) instead of predictable patterns. Restrict permissions on the /tmp directory to prevent unauthorized users from creating or modifying files. Employ mandatory access controls (e.g., AppArmor, SELinux) to limit the ability of local users to interfere with temporary files used by bash-git-prompt. Conduct regular audits of temporary file usage in scripts and development tools to identify similar insecure patterns. Educate developers and system administrators about the risks of predictable temporary files and enforce secure coding standards. Monitor system logs for suspicious file access or modification attempts in /tmp. Finally, isolate build and development environments to reduce the risk of local privilege escalation through such vulnerabilities.

Description

bash-git-prompt 2.6.1 through 2.7.1 insecurely uses the /tmp/git-index-private$$ file, which has a predictable name.

Impact

For European organizations, the impact of CVE-2025-61659 can be significant in environments where bash-git-prompt is used, particularly in software development, continuous integration, and deployment pipelines. Exploitation could allow local attackers to manipulate temporary files, leading to unauthorized access or modification of sensitive data, injection of malicious commands, or disruption of development workflows. This could result in data leaks, integrity violations in source code or build artifacts, and potential denial of service if critical scripts fail. Organizations relying on shared development environments or multi-user systems are at higher risk, as attackers with local access could leverage this vulnerability to escalate privileges or compromise other users' sessions. Although the attack requires local access, insider threats or compromised accounts could exploit this vulnerability. The medium severity rating reflects a moderate risk that should not be ignored, especially in high-security or regulated sectors prevalent in Europe such as finance, healthcare, and critical infrastructure. Failure to address this vulnerability could lead to compliance issues under GDPR or other data protection regulations if sensitive data is exposed or integrity is compromised.

CWE-377Insecure Temporary File (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Explore for Predictable Temporary File Names (opens in a new tab)
Screen Temporary Files for Sensitive Information (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/magicmonty/bash-git-prompt/issues/561 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 16:16 UTC

WeaknessesCWE-377

Technical details

References

Community reviews

Related threats