# CVE-2025-13353: gokey allows secret recovery from a seed file without the master password - **Severity:** High 7.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`) - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 2 Dec 2025 - **Updated:** 2 Dec 2025 - **Also known as:** DEBIAN-CVE-2025-13353, GHSA-69jw-4jj8-fcxm, GO-2025-4174, UBUNTU-CVE-2025-13353 ## What is CVE-2025-13353? CVE-2025-13353 is a high-severity vulnerability in Cloudflare gokey, published on 2 Dec 2025. ### Official description 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 Théo Cusnir ( @mister_mime https://hackerone.com/mister_mime ) and responsibly disclosed through Cloudflare's bug bounty program. Weakness: CWE-330 (Use of Insufficiently Random Values) ## Which versions are affected by CVE-2025-13353? 3 open source packages ship an affected version, including github.com/cloudflare/gokey. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/cloudflare/gokey` | Go | All versions | 0.2.0 | | `github.com/cloudflare/gokey` | Go | All versions | 0.2.0 | | `github.com/cloudflare/gokey` | Go | All versions | 0.2.0 | Products: Cloudflare Gokey. ## How do I fix CVE-2025-13353? Upgrade github.com/cloudflare/gokey to 0.2.0 or later. ## Is CVE-2025-13353 being exploited? There is no known exploitation of CVE-2025-13353 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-13353 and fix it if it is affected. What it is: CVE-2025-13353 is a high-severity vulnerability in Cloudflare gokey, published on 2 Dec 2025. Exploitation: There is no known exploitation of CVE-2025-13353 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0 - github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0 - github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0 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-13353/ (Markdown: https://insights.sbomify.com/CVE-2025-13353/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13353 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13353 - OSV: https://osv.dev/vulnerability/CVE-2025-13353 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-13353/ Summaries are generated and may contain mistakes; the official description above is the record.