CVE-2025-64766: CWE-798: Use of Hard-coded Credentials in NixOS nixpkgs
CVE-2025-64766 is a medium-severity vulnerability in NixOS nixpkgs affecting the OnlyOffice document server module. It involves the use of a hard-coded secret to protect the file cache, allowing an attacker who knows a document's revision ID to access that document. The vulnerability affects versions from 22. 11 up to but not including 25. 05, and unstable versions before 25. 11. Exploitation does not require authentication or user interaction but does require knowledge of a valid revision ID, which is considered difficult to obtain. The primary impact is unauthorized read access to documents that users may no longer have permission to access, potentially exposing sensitive information. The issue was fixed in NixOS versions 25. 05 and unstable 25.
AI Analysis
Technical Summary
CVE-2025-64766 is a vulnerability classified under CWE-798, indicating the use of hard-coded credentials within the NixOS nixpkgs distribution, specifically in the OnlyOffice document server module. OnlyOffice is a widely used suite for document editing and collaboration, integrated into NixOS as a module. In affected versions (22.11 through before 25.05, and unstable versions before 25.11), a hard-coded secret was embedded to protect the file cache. This secret acts as a static key to control access to cached document files. An attacker who can obtain a valid revision ID of a document can leverage this hard-coded secret to bypass intended access controls and retrieve the document from the cache. Although the revision ID is not trivial to acquire, if obtained, it allows unauthorized read-only access to documents, including those for which user access rights may have expired. The vulnerability does not allow modification or deletion of documents, nor does it affect system availability. The flaw was addressed in NixOS stable version 25.05 and unstable 25.11 by removing or replacing the hard-coded secret with a more secure mechanism. The CVSS v3.1 base score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges or user interaction required, and limited confidentiality impact. No known exploits have been reported in the wild to date. This vulnerability highlights the risks of embedding static secrets in software modules, especially in collaborative environments where document confidentiality is critical.
Potential Impact
For European organizations, the primary impact of this vulnerability is unauthorized disclosure of sensitive documents stored or cached via the OnlyOffice document server on NixOS systems. Organizations relying on OnlyOffice for document collaboration and management may face confidentiality breaches if an attacker obtains revision IDs, potentially exposing intellectual property, personal data, or confidential business information. Although exploitation requires knowledge of revision IDs, insider threats or attackers with partial system access could leverage this vulnerability to access documents beyond their authorization. The vulnerability does not affect document integrity or availability, limiting the scope to confidentiality concerns. Given the increasing regulatory focus on data protection in Europe, such as GDPR, unauthorized disclosure could lead to compliance violations and reputational damage. Organizations using affected NixOS versions in critical sectors like finance, healthcare, or government should consider this a significant risk vector. The lack of known exploits reduces immediate urgency but does not eliminate the threat, especially as attackers may develop techniques to discover revision IDs over time.
Mitigation Recommendations
European organizations should immediately verify if their NixOS deployments include the OnlyOffice document server module within the affected version ranges (>=22.11 and <25.05, or unstable versions <25.11). The primary mitigation is to upgrade NixOS to version 25.05 or later, or unstable 25.11 or later, where the hard-coded secret has been removed or replaced. If upgrading is not immediately feasible, organizations should restrict network access to the OnlyOffice document server to trusted users and networks, minimizing exposure to external attackers. Implement strict access controls and monitoring to detect unusual access patterns that might indicate attempts to enumerate or guess revision IDs. Consider auditing document revision ID generation and distribution processes to reduce leakage risks. Additionally, review and rotate any secrets or tokens associated with OnlyOffice caches if possible. Employ network-level protections such as firewalls and VPNs to limit access to the document server. Finally, educate users about the sensitivity of document revision identifiers and encourage secure handling practices to prevent inadvertent disclosure.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Norway, Denmark, Switzerland, Belgium
CVE-2025-64766: CWE-798: Use of Hard-coded Credentials in NixOS nixpkgs
Description
CVE-2025-64766 is a medium-severity vulnerability in NixOS nixpkgs affecting the OnlyOffice document server module. It involves the use of a hard-coded secret to protect the file cache, allowing an attacker who knows a document's revision ID to access that document. The vulnerability affects versions from 22. 11 up to but not including 25. 05, and unstable versions before 25. 11. Exploitation does not require authentication or user interaction but does require knowledge of a valid revision ID, which is considered difficult to obtain. The primary impact is unauthorized read access to documents that users may no longer have permission to access, potentially exposing sensitive information. The issue was fixed in NixOS versions 25. 05 and unstable 25.
AI-Powered Analysis
Technical Analysis
CVE-2025-64766 is a vulnerability classified under CWE-798, indicating the use of hard-coded credentials within the NixOS nixpkgs distribution, specifically in the OnlyOffice document server module. OnlyOffice is a widely used suite for document editing and collaboration, integrated into NixOS as a module. In affected versions (22.11 through before 25.05, and unstable versions before 25.11), a hard-coded secret was embedded to protect the file cache. This secret acts as a static key to control access to cached document files. An attacker who can obtain a valid revision ID of a document can leverage this hard-coded secret to bypass intended access controls and retrieve the document from the cache. Although the revision ID is not trivial to acquire, if obtained, it allows unauthorized read-only access to documents, including those for which user access rights may have expired. The vulnerability does not allow modification or deletion of documents, nor does it affect system availability. The flaw was addressed in NixOS stable version 25.05 and unstable 25.11 by removing or replacing the hard-coded secret with a more secure mechanism. The CVSS v3.1 base score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges or user interaction required, and limited confidentiality impact. No known exploits have been reported in the wild to date. This vulnerability highlights the risks of embedding static secrets in software modules, especially in collaborative environments where document confidentiality is critical.
Potential Impact
For European organizations, the primary impact of this vulnerability is unauthorized disclosure of sensitive documents stored or cached via the OnlyOffice document server on NixOS systems. Organizations relying on OnlyOffice for document collaboration and management may face confidentiality breaches if an attacker obtains revision IDs, potentially exposing intellectual property, personal data, or confidential business information. Although exploitation requires knowledge of revision IDs, insider threats or attackers with partial system access could leverage this vulnerability to access documents beyond their authorization. The vulnerability does not affect document integrity or availability, limiting the scope to confidentiality concerns. Given the increasing regulatory focus on data protection in Europe, such as GDPR, unauthorized disclosure could lead to compliance violations and reputational damage. Organizations using affected NixOS versions in critical sectors like finance, healthcare, or government should consider this a significant risk vector. The lack of known exploits reduces immediate urgency but does not eliminate the threat, especially as attackers may develop techniques to discover revision IDs over time.
Mitigation Recommendations
European organizations should immediately verify if their NixOS deployments include the OnlyOffice document server module within the affected version ranges (>=22.11 and <25.05, or unstable versions <25.11). The primary mitigation is to upgrade NixOS to version 25.05 or later, or unstable 25.11 or later, where the hard-coded secret has been removed or replaced. If upgrading is not immediately feasible, organizations should restrict network access to the OnlyOffice document server to trusted users and networks, minimizing exposure to external attackers. Implement strict access controls and monitoring to detect unusual access patterns that might indicate attempts to enumerate or guess revision IDs. Consider auditing document revision ID generation and distribution processes to reduce leakage risks. Additionally, review and rotate any secrets or tokens associated with OnlyOffice caches if possible. Employ network-level protections such as firewalls and VPNs to limit access to the document server. Finally, educate users about the sensitivity of document revision identifiers and encourage secure handling practices to prevent inadvertent disclosure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-11-10T22:29:34.877Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 691b98f601a6b16707f49d49
Added to database: 11/17/2025, 9:51:50 PM
Last enriched: 11/24/2025, 10:16:37 PM
Last updated: 1/7/2026, 8:57:52 AM
Views: 103
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-15158: CWE-434 Unrestricted Upload of File with Dangerous Type in eastsidecode WP Enable WebP
HighCVE-2025-15018: CWE-639 Authorization Bypass Through User-Controlled Key in djanym Optional Email
CriticalCVE-2025-15000: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in tfrommen Page Keys
MediumCVE-2025-14999: CWE-352 Cross-Site Request Forgery (CSRF) in kentothemes Latest Tabs
MediumCVE-2025-13531: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in hayyatapps Stylish Order Form Builder
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.