Data decryption via zeroed PKESK session keys
Published Nov 21, 2025 · Updated Nov 21, 2025
Insufficiently random session keys in Ribose RNP 0.18.0 allow remote attackers to decrypt data encrypted with public keys. The encrypted_build_skesk() refactoring leaves the PKESK session-key buffer zeroed instead of filling it with cryptographically random bytes. Only public-key encryption produced by 0.18.0 is exposed; passphrase-based SKESK encryption is unaffected, and possession of ciphertext permits decryption without the private key.
Summary
What happened
Insufficiently random session keys in Ribose RNP 0.18.0 allow remote attackers to decrypt data encrypted with public keys. The encrypted_build_skesk() refactoring leaves the PKESK session-key buffer zeroed instead of filling it with cryptographically random bytes. Only public-key encryption produced by 0.18.0 is exposed; passphrase-based SKESK encryption is unaffected, and possession of ciphertext permits decryption without the private key.
The record
- CVE
- CVE-2025-13470
- Published
- Nov 21, 2025
- Updated
- Nov 21, 2025
- Vendor
- Ribose
- Product
- RNP
- Classifications
- CWE-330, T1140
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2025CVE publishedPublication date reported by the CVE source.
- Nov 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo