Skip to content
Applications

CVE-2026-73047

8.6
High
EPSS 0.13%Patch availableAug 16, 2026

Local SSTI in SiYuan <=3.7.3 exposes env vars and enables DNS lookups.

common questions

Is CVE-2026-73047 being exploited?

Not confirmed. CVE-2026-73047 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-73047?

CVE-2026-73047 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73047?

Yes. A fix has been recorded for CVE-2026-73047. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73047 affect?

CVE-2026-73047 affects SiYuan <= 3.7.3, attribute-view Template calculation feature, hosts running SiYuan bound to 127.0.0.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73047?

Upgrade to SiYuan v3.7.4, restrict local access and rotate any exposed secrets.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
SiYuan <= 3.7.3attribute-view Template calculation featurehosts running SiYuan bound to 127.0.0.1
impact

Local, unauthenticated template injection allows reading process environment variables (credentials/data) and performing DNS lookups from the host.

action required

Patch when possible

affected versions
siyuan-note siyuan
  • affected< 3.7.4
vendor says fixed in3.7.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free