VulnerabilityPublished 17 Nov 2025

CVE-2025-64766: NixOS nixpkgs · Use of Hard-coded Credentials

Affects NixOS nixpkgsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 25.11 or 25.05 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.11, 25.05

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nixos/nixpkgs to 25.11 or 25.05.

Affected software

Product	Affected	Fixed in
GitHubnixos/nixpkgs`pkg:github/nixos/nixpkgs`Other threats	Affected <25.05 <25.11	Fixed in 25.05 25.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

CWE-798Use of Hard-coded Credentials (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product contains hard-coded credentials, such as a password or cryptographic key.
Architecture and Design
For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320).
Architecture and Design
For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design
If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
OWASP Cheat Sheets
Key Management (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.4 (opens in a new tab)
V6.4.1 (opens in a new tab)
V3.5.2 (opens in a new tab)
Attack patterns
Read Sensitive Constants Within an Executable (opens in a new tab)
Try Common or Default Usernames and Passwords (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Nov 2025, 22:16 UTC

WeaknessesCWE-798

Technical details

References

Community reviews

Related threats