# CVE-2025-64766: NixOS has hardcoded credentials in Onlyoffice module

> Hardcoded secret in NixOS OnlyOffice module allows attackers with revision IDs to access documents, impacting users with expired access.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-58m4-5wg3-5g5v

## What is CVE-2025-64766?

CVE-2025-64766 is a medium-severity vulnerability in NixOS nixpkgs, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NixOS's Onlyoffice is a software suite that offers online and offline tools for document editing, collaboration, and management. In versions from 22.11 to before 25.05 and versions before Unstable 25.11, a hard-coded secret was used in the NixOS module for the OnlyOffice document server to protect its file cache. An attacker with knowledge of an existing revision ID could use this secret to obtain a document. In practice, an arbitrary revision ID should be hard to obtain. The primary impact is likely the access to known documents from users with expired access. This issue was resolved in NixOS unstable version 25.11 and version 25.05.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-64766 being exploited?

There is no known exploitation of CVE-2025-64766 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64766 is a medium-severity vulnerability in NixOS nixpkgs, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64766 in the wild and no public exploit code.

Affected product: NixOS nixpkgs. 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-64766/ (Markdown: https://insights.sbomify.com/CVE-2025-64766/index.md)
```

## Sources

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

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