The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In gokey versions <0.2.0, a flaw in the seed decryption logic resulted in passwords incorrectly being     derived solely from the initial vector and the AES-GCM authentication tag of the key seed. This issue has     been fixed in gokey version 0.2.0. This is a breaking change. The fix has invalidated any     passwords/secrets that were derived from the seed file (using the -s option). Even if the input seed file     stays the same, version 0.2.0 gokey will generate different secrets. Impact This vulnerability impacts     generated keys/secrets using a seed file as an entropy input (using the -s option). Keys/secrets generated     just from the master password (without the -s option) are not impacted. The confidentiality of the seed     itself is also not impacted (it is not required to regenerate the seed itself). Specific impact includes:
    * keys/secrets generated from a seed file may have lower entropy: it was expected that the whole seed     would be used to generate keys (240 bytes of entropy input), where in vulnerable versions only 28 bytes     was used * a malicious entity could have recovered all passwords, generated from a particular seed, having     only the seed file in possession without the knowledge of the seed master password Patches The code logic     bug has been fixed in gokey version 0.2.0 and above. Due to the deterministic nature of gokey, fixed     versions will produce different passwords/secrets using seed files, as all seed entropy will be used now.
    System secret rotation guidance It is advised for users to regenerate passwords/secrets using the patched     version of gokey (0.2.0 and above), and provision/rotate these secrets into respective systems in place of     the old secret. A specific rotation procedure is system-dependent, but most common patterns are described     below. Systems that do not require the old password/secret for rotation Such systems usually have a     Forgot password facility or a similar facility allowing users to rotate their password/secrets by     sending a unique magic link to the user's email or phone. In such cases users are advised to use this     facility and input the newly generated password secret, when prompted by the system. Systems that require     the old password/secret for rotation Such systems usually have a modal password rotation window usually in     the user settings section requiring the user to input the old and the new password sometimes with a     confirmation. To generate/recover the old password in such cases users are advised to: * temporarily     download gokey version 0.1.3 https://github.com/cloudflare/gokey/releases/tag/v0.1.3 for their respective     operating system to recover the old password * use gokey version 0.2.0 or above to generate the new     password * populate the system provided password rotation form Systems that allow multiple credentials for     the same account to be provisioned Such systems usually require a secret or a cryptographic key as a     credential for access, but allow several credentials at the same time. One example is SSH: a particular     user may have several authorized public keys configured on the SSH server for access. For such systems     users are advised to: * generate a new secret/key/credential using gokey version 0.2.0 or above *     provision the new secret/key/credential in addition to the existing credential on the system * verify that     the access or required system operation is still possible with the new secret/key/credential * revoke     authorization for the existing/old credential from the system Credit This vulnerability was found by Tho     Cusnir ( @mister_mime https://hackerone.com/mister_mime ) and responsibly disclosed through Cloudflare's     bug bounty program. (CVE-2025-13353)

Note that Nessus relies on the presence of the package as reported by the vendor.

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2025-13353

high Nessus Plugin ID 277090

Version 1.10

Version 1.9

Version 1.7

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.10 Jul 27, 2026, 10:22 AM Detection (updated detection logic) Plugin Feed: 202607271022
Version 1.9 Jul 4, 2026, 4:43 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607041643
Version 1.7 Apr 29, 2026, 12:50 PM CVSS metrics ("CVSSv2 score" set to 4.0) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N") Detection (updated detection logic) Plugin metadata Plugin Feed: 202604291250
Version 1.6 Feb 27, 2026, 1:16 PM CVSS metrics ("CVSSv2 score" set to 4.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:N/A:N") Plugin Feed: 202602271316
Version 1.5 Feb 2, 2026, 9:31 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202602022131
Version 1.4 Jan 21, 2026, 10:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601211050
Version 1.3 Jan 3, 2026, 12:01 AM CVSS metrics ("CVSSv3 score" set to 5.5) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N") Detection (updated detection logic) Plugin metadata Plugin Feed: 202601030001
Version 1.2 Dec 4, 2025, 7:43 PM CVSS metrics ("CVSSv2 score" set to 4.0) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:N/AC:L/Au:S/C:P/I:N/A:N") CVSS metrics ("CVSSv3 score" set to 5.3) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N") CVSSv2 severity (based on CVE-2025-13353, severity decreased from "High" to "Medium") CVSSv3 severity (based on None, severity decreased from "High" to "Medium") Detection (updated detection logic) Plugin metadata Plugin Feed: 202512041943
Version 1.1 Dec 3, 2025, 8:52 PM New Plugin Feed: 202512032052