Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64766: CWE-798: Use of Hard-coded Credentials in NixOS nixpkgs

0
Medium
VulnerabilityCVE-2025-64766cvecve-2025-64766cwe-798
Published: Mon Nov 17 2025 (11/17/2025, 21:38:10 UTC)
Source: CVE Database V5
Vendor/Project: NixOS
Product: nixpkgs

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.

AI-Powered Analysis

AILast updated: 11/17/2025, 22:00:04 UTC

Technical Analysis

The vulnerability identified as CVE-2025-64766 pertains to the NixOS module for the OnlyOffice document server distributed via nixpkgs. In affected versions (22.11 up to 25.05 and unstable versions before 25.11), a hard-coded secret was embedded in the software to protect the file cache. This secret acts as a static credential that does not change per deployment or user, violating secure credential management best practices (CWE-798). An attacker who can obtain a valid revision ID of a document stored in the OnlyOffice server's cache can leverage this hard-coded secret to retrieve the document contents without proper authorization. The difficulty lies in acquiring a valid revision ID, which is not trivially guessable or publicly exposed under normal circumstances. The vulnerability impacts confidentiality by potentially exposing documents that should no longer be accessible, such as those from users with expired access rights. There is no impact on data integrity or system availability, and exploitation does not require authentication or user interaction, making it remotely exploitable over the network. The issue was addressed by removing or replacing the hard-coded secret in NixOS unstable 25.11 and stable 25.05 releases. No public exploits have been reported, but the presence of hard-coded credentials represents a significant security weakness that could be leveraged in targeted attacks.

Potential Impact

For European organizations, the primary impact of CVE-2025-64766 is unauthorized disclosure of sensitive documents managed via OnlyOffice on NixOS systems. This could lead to leakage of confidential business information, intellectual property, or personal data, especially if revision IDs are exposed through other means such as insider threats, misconfigurations, or indirect information leaks. The vulnerability does not affect data integrity or system availability, limiting the scope of damage. However, the ease of exploitation without authentication and user interaction increases the risk profile, particularly for organizations with publicly accessible OnlyOffice deployments or weak access controls. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, may face compliance risks under GDPR if sensitive data is exposed. The lack of known exploits suggests limited active targeting currently, but the vulnerability should be treated proactively to prevent future abuse.

Mitigation Recommendations

European organizations should immediately assess their NixOS deployments to identify if affected versions of nixpkgs with OnlyOffice are in use. The primary mitigation is to upgrade to NixOS stable version 25.05 or unstable 25.11 and later, where the hard-coded secret has been removed. If upgrading is not immediately feasible, organizations should implement network-level access controls to restrict access to OnlyOffice servers, ensuring they are not exposed to untrusted networks. Monitoring and logging access to OnlyOffice document caches can help detect suspicious activities involving revision IDs. Additionally, organizations should audit their document management policies to minimize exposure of revision IDs and ensure that expired user access is properly revoked and enforced. Employing application-layer security measures such as web application firewalls (WAFs) and intrusion detection systems (IDS) can provide additional layers of defense. Finally, educating administrators and users about the risks of sharing document revision links can reduce the likelihood of accidental exposure.

Need more detailed analysis?Get Pro

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/17/2025, 10:00:04 PM

Last updated: 11/22/2025, 1:34:43 PM

Views: 45

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats