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.
References
Configurations
No configuration.
History
21 Nov 2025, 18:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
|
21 Nov 2025, 17:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-11-21 17:15
Updated : 2025-11-25 22:16
NVD link : CVE-2025-13470
Mitre link : CVE-2025-13470
CVE.ORG link : CVE-2025-13470
JSON object : View
Products Affected
No product.
CWE
CWE-330
Use of Insufficiently Random Values
