SiYuan versions before v3.8.1 contain a server-side request forgery vulnerability in the http_request and web_fetch agent tools that perform DNS resolution only at guard time without validating the connect-time resolution. Attackers can use DNS rebinding to answer the guard resolution with a public IP and the connect resolution with a private or metadata IP, bypassing the SSRF defense to access cloud instance metadata and internal services.
CVE-2026-82234
Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 8.2; 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
- 8.2
- EG Score
- 8.2(high)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity82% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026SiYuan before v3.8.1 SSRF via DNS-Rebinding TOCTOU | Advisories | VulnCheck
https://www.vulncheck.com/advisories/siyuan-before-3.8.1-ssrf-via-dns-rebinding-toctouSiYuan Agent Tools SSRF via DNS-Rebinding TOCTOU (Bypass of CheckHostSSRF) · Advisory · siyuan-note/siyuan · GitHub
https://github.com/siyuan-note/siyuan/security/advisories/GHSA-x8gv-g2g3-65fjVendor Advisories for CVE-2026-82234(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 9× in last 7d / 9× 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-30 01:22 UTCEPSS rescore
- 2026-08-29 21:07 UTCGHSA enrichment
- 2026-08-29 08:49 UTCGHSA enrichment
- 2026-08-28 20:30 UTCGHSA enrichment
- 2026-08-28 18:57 UTCEG score recompute
- 2026-08-28 18:57 UTCGHSA enrichment
- 2026-08-28 12:23 UTCEG score recompute
- 2026-08-28 11:24 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p91CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-82234?
When was CVE-2026-82234 disclosed?
Is CVE-2026-82234 actively exploited?
What is the CVSS score of CVE-2026-82234?
How do I remediate CVE-2026-82234?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82234
Is Your Infrastructure Affected by CVE-2026-82234?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.