# CVE-2025-68948: SiYuan: Information Disclosure and Authentication Bypass via Hardcoded Session Secret

> Attackers can decrypt session cookies using a hardcoded secret to steal authentication codes and take over user accounts in SiYuan.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-f7ph-rc3w-qp28

## What is CVE-2025-68948?

CVE-2025-68948 is a medium-severity vulnerability in B3log Siyuan, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan is self-hosted, open source personal knowledge management software. In versions 3.5.1 and prior, the SiYuan Note application utilizes a hardcoded cryptographic secret for its session store. This unsafe practice renders the session encryption ineffective. Since the sensitive AccessAuthCode is stored within the session cookie, an attacker who intercepts or obtains a user's encrypted session cookie (e.g., via session hijacking) can locally decrypt it using the public key. Once decrypted, the attacker can retrieve the AccessAuthCode in plain text and use it to authenticate or take over the session.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-68948?

It affects 1 product.


Products: B3log Siyuan.

## How do I fix CVE-2025-68948?

No fix has been published for CVE-2025-68948 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-68948 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68948 exists.

## Other vulnerabilities in B3log Siyuan

- [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9)
- [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8)
- [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8)
- [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8)
- [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68948 and fix it if it is affected.

What it is: CVE-2025-68948 is a medium-severity vulnerability in B3log Siyuan, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68948 exists.

Affected product: B3log Siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68948/ (Markdown: https://insights.sbomify.com/CVE-2025-68948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68948
- OSV: https://osv.dev/vulnerability/CVE-2025-68948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68948/
Summaries are generated and may contain mistakes; the official description above is the record.