VulnerabilityPublished 8 Mar 2026Updated 10 Mar 2026

CVE-2026-3788: Bytedesk · Server-Side Request Forgery

Affects BytedeskSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
Bytedesk	Affected 1.3.0 – 1.3.9 10 affected builds	Fixed in–
GitHubbytedesk/bytedesk`pkg:github/bytedesk/bytedesk`Other threats	Affected 1.3.0 – 1.3.9 10 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-3788, organizations should immediately upgrade Bytedesk to version 1.4.5.4 or later, which contains the official patch addressing the SSRF vulnerability. Beyond patching, implement strict input validation and sanitization on any parameters that accept URLs or external resource identifiers to prevent manipulation. Employ network segmentation and firewall rules to restrict the server's ability to make arbitrary outbound requests, limiting access to only trusted endpoints. Monitor and log outbound requests from the Bytedesk server to detect unusual or unauthorized access attempts. Use web application firewalls (WAFs) with SSRF detection capabilities to block suspicious payloads. Conduct regular security assessments and code reviews focusing on external input handling. If upgrading is temporarily not possible, consider disabling or restricting the vulnerable component or function. Educate developers and administrators about SSRF risks and secure coding practices to prevent similar issues in the future.

Description

A security vulnerability has been detected in Bytedesk up to 1.3.9. This impacts the function getModels of the file source-code/src/main/java/com/bytedesk/ai/springai/providers/openrouter/SpringAIOpenrouterRestService.java of the component SpringAIOpenrouterRestController. Such manipulation of the argument apiUrl leads to server-side request forgery. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.4.5.4 will fix this issue. The name of the patch is 975e39e4dd527596987559f56c5f9f973f64eff7. It is recommended to upgrade the affected component.

Impact

The SSRF vulnerability in Bytedesk could allow attackers to make unauthorized requests from the vulnerable server to internal or external systems. This can lead to several impacts: unauthorized access to internal network services that are not exposed externally, potentially exposing sensitive data or internal APIs; information disclosure if the attacker can retrieve internal metadata or configuration details; potential pivoting to other internal systems leading to broader network compromise; disruption of service if the attacker causes the server to make malicious or resource-intensive requests; and undermining trust in the affected application. Organizations relying on Bytedesk for AI or chat services may face data confidentiality risks and operational disruptions. The medium CVSS score reflects that while the vulnerability is exploitable remotely without authentication, the impact on confidentiality, integrity, and availability is limited to low levels individually. However, combined with other vulnerabilities or misconfigurations, the risk could escalate. Industries with sensitive internal networks or regulatory requirements for data protection are particularly at risk.

Summary

CVE-2026-3788 is a server-side request forgery (SSRF) vulnerability identified in Bytedesk software versions 1.3.0 through 1.3.9. The vulnerability exists in the getModels method within the SpringAIOpenrouterRestService.java source file, part of the SpringAIOpenrouterRestController component. The root cause is insufficient validation or sanitization of the apiUrl parameter, which an attacker can manipulate to coerce the server into making arbitrary HTTP requests. This can allow attackers to access internal resources, bypass firewall restrictions, or retrieve sensitive information from internal networks that are otherwise inaccessible externally. The vulnerability can be exploited remotely without requiring authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and impacts on confidentiality, integrity, and availability at a low level (VC:L, VI:L, VA:L). The vulnerability was publicly disclosed on March 8, 2026, and a patch is available in version 1.4.5.4, identified by patch commit 975e39e4dd527596987559f56c5f9f973f64eff7. While no active exploitation has been reported, the public disclosure increases the risk of future attacks. The vulnerability highlights the importance of proper input validation in server-side components that handle external URLs or API endpoints.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Mar 2026, 09:25 UTC

Technical details

References

Community reviews

Related threats