SiYuan before v3.7.4 contains a server-side request forgery (SSRF) vulnerability in the isPrivateIP function in kernel/util/net.go, used by SSRFSafeDialer to enforce SSRF protection in SafeMode. The function only checks for loopback, link-local unicast, private, and unspecified addresses and does not recognize IPv6 transition addresses (NAT64 64:ff9b::/96, 6to4 2002::/16, Teredo 2001::/32) that embed private IPv4 destinations. When SafeMode is enabled, an authenticated attacker can bypass the SSRF guard via the network forward proxy, WebSocket proxy, or SSE proxy endpoints by supplying a URL whose hostname resolves to such a transition address, reaching internal services and cloud metadata endpoints (e.g., 169.254.169.254). Because the forward proxy returns the full response body, this is a full-read SSRF that can be used to steal instance credentials, reach internal services, and port-scan internal infrastructure.
CVE-2026-74905
Score 7.1 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 7.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(high)
- EG Risk
- 48(Track)EG Risk 48/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026SiYuan before v3.7.4 SSRF via IPv6 Transition Address Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-ssrf-via-ipv6-transition-address-bypassSSRF via IPv6 Transition Address Bypass of SSRFSafeDialer Guard in SafeMode · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-qq8m-8p8v-x4xgVendor Advisories for CVE-2026-74905(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 03:17 UTCEG score recompute
- 2026-08-21 03:16 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:17 UTCGHSA enrichment
- 2026-08-20 03:22 UTCEG score recompute
- 2026-08-20 03:22 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:25 UTCEG score recompute
- 2026-08-19 15:25 UTCGHSA enrichment
- 2026-08-19 14:27 UTCEG score recompute
- 2026-08-19 14:27 UTCGHSA enrichment
- 2026-08-19 12:29 UTCGHSA enrichment
- 2026-08-19 00:34 UTCGHSA enrichment
- 2026-08-18 12:35 UTCEG score recompute
- 2026-08-18 12:35 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-74905?
When was CVE-2026-74905 disclosed?
Is CVE-2026-74905 actively exploited?
What is the CVSS score of CVE-2026-74905?
How do I remediate CVE-2026-74905?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74905
Is Your Infrastructure Affected by CVE-2026-74905?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.