vciy

CVE-2026-72802

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

SiYuan before v3.7.4 Information Disclosure via resolveAssetPath

CVE-2026-728023 of 4 sources documented this
13

rank 13 = 0 + 13 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00237  ·  without this subject the record ranks 13

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.3, from NVD  ·  without this subject the record ranks 0

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 13

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 13

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2,840over the next 30 days, if this record is yours
Movementnot heldno dated series to read a change from
Basisassumeda published average, not your estate

$2,840 = $4.99M incident cost x 0.24048551839932833 exposure x 0.00237 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00237EPSSNOT IN KEVas of 2026-09-20
Severity6.9 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementone observationreceipt
SINGLE READINGOne observation held. There is no shape yet. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
VulnCheck6.9 MEDIUMreceipt
NVD5.3 MEDIUMreceipt
Scoring standard
VulnCheckCVSS v4.0receipt
NVDCVSS v3.1receipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running siyuan-note siyuan? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexity · no attack requirementsreceipt
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-639 Authorization Bypass Through User-Controlled Keyreceipt
Published consequencesCWE-639: Access Control: Bypass Protection Mechanism; Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in3.7.4receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA6.9 MEDIUMreceipt
CVSS, NVD5.3 MEDIUMreceipt
Exploit probability0.00237 · top 85% of all CVEsreceipt
Assigned byVulnCheckreceipt
Recorded changes1 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productsiyuan-note siyuanreceipt
Fixed in3.7.4receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

SiYuan versions before v3.7.4 contain an information disclosure vulnerability in the resolveAssetPath endpoint that returns absolute filesystem paths unmodified to CheckAuth-only requests. Attackers can harvest relative asset paths from published documents and submit them to resolveAssetPath to obtain the server's absolute workspace path, disclosing the operating-system username and installation layout. receipt

NVD's analysis a second authority

severity
5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
weakness
CWE-639
also scored by
[email protected] 6.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

The CNA scored it 6.9 and NVD 5.3. Both are shown because both were published; we do not pick one.

check it yourself github.com vulncheck.com receipt

Movement

Only one observation of this value is held, so there is no movement to show yet.

The full biography

Published2026-08-12Index as of2026-08-13

The record had been public for 1 day when this index was last written.

Published 2026-08-12 receipt · Index as of 2026-08-13 derived

Siblings and hubs

Records related to this one

Its defect family

siyuan-note siyuan

Of the 3 records in this family that state one, this holds the highest EPSS percentile: 0.14511.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2026-72802.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.