CVE-2025-13470
Last modified
CVE-2025-13470 is a high-severity vulnerability rated 7.7/10 on the CVSS scale. 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.. EPSS estimates a 0.27% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-13470?
How severe is CVE-2025-13470?
How do I fix CVE-2025-13470?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-13463The Bold Page Builder plugin for WordPress is vulnerable to …6.4
- CVE-2025-13465Lodash versions 4.0.0 through 4.17.22 are vulnerable to prot…5.3
- CVE-2025-13466body-parser 2.2.0 is vulnerable to denial of service due to …5.5
- CVE-2025-13467A flaw was found in the Keycloak LDAP User Federation provid…5.5
- CVE-2025-13468A weakness has been identified in SourceCodester Alumni Mana…8.1
- CVE-2025-13469A security vulnerability has been detected in Public Knowled…4.8
- CVE-2025-13471The User Activity Log WordPress plugin through 2.2 does not …5.3
- CVE-2025-13472A fix was made in BlazeMeter Jenkins Plugin version 4.27 to …5.3
- CVE-2025-13473An issue was discovered in 6.0 before 6.0.2, 5.2 before 5.2.…5.3
- CVE-2025-13474Authorization Bypass Through User-Controlled Key vulnerabili…7.5
- CVE-2025-13475In multi-tenanted deployments, the application consent manag…7.3
- CVE-2025-13476Rakuten Viber Cloak mode in Android v25.7.2.0g and Windows v…9.8
Are you affected by CVE-2025-13470?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST