{"answers":{"affected":"3 open source packages ship an affected version, including github.com/cloudflare/gokey. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-13353 in the wild and no public exploit code.","fix":"Upgrade github.com/cloudflare/gokey to 0.2.0 or later.","what":"CVE-2025-13353 is a high-severity vulnerability in Cloudflare gokey, published on 2 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2025-13353 and fix it if it is affected.\n\nWhat it is: CVE-2025-13353 is a high-severity vulnerability in Cloudflare gokey, published on 2 Dec 2025. \nExploitation: There is no known exploitation of CVE-2025-13353 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0\n- github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0\n- github.com/cloudflare/gokey (Go): affected all versions; fixed in 0.2.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-13353/ (Markdown: https://insights.sbomify.com/CVE-2025-13353/index.md)","id":"CVE-2025-13353","markdown":"https://insights.sbomify.com/CVE-2025-13353/index.md","name":"CVE-2025-13353","record":{"aliases":["DEBIAN-CVE-2025-13353","GHSA-69jw-4jj8-fcxm","GO-2025-4174","UBUNTU-CVE-2025-13353"],"analysis":null,"analysis_generated_by":null,"assigner":"cloudflare","cpe":[{"product":"gokey","vendor":"cloudflare"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"In gokey versions \u003c0.2.0,\n a flaw in the seed decryption logic resulted in passwords incorrectly \nbeing derived solely from the initial vector and the AES-GCM \nauthentication tag of the key seed.\n\nThis 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.\n\nImpact\nThis 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\n option) are not impacted. The confidentiality of the seed itself is \nalso not impacted (it is not required to regenerate the seed itself). \nSpecific impact includes:\n\n  *  keys/secrets generated from a seed file may have lower entropy: it \nwas expected that the whole seed would be used to generate keys (240 \nbytes of entropy input), where in vulnerable versions only 28 bytes was \nused\n\n  *  a malicious entity could have recovered all passwords, generated \nfrom a particular seed, having only the seed file in possession without \nthe knowledge of the seed master password\n\nPatches\nThe code logic bug has been fixed in gokey version 0.2.0\n and above. Due to the deterministic nature of gokey, fixed versions \nwill produce different passwords/secrets using seed files, as all seed \nentropy will be used now.\n\nSystem secret rotation guidance\nIt is advised for users to regenerate passwords/secrets using the patched version of gokey (0.2.0\n and above), and provision/rotate these secrets into respective systems \nin place of the old secret. A specific rotation procedure is \nsystem-dependent, but most common patterns are described below.\n\nSystems that do not require the old password/secret for rotation\nSuch systems usually have a \"Forgot password\" facility or a\n similar facility allowing users to rotate their password/secrets by \nsending a unique \"magic\" link to the user's email or phone. In such \ncases users are advised to use this facility and input the newly \ngenerated password secret, when prompted by the system.\n\nSystems that require the old password/secret for rotation\nSuch systems usually have a modal password rotation window\n usually in the user settings section requiring the user to input the \nold and the new password sometimes with a confirmation. To \ngenerate/recover the old password in such cases users are advised to:\n\n  *  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\n\n  *  use gokey version 0.2.0 or above to generate the new password\n\n  *  populate the system provided password rotation form\n\nSystems that allow multiple credentials for the same account to be provisioned\nSuch systems usually require a secret or a cryptographic \nkey as a credential for access, but allow several credentials at the \nsame time. One example is SSH: a particular user may have several \nauthorized public keys configured on the SSH server for access. For such\n systems users are advised to:\n\n  *  generate a new secret/key/credential using gokey version 0.2.0 or above\n\n  *  provision the new secret/key/credential in addition to the existing credential on the system\n\n  *  verify that the access or required system operation is still possible with the new secret/key/credential\n\n  *  revoke authorization for the existing/old credential from the system\n\nCredit\nThis vulnerability was found by Théo Cusnir ( @mister_mime https://hackerone.com/mister_mime ) and responsibly disclosed through Cloudflare's bug bounty program.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"gokey allows secret recovery from a seed file without the master password","id":"CVE-2025-13353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Missing authorization in Tag, Category, and Taxonomy Manager – AI Autotagger with OpenAI","id":"CVE-2025-13354"},"packages":[{"ecosystem":"Go","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cloudflare/gokey","purl":null,"source":"GHSA-69jw-4jj8-fcxm"},{"ecosystem":"Go","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cloudflare/gokey","purl":"pkg:golang/github.com/cloudflare/gokey","source":"GHSA-69jw-4jj8-fcxm"},{"ecosystem":"Go","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"github.com/cloudflare/gokey","purl":"pkg:golang/github.com/cloudflare/gokey","source":"GO-2025-4174"}],"prev":{"headline":"Mattermost GitHub Plugin allows unauthorized GitHub reactions via reaction forwarding hijacking","id":"CVE-2025-13352"},"products":["gokey"],"published":"2025-12-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-02","vendors":["Cloudflare"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-13353/"}