{"id":"CVE-2025-13470","aliases":["DEBIAN-CVE-2025-13470","EUVD-2025-198494","GHSA-r3r8-w3g2-hq7h","UBUNTU-CVE-2025-13470","openSUSE-SU-2025:15762-1","openSUSE-SU-2025:20116-1"],"status":"published","title":"RNP 0.18.0 Vulnerable PKESK session keys","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","severity":{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/RE:H/U:Red","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.00325,"percentile":0.25804,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-330"],"published":"2025-11-21T17:05:15Z","modified":"2026-10-28T10:42:21Z","fixes":[{"ecosystem":"Debian:14","package":"rnp","fixed_in":["0.18.1-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:14","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.1-1"}]}],"versions":["0.17.1-1","0.18.0-1","0.18.0-2","0.18.0-3","0.18.0-4"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.14.0-6","0.15.2-6build1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.17.0-3"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.17.1-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["0.17.1-1","0.18.0-4","0.18.1-1","0.18.1-1build1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.1-1.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"rnp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.18.1-bp160.1.1"}]}],"bundled":2}],"products":[{"vendor":"ribose","product":"rnp"}],"references":[{"url":"https://github.com/rnpgp/rnp/commit/7bd9a8dc356aae756b40755be76d36205b6b161a","tags":["related","fix","report"]},{"url":"https://launchpad.net/ubuntu/+source/rnp","tags":["x_downstream-package","web","report"]},{"url":"https://aur.archlinux.org/packages/rnp","tags":["x_downstream-package","web","report"]},{"url":"https://packages.gentoo.org/packages/dev-util/librnp","tags":["x_downstream_package","web","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2415863","tags":["issue-tracking","report"]},{"url":"https://access.redhat.com/security/cve/cve-2025-13402","tags":["third-party-advisory","advisory","report"]},{"url":"https://open.ribose.com/advisories/ra-2025-11-20/","tags":["vendor-advisory","advisory","report"]},{"url":"https://github.com/rnpgp/rnp/releases/tag/v0.18.1","tags":["release-notes","advisory","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-13470","tags":["advisory"]},{"url":"https://open.ribose.com/advisories/ra-2025-11-20"},{"url":"https://github.com/advisories/GHSA-r3r8-w3g2-hq7h"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/13xxx/CVE-2025-13470.json","tags":["advisory"]},{"url":"https://github.com/rnpgp/rnp","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-13470","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-13470","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-13470","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2025-13402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-13470","tags":["web"]},{"url":"https://bugzilla.suse.com/1253957","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2025-13470","title":"RNP 0.18.0 Vulnerable PKESK session keys","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:05:15.683Z","modified":"2025-11-21T17:35:33.645Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/RE:H/U:Red","level":"high","assessor":"cna"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-330"],"updated_at":"2026-11-02T14:32:43.770144Z"}],"euvd":[{"id":"EUVD-2025-198494","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:05:15Z","modified":"2025-11-21T17:35:33Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/RE:H/U:Red","level":"high"}],"updated_at":"2026-11-02T19:49:13.665045Z"}],"ghsa":[{"id":"GHSA-r3r8-w3g2-hq7h","title":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public...","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T18:30:30Z","modified":"2025-11-21T18:30:35Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:H/U:Red","level":"high"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-330"],"updated_at":"2026-11-02T15:04:54.759819Z"}],"nvd":[{"id":"CVE-2025-13470","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:15:50.473Z","modified":"2026-10-08T10:10:00.227Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:H/U:Red","level":"high","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-330"],"updated_at":"2026-11-02T14:11:46.009629Z"}],"osv":[{"id":"CVE-2025-13470","title":"RNP 0.18.0 Vulnerable PKESK session keys","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric \nsession key used for Public-Key Encrypted Session Key (PKESK) packets to\n be left uninitialized except for zeroing, resulting in it always being \nan all-zero byte array.\n\nAny data encrypted using public-key encryption \nin this release can be decrypted trivially by supplying an all-zero \nsession key, fully compromising confidentiality.\n\nThe vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.\n\nRoot cause: Vulnerable session key buffer used in PKESK packet generation.\n\n\n\nThe defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization \nlogic inside `encrypted_build_skesk()` only randomized the key for the \nSKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:05:15.683Z","modified":"2026-10-28T10:42:21.768626934Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/RE:H/U:Red","level":"high"}],"cwes":["CWE-330"],"updated_at":"2026-11-02T15:44:46.340268Z"},{"id":"DEBIAN-CVE-2025-13470","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric  session key used for Public-Key Encrypted Session Key (PKESK) packets to  be left uninitialized except for zeroing, resulting in it always being  an all-zero byte array.  Any data encrypted using public-key encryption  in this release can be decrypted trivially by supplying an all-zero  session key, fully compromising confidentiality.  The vulnerability affects only public key encryption (PKESK packets).  Passphrase-based encryption (SKESK packets) is not affected.  Root cause: Vulnerable session key buffer used in PKESK packet generation.    The defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization  logic inside `encrypted_build_skesk()` only randomized the key for the  SKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:15:50.473Z","modified":"2026-10-09T09:47:35.176165607Z","cvss":[{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:X/V:X/RE:H/U:Red","level":"high"}],"updated_at":"2026-11-02T15:45:45.102284Z"},{"id":"UBUNTU-CVE-2025-13470","description":"In RNP version 0.18.0 a refactoring regression causes the symmetric session key used for Public-Key Encrypted Session Key (PKESK) packets to  be left uninitialized except for zeroing, resulting in it always being an all-zero byte array. Any data encrypted using public-key encryption in this release can be decrypted trivially by supplying an all-zero session key, fully compromising confidentiality. The vulnerability affects only public key encryption (PKESK packets). Passphrase-based encryption (SKESK packets) is not affected. Root cause: Vulnerable session key buffer used in PKESK packet generation. The defect was introduced in commit `7bd9a8dc356aae756b40755be76d36205b6b161a` where initialization logic inside `encrypted_build_skesk()` only randomized the key for the SKESK path and omitted it for the PKESK path.","status":"published","published":"2025-11-21T17:15:00Z","modified":"2026-05-20T16:20:22.026858369Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","level":"high"},{"version":"4.0","score":7.7,"vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/RE:H/U:Red","level":"high"}],"updated_at":"2026-11-02T16:55:20.144818Z"},{"id":"openSUSE-SU-2025:15762-1","title":"librnp0-0.18.1-1.1 on GA media","description":"These are all security issues fixed in the librnp0-0.18.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2025-11-24T00:00:00Z","modified":"2026-03-23T04:54:10.203583Z","updated_at":"2026-11-02T16:58:37.810934Z"},{"id":"openSUSE-SU-2025:20116-1","title":"Security update for rnp","description":"This update for rnp fixes the following issues:\n\n- update to 0.18.1:\n  * CVE-2025-13470: PKESK (public-key encrypted) session keys were\n    generated as all-zero, allowing trivial decryption of messages\n    encrypted with public keys only (boo#1253957, CVE-2025-13402)\n","status":"published","published":"2025-11-27T12:39:03Z","modified":"2026-03-23T04:54:17.411903Z","updated_at":"2026-11-02T16:58:38.101535Z"}]}}