VulnerabilityPublished 8 Mar 2026Updated 10 Mar 2026

CVE-2026-3789: 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 38% 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-3789, organizations should immediately upgrade Bytedesk to version 1.4.5.4 or later, which includes the official patch addressing the SSRF vulnerability. Beyond upgrading, administrators should implement strict input validation and sanitization for any parameters that influence server-side HTTP requests, ensuring only trusted URLs or domains are allowed. Network-level controls such as egress filtering and segmentation can limit the server's ability to reach unauthorized internal or external endpoints, reducing SSRF impact. Monitoring and logging of outbound HTTP requests from Bytedesk servers should be enhanced to detect anomalous or unexpected traffic patterns indicative of exploitation attempts. If upgrading is temporarily not possible, consider applying web application firewall (WAF) rules to detect and block suspicious apiUrl parameter values. Regularly review and update security policies around third-party software components and maintain timely patch management practices to reduce exposure to such vulnerabilities.

Description

A vulnerability was detected in Bytedesk up to 1.3.9. Affected is the function getModels of the file source-code/src/main/java/com/bytedesk/ai/springai/providers/gitee/SpringAIGiteeRestService.java of the component SpringAIGiteeRestController. Performing a manipulation of the argument apiUrl results in server-side request forgery. Remote exploitation of the attack is possible. The exploit is now public and may be used. Upgrading to version 1.4.5.4 is able to address this issue. The patch is named 975e39e4dd527596987559f56c5f9f973f64eff7. Upgrading the affected component is advised.

Impact

The SSRF vulnerability in Bytedesk can have significant impacts on organizations running affected versions. Attackers exploiting this flaw can make the server perform unauthorized requests, potentially accessing internal network resources that are otherwise protected by firewalls or network segmentation. This can lead to information disclosure, such as retrieving sensitive internal data or metadata from cloud services. Additionally, SSRF can be leveraged as a pivot point for further attacks within an organization's infrastructure, including scanning internal services, exploiting other vulnerabilities, or causing denial of service by overwhelming internal endpoints. Since the vulnerability requires no authentication or user interaction, it can be exploited by remote attackers, increasing the attack surface. Organizations using Bytedesk in critical environments or with sensitive internal networks are at higher risk. The medium CVSS score reflects a moderate risk, but the availability of a public exploit elevates the urgency of mitigation.

Summary

CVE-2026-3789 is a server-side request forgery vulnerability identified in Bytedesk, specifically affecting versions 1.3.0 through 1.3.9. The vulnerability resides in the getModels function of the SpringAIGiteeRestService.java source file, part of the SpringAIGiteeRestController component. The issue arises from insufficient validation or sanitization of the apiUrl argument, which an attacker can manipulate to coerce the server into making arbitrary HTTP requests. SSRF vulnerabilities enable attackers to bypass network access controls, potentially accessing internal resources, sensitive data, or services not exposed externally. The vulnerability can be exploited remotely without requiring authentication or user interaction, increasing its risk profile. Although no known exploits in the wild have been reported yet, a public exploit has been disclosed, making exploitation more feasible. The vulnerability has a CVSS 4.0 score of 5.3, reflecting medium severity due to its impact on confidentiality, integrity, and availability being limited but still notable. The recommended remediation is to upgrade to Bytedesk version 1.4.5.4, which contains a patch (commit 975e39e4dd527596987559f56c5f9f973f64eff7) that properly validates the apiUrl parameter to prevent SSRF attacks.

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