CVE-2025-64299VulnerabilityPublished 21 Nov 2025

CVE-2025-64299: LogStare Collector (for Windows) · Insertion of sensitive information into sent data

Affects LogStare Collector (for Windows)Source CVE Database V5

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.0 base score

4.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Nov 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 2026-10-26.

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 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
LogStare Inc. LogStare Collector (for Windows)	Affected <=2.4.1	Fixed in–

AI-suggested

Organizations should immediately inventory their use of LogStare Collector and identify any instances running version 2.4.1 or earlier. They should restrict administrative privileges to trusted personnel only and implement strict access controls and monitoring on systems running the affected software. Until a vendor patch is available, consider isolating LogStare Collector servers to minimize exposure and monitor logs for unusual access patterns or attempts to extract credential data. Employ multi-factor authentication (MFA) for administrative accounts to reduce the risk of credential compromise. Additionally, enforce strong password policies and consider using password hash salting and key stretching techniques if supported by the environment. Regularly audit and rotate credentials to limit the window of opportunity for attackers. Engage with LogStare Inc. for official patches or updates and apply them promptly once released. Finally, incorporate this vulnerability into incident response plans to quickly detect and respond to any exploitation attempts.

Description

LogStare Collector improperly handles the password hash data. An administrative user may obtain the other users' password hashes.

Impact

For European organizations, the exposure of password hashes through this vulnerability poses a significant confidentiality risk. If an attacker with administrative access extracts these hashes, they could perform offline brute-force or dictionary attacks to recover plaintext passwords, potentially escalating privileges or moving laterally across networks. This is particularly concerning for organizations subject to stringent data protection regulations such as GDPR, where unauthorized access to user credentials could lead to compliance violations and reputational damage. Critical infrastructure operators and enterprises using LogStare Collector for security monitoring may face increased risk of insider threats or compromised administrative accounts. The vulnerability does not directly affect system availability or integrity, but the indirect consequences of credential compromise could lead to broader security incidents. The medium severity rating reflects the need for timely remediation but indicates that exploitation requires existing administrative access, somewhat limiting the attack surface.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Nov 2025, 07:50 UTC

Technical details

References

Community reviews

Related threats