Vulnerability · CVE-2025-6386
The parisneo/lollms repository is affected by a timing attack vulnerability in the function within the file.
Published Jul 7, 2025 · catalog updated Jul 7, 2025 · The parisneo/lollms repository is
Check this week
CVE-2025-6386 is not in CISA KEV. FIRST estimates a 41.00% chance of exploitation in the next 30 days. Check whether you run The parisneo/lollms repository is.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (The parisneo/lollms repository is).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.5
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 41.00%
- Remediation
- Version ranges on file
- Affected products
- vendor parisneo parisneo/lollms unspecified <20.1
The parisneo/lollms repository is affected by a timing attack vulnerability in the function within the file. This vulnerability allows attackers to enumerate valid usernames and guess passwords incrementally by analyzing response time differences. The affected version is the latest, and the issue is resolved in version 20.1. The vulnerability arises from the use of Python's default string equality operator for password comparison, which compares characters sequentially and exits on the first mismatch, leading to variable response times based on the number of matching initial characters.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor parisneo parisneo/lollms unspecified <20.1unspecified <20.1
How to fix CVE-2025-6386
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-6386 is not in CISA KEV. FIRST estimates a 41.00% chance of exploitation in the next 30 days. Check whether you run The parisneo/lollms repository is.
Which versions are affected?
Compare what you have installed with parisneo parisneo/lollms unspecified <20.1 unspecified <20.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 41.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jul 7, 2025 · EUVD
Detected
The parisneo/lollms repository is affected by a timing attack vulnerability in the function within the file. This vulnerability allows attackers to enumerate valid usernames and guess passwords incrementally by analyzing response time differences. The affected version is the latest, and the issue is resolved in version 20.1. The vulnerability arises from the use of Python's default string equality
Jul 7, 2025 · EUVD
Updated
The parisneo/lollms repository is affected by a timing attack vulnerability in the function within the file. This vulnerability allows attackers to enumerate valid usernames and guess passwords incrementally by analyzing response time differences. The affected version is the latest, and the issue is resolved in version 20.1. The vulnerability arises from the use of Python's default string equality
Sources
- CVE.orgVulnerability recordCVE-2025-6386
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-20213
The parisneo/lollms repository is affected by a timing attack vulnerability in the function within the file. This vulnerability allows attackers to enumerate valid usernames and guess passwords incrementally by analyzing response time differences. The affected version is the late
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Jul 7, 2025. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.