CVE-2026-85701 in freegpt-webui
Summary
by MITRE • 09/05/2026
A vulnerability has been found in ramon-victor freegpt-webui up to 098db3dfeb41555c2ca9269df0f13e10ec1c35dc. This issue affects the function ChatCompletion.create of the file g4f/__init__.py of the component Authentication Check. Such manipulation leads to missing authentication. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. This vulnerability only affects products that are no longer supported by the maintainer.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 09/05/2026
The identified security flaw resides within the freegpt-webui project, specifically affecting versions up to commit 098db3dfeb41555c2ca9269df0f13e10ec1c35dc. This vulnerability is located in the ChatCompletion.create function found in the g4f/_init_.py file and impacts the component responsible for authentication checks. The core technical issue stems from a failure to properly enforce access controls, resulting in missing authentication mechanisms that allow unauthorized entities to interact with sensitive application functions. Because this flaw bypasses the intended security boundaries of the software, it represents a critical integrity violation where any remote actor can execute commands or retrieve data without valid credentials.
From an operational perspective, the impact of this vulnerability is severe due to its remote exploitability and public disclosure status. Attackers who are aware of this weakness can leverage existing exploits to gain unauthorized access to the system's capabilities. This lack of authentication control means that sensitive operations protected by the ChatCompletion interface can be triggered maliciously, potentially leading to data exfiltration, service disruption, or further compromise depending on how the underlying API is utilized. The fact that the exploit has been disclosed publicly significantly increases the risk landscape, as automated scanning tools and opportunistic attackers are likely already targeting systems running affected versions.
The context of this vulnerability is complicated by the project's release model, which utilizes a rolling release system for continuous delivery. Consequently, specific version numbers for updated or patched releases are not formally documented in traditional ways, making it difficult to determine exactly which builds contain fixes versus those that remain vulnerable. This ambiguity requires administrators and users to rely on commit hashes rather than semantic versioning when assessing their exposure. Furthermore, the advisory explicitly notes that this vulnerability only affects products no longer supported by the maintainer. This implies that there are likely no official patches or security updates available from the original developers, leaving affected deployments without a direct remediation path through standard update channels.
To mitigate the risks associated with this flaw, organizations and individuals must prioritize immediate isolation of any instances running code up to the specified commit hash. Since the maintainer has ceased support for these versions, relying on upstream fixes is not viable. Instead, mitigation strategies should focus on network-level controls such as restricting access to the affected service via firewalls or reverse proxies that enforce strict IP whitelisting and additional authentication layers external to the vulnerable application logic. If possible, migrating to a supported alternative or maintaining an isolated, air-gapped instance of the software for non-critical use cases is recommended. Continuous monitoring for unauthorized access attempts should also be implemented given the public nature of the exploit.
This vulnerability aligns with CWE-287, which describes Improper Authentication, where the system fails to correctly verify identity before granting access. In terms of offensive security frameworks, this flaw facilitates actions consistent with MITRE ATT&CK technique T1078, Valid Accounts, as it allows attackers to operate under false pretenses by bypassing credential verification entirely. The combination of remote exploitability and lack of vendor support underscores the critical need for proactive defense-in-depth measures rather than reliance on application-level security controls that have proven insufficient in this specific context.