How many CVEs have patched checkBlockPublishAccessInBox?

2 published CVEs changed checkBlockPublishAccessInBox in siyuan-note/siyuan, in 1 distinct patches totalling 18 changed lines, between 2026 and 2026.

What is the latest CVE that changed checkBlockPublishAccessInBox?

CVE-2026-72805 (SiYuan before v3.7.4 Information Disclosure via Block Endpoints), published 2026-08-12, changed lines 874 to 878 of kernel/api/block.go.

How does checkBlockPublishAccessInBox compare to the rest of siyuan-note/siyuan?

siyuan-note/siyuan has 67 CVEs with a located fix in total; 2 of them changed checkBlockPublishAccessInBox.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

siyuan-note/siyuan

Function

checkBlockPublishAccessInBox

Name: checkBlockPublishAccessInBox in siyuan-note/siyuan: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

kernel/api/block.go

Last patched August 12, 2026

2

CVEs

That changed this function

1

Distinct patches

Backports counted once

18

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

checkBlockPublishAccessInBox in siyuan-note/siyuan was changed by 2 published CVE fixes in 2026, in 1 distinct patches that added or removed 18 lines in total.

siyuan-note/siyuan has 67 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed checkBlockPublishAccessInBox, newest first, with the lines each fix touched.

SiYuan before v3.7.4 Information Disclosure via Block Endpoints
CVE-2026-72805 · lines 874–878 · +4 −5
Medium · CVSS 6.9
EPSS 0.3%2026-08-12
SiYuan before v3.7.4 Information Disclosure via Unfiltered API
CVE-2026-72800 · lines 874–878 · +4 −5
Medium · CVSS 6.9
EPSS 0.3%2026-08-12

Get an alert when the next CVE fix lands in siyuan-note/siyuan, with the patched functions.

Monitor siyuan CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in siyuan-note/siyuan changed by the most CVE fixes.

IsSensitivePath8 CVEs · kernel/util/path.go ServeAPI6 CVEs · kernel/api/router.go getBlockInfo4 CVEs · kernel/api/block.go getDocInfo4 CVEs · kernel/api/block.go fullTextSearchBlock3 CVEs · kernel/api/search.go serveExport3 CVEs · kernel/server/serve.go

All patched functions in siyuan-note/siyuan

Frequently asked questions

Common questions about CVE fixes to checkBlockPublishAccessInBox.

How many CVEs have patched checkBlockPublishAccessInBox?: 2 published CVEs changed checkBlockPublishAccessInBox in siyuan-note/siyuan, in 1 distinct patches totalling 18 changed lines, between 2026 and 2026.
What is the latest CVE that changed checkBlockPublishAccessInBox?: CVE-2026-72805 (SiYuan before v3.7.4 Information Disclosure via Block Endpoints), published 2026-08-12, changed lines 874 to 878 of kernel/api/block.go.
How does checkBlockPublishAccessInBox compare to the rest of siyuan-note/siyuan?: siyuan-note/siyuan has 67 CVEs with a located fix in total; 2 of them changed checkBlockPublishAccessInBox.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track siyuan-note/siyuan CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing