High SSRF exploit reference

CVE-2026-3789 — Bytedesk SpringAIGiteeRestController SpringAIGiteeRestService.java getModels server-side request forgery

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.

Published Mar 8, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.7%

ahead of 52% of scored CVEs · Oct 14, 2026

Affects

Bytedesk

CVSS base

8.8

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Bytedesk Bytedesk).
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Bytedesk	Bytedesk	< 1.4.5.4	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 4.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
2.1	CVSS 4.0	Low	—	—	cna@vuldb.com via NIST National Vulnerability Database
8.8	CVSS 3.1	High	2.8	5.9	nvd@nist.gov via NIST National Vulnerability Database
6.3	CVSS 3.1	Medium	2.8	3.4	cna@vuldb.com via NIST National Vulnerability Database
6.3	CVSS 3.1	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
6.3	CVSS 3.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP
6.5	CVSS 2.0	Medium	8.0	6.4	cna@vuldb.com via NIST National Vulnerability Database
6.5	CVSS 2.0	Medium	—	—	VulDB via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.70%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.

web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 8.8
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Mar 8, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

github.com/Bytedesk/bytedesk/issues/21
Exploit, Vendor Advisory, issue-tracking, NIST National Vulnerability Database
github.com/Bytedesk/bytedesk/issues/21
Exploit, Vendor Advisory, issue-tracking, NIST National Vulnerability Database
github.com/Bytedesk/bytedesk/issues/21
Exploit, Vendor Advisory, exploit, issue-tracking, NIST National Vulnerability Database
github.com/Bytedesk/bytedesk/commit/975e39e4dd527596987559f56c5f9f973f64eff7
Patch, patch, NIST National Vulnerability Database
github.com/Bytedesk/bytedesk/releases/tag/v1.4.5.4
Release Notes, patch, NIST National Vulnerability Database
github.com/Bytedesk/bytedesk/
Product, product, NIST National Vulnerability Database
vuldb.com/
Third Party Advisory, VDB Entry, third-party-advisory, NIST National Vulnerability Database
vuldb.com/
Third Party Advisory, VDB Entry, vdb-entry, technical-description, NIST National Vulnerability Database
vuldb.com/
Permissions Required, VDB Entry, signature, permissions-required, NIST National Vulnerability Database

Elsewhere on this site

Bytedesk
every CVE for this vendor

SSRF
same class

CWE-918
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-3788 Bytedesk SpringAIOpenrouterRestController SpringAIOpenrouterRestService.java getModels server-side request forgery Mar 8, 2026
High CVE-2026-3748 Bytedesk SVG File UploadRestController.java uploadFile unrestricted upload Mar 8, 2026
High CVE-2026-3749 Bytedesk SVG File UploadRestService.java handleFileUpload unrestricted upload Mar 8, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-3789 is "Bytedesk SpringAIGiteeRestController SpringAIGiteeRestService.java getModels server-side request forgery", rated High. It affects Bytedesk (Bytedesk); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.70% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.