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.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 14, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Sep 30, 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 rangeFix by version rangeDependents
github.com/siyuan-note/siyuan/kernel—
  • every version up to 0.0.0-20260723004839-1a5b3431d5ab: fixed in 0.0.0-20260723004839-1a5b3431d5ab
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 209 total refreshes for this CVE.

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

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 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.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-72811?
CVE-2026-72811 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-72811?
A fix for CVE-2026-72811 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72811 are linked in the Vendor Advisories panel on this page.

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.