CVE-2026-72811

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-14. a secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

SiYuan versions <= v3.7.2 contain a SQL injection vulnerability in the backlink/mention search query (kernel/model/backlink.go), which concatenates stored block metadata (title, name, alias, anchor text) and the client-supplied keyword into a SQL MATCH/search statement while escaping only the double-quote character and not the single quote. A single quote in the client keyword (first-order, reachable by an anonymous or RoleReader user on the publish surface) or in stored document metadata (second-order) breaks out of the string literal. Because the query runs on the main read-write siyuan.db handle via a statement-stacking-capable driver, an attacker can execute arbitrary SQL, enabling cross-notebook read and write. Fixed in v3.7.4.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
60(Track)
EG Risk 60/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 computed
Severity100% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 14, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

SiYuan before v3.7.4 SQL Injection via backlink search | Advisories | VulnCheck

https://www.vulncheck.com/advisories/siyuan-before-sql-injection-via-backlink-search
github Patch Available🟡 PoC Available

SQL injection in backlink/mention search via unescaped stored and client input (publish mode): first-order (client keyword) and second-order (stored document title) breakout on read-write handle · Advisory · siyuan-note/siyuan · GitHub

https://github.com/siyuan-note/siyuan/security/advisories/GHSA-q2vg-7qgx-x5fc

Vendor Advisories for CVE-2026-72811(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/siyuan-note/siyuan/kernel—0.0.0-20260723004839-1a5b3431d5ab—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 132× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-18 22:47 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 22:16 UTCEG score recompute
  4. 2026-09-16 23:50 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 10:27 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 05:59 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-13 17:16 UTCEG score recompute
  11. 2026-09-13 13:18 UTCEG score recompute
  12. 2026-09-12 17:28 UTCEG score recompute
  13. 2026-09-12 15:02 UTCEPSS rescore
  14. 2026-09-11 17:41 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:44 UTCEG score recompute
  17. 2026-09-10 09:44 UTCEG score recompute
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-09 04:50 UTCEG score recompute
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 16:26 UTCEG score recompute
  22. 2026-09-06 16:29 UTCEG score recompute
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-05 16:39 UTCEG score recompute
  25. 2026-09-04 14:13 UTCEG score recompute
Show 75 more
  1. 2026-09-03 20:09 UTCGHSA enrichment
  2. 2026-09-03 16:09 UTCGHSA enrichment
  3. 2026-09-03 11:13 UTCGHSA enrichment
  4. 2026-09-03 06:57 UTCGHSA enrichment
  5. 2026-09-03 02:56 UTCGHSA enrichment
  6. 2026-09-02 22:58 UTCEG score recompute
  7. 2026-09-02 22:58 UTCGHSA enrichment
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-02 13:04 UTCGHSA enrichment
  10. 2026-09-02 08:43 UTCGHSA enrichment
  11. 2026-09-02 04:44 UTCGHSA enrichment
  12. 2026-09-02 00:29 UTCGHSA enrichment
  13. 2026-09-01 20:17 UTCGHSA enrichment
  14. 2026-09-01 15:13 UTCEG score recompute
  15. 2026-09-01 15:13 UTCGHSA enrichment
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-09-01 11:14 UTCGHSA enrichment
  18. 2026-09-01 06:10 UTCEG score recompute
  19. 2026-09-01 06:10 UTCGHSA enrichment
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 01:52 UTCGHSA enrichment
  23. 2026-08-31 21:30 UTCGHSA enrichment
  24. 2026-08-31 11:56 UTCGHSA enrichment
  25. 2026-08-31 07:58 UTCGHSA enrichment
  26. 2026-08-31 04:01 UTCGHSA enrichment
  27. 2026-08-31 00:03 UTCGHSA enrichment
  28. 2026-08-30 20:06 UTCEG score recompute
  29. 2026-08-30 20:05 UTCGHSA enrichment
  30. 2026-08-30 19:18 UTCEPSS rescore
  31. 2026-08-30 19:17 UTCEPSS rescore
  32. 2026-08-30 16:08 UTCGHSA enrichment
  33. 2026-08-30 12:10 UTCGHSA enrichment
  34. 2026-08-30 08:13 UTCGHSA enrichment
  35. 2026-08-30 04:15 UTCEG score recompute
  36. 2026-08-30 04:15 UTCGHSA enrichment
  37. 2026-08-30 01:22 UTCEPSS rescore
  38. 2026-08-30 00:17 UTCGHSA enrichment
  39. 2026-08-29 20:19 UTCGHSA enrichment
  40. 2026-08-29 15:03 UTCGHSA enrichment
  41. 2026-08-29 11:04 UTCGHSA enrichment
  42. 2026-08-29 06:57 UTCEG score recompute
  43. 2026-08-29 06:57 UTCGHSA enrichment
  44. 2026-08-28 21:42 UTCEPSS rescore
  45. 2026-08-28 12:28 UTCGHSA enrichment
  46. 2026-08-28 08:19 UTCGHSA enrichment
  47. 2026-08-28 03:37 UTCGHSA enrichment
  48. 2026-08-27 23:40 UTCGHSA enrichment
  49. 2026-08-27 19:31 UTCEG score recompute
  50. 2026-08-27 19:31 UTCGHSA enrichment
  51. 2026-08-27 14:25 UTCEPSS rescore
  52. 2026-08-27 13:05 UTCGHSA enrichment
  53. 2026-08-27 09:07 UTCGHSA enrichment
  54. 2026-08-27 05:07 UTCGHSA enrichment
  55. 2026-08-27 01:09 UTCGHSA enrichment
  56. 2026-08-26 21:11 UTCGHSA enrichment
  57. 2026-08-26 17:14 UTCEG score recompute
  58. 2026-08-26 17:14 UTCGHSA enrichment
  59. 2026-08-26 14:47 UTCEPSS rescore
  60. 2026-08-26 13:53 UTCGHSA enrichment
  61. 2026-08-26 09:54 UTCGHSA enrichment
  62. 2026-08-26 05:42 UTCGHSA enrichment
  63. 2026-08-26 01:44 UTCGHSA enrichment
  64. 2026-08-25 21:46 UTCGHSA enrichment
  65. 2026-08-25 17:28 UTCEG score recompute
  66. 2026-08-25 17:28 UTCGHSA enrichment
  67. 2026-08-25 13:49 UTCEPSS rescore
  68. 2026-08-25 13:27 UTCGHSA enrichment
  69. 2026-08-25 09:29 UTCGHSA enrichment
  70. 2026-08-25 05:31 UTCGHSA enrichment
  71. 2026-08-25 01:33 UTCGHSA enrichment
  72. 2026-08-24 21:36 UTCGHSA enrichment
  73. 2026-08-24 17:24 UTCEG score recompute
  74. 2026-08-24 17:23 UTCGHSA enrichment
  75. 2026-08-24 13:25 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72811?
CVE-2026-72811 is a critical vulnerability published on August 14, 2026. SiYuan versions <= v3.7.2 contain a SQL injection vulnerability in the backlink/mention search query (kernel/model/backlink.go), which concatenates stored block metadata (title, name, alias, anchor text) and the client-supplied keyword into a SQL MATCH/search statement while escaping only the…
When was CVE-2026-72811 disclosed?
CVE-2026-72811 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72811 actively exploited?
CVE-2026-72811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-72811?
CVE-2026-72811 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-72811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72811

Explore →

Is Your Infrastructure Affected by CVE-2026-72811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs