CVE-2026-3789: Server-Side Request Forgery in Bytedesk
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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
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.
Affected Countries
United States, China, India, Germany, United Kingdom, Japan, South Korea, France, Canada, Australia
CVE-2026-3789: Server-Side Request Forgery in Bytedesk
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-03-08T07:20:34.086Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69ae0bcb2904315ca302ed63
Added to database: 3/8/2026, 11:52:43 PM
Last enriched: 3/16/2026, 9:25:55 AM
Last updated: 4/28/2026, 3:39:00 AM
Views: 153
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.