{"answers":{"affected":"3 open source packages ship an affected version, including lollms.","exploited":"There is no known exploitation of CVE-2025-6386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-6386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6386 is a high-severity vulnerability in parisneo/lollms, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-6386 and fix it if it is affected.\n\nWhat it is: CVE-2025-6386 is a high-severity vulnerability in parisneo/lollms, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-6386 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- lollms (PyPI): affected all versions up to 11.0.0; no fix listed\n- lollms (PyPI): affected all versions up to 11.0.0; no fix listed\n- lollms (PyPI): affected all versions up to 11.0.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-6386/ (Markdown: https://insights.sbomify.com/CVE-2025-6386/index.md)","id":"CVE-2025-6386","markdown":"https://insights.sbomify.com/CVE-2025-6386/index.md","name":"CVE-2025-6386","record":{"aliases":["GHSA-j5pr-vrjj-9v4h","PYSEC-2026-1590"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"lollms web application","requires_auth":"none","summary":"Attackers can enumerate valid usernames and guess passwords by analyzing response time differences in the authentication function.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"The parisneo/lollms repository is affected by a timing attack vulnerability in the `authenticate_user` function within the `lollms_authentication.py` 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Timing Attack Vulnerability in parisneo/lollms","id":"CVE-2025-6386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"WP Get The Table \u003c= 1.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via url Parameter","id":"CVE-2025-6387"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["11.0.0"],"package":"lollms","purl":null,"source":"GHSA-j5pr-vrjj-9v4h"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["11.0.0"],"package":"lollms","purl":"pkg:pypi/lollms","source":"GHSA-j5pr-vrjj-9v4h"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["11.0.0"],"package":"lollms","purl":"pkg:pypi/lollms","source":"PYSEC-2026-1590"}],"prev":{"headline":"WP Applink \u003c= 0.4.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via title Parameter","id":"CVE-2025-6385"},"products":["parisneo/lollms"],"published":"2025-07-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-07","vendors":["parisneo"]},"summary":"Attackers can enumerate valid usernames and guess passwords by analyzing response time differences in the authentication function.","url":"https://insights.sbomify.com/CVE-2025-6386/"}