CVE-2025-13470

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-11-21. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

November 21, 2025

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Aug 8, 2026
Patch available. Sources: redhat, github_commit, github_release.
generic

dev-util/librnp – Gentoo Packages

https://packages.gentoo.org/packages/dev-util/librnp
generic

RA-2025-11-20: Security vulnerability fixed in RNP 0.18.1 | Ribose

https://open.ribose.com/advisories/ra-2025-11-20/
generic

rnp package : Ubuntu

https://launchpad.net/ubuntu/+source/rnp
github_release Patch Available

Version 0.18.1

Patch available: rnpgp/rnp v0.18.1

https://github.com/rnpgp/rnp/releases/tag/v0.18.1
github_commit

commit 7bd9a8dc356a (rnpgp/rnp)

Fix landed in rnpgp/rnp commit 7bd9a8dc356a — awaiting tagged release

https://github.com/rnpgp/rnp/commit/7bd9a8dc356aae756b40755be76d36205b6b161a
redhat Patch Available

2415863 – (CVE-2025-13402) CVE-2025-13402 github.com/rnpgp/rnp: RNP PKESK Session Keys Generated as All‑Zero

https://bugzilla.redhat.com/show_bug.cgi?id=2415863
generic

AUR (en) - rnp

https://aur.archlinux.org/packages/rnp
redhat Patch Available

CVE-2025-13402 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/cve-2025-13402

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rnp0.17.1-1, 0.18.0-1, 0.18.0-2, 0.18.0-3, 0.18.0-40.18.1-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:13 UTCEPSS rescore
  4. 2026-09-15 03:08 UTCEPSS rescore
  5. 2026-09-13 16:45 UTCEPSS rescore
  6. 2026-09-12 14:59 UTCEPSS rescore
  7. 2026-09-12 10:10 UTCOSV refresh
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-04 13:59 UTCEPSS rescore
  15. 2026-09-04 05:05 UTCEPSS rescore
  16. 2026-09-02 14:10 UTCEPSS rescore
  17. 2026-09-01 13:52 UTCEPSS rescore
  18. 2026-09-01 04:38 UTCEPSS rescore
  19. 2026-08-30 19:16 UTCEPSS rescore
  20. 2026-08-30 01:21 UTCEPSS rescore
  21. 2026-08-28 21:40 UTCEPSS rescore
  22. 2026-08-27 14:24 UTCEPSS rescore
  23. 2026-08-26 14:45 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-24 15:03 UTCOSV refresh
Show 75 more
  1. 2026-08-24 14:15 UTCEPSS rescore
  2. 2026-08-23 00:18 UTCEPSS rescore
  3. 2026-08-21 23:48 UTCEPSS rescore
  4. 2026-08-20 22:54 UTCEPSS rescore
  5. 2026-08-19 17:02 UTCEPSS rescore
  6. 2026-08-18 13:47 UTCEPSS rescore
  7. 2026-08-17 13:46 UTCEPSS rescore
  8. 2026-08-16 14:55 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-16 02:13 UTCEPSS rescore
  11. 2026-08-15 01:29 UTCEPSS rescore
  12. 2026-08-13 21:59 UTCEPSS rescore
  13. 2026-08-12 13:49 UTCEPSS rescore
  14. 2026-08-11 13:41 UTCEPSS rescore
  15. 2026-08-10 23:59 UTCEPSS rescore
  16. 2026-08-09 13:45 UTCEPSS rescore
  17. 2026-08-08 09:47 UTCEG score recompute
  18. 2026-08-08 09:47 UTCGHSA enrichment
  19. 2026-08-07 16:26 UTCEPSS rescore
  20. 2026-08-06 13:45 UTCEPSS rescore
  21. 2026-08-05 19:16 UTCEPSS rescore
  22. 2026-08-04 15:09 UTCEPSS rescore
  23. 2026-08-04 10:37 UTCEPSS rescore
  24. 2026-08-03 10:35 UTCEPSS rescore
  25. 2026-08-02 02:25 UTCEPSS rescore
  26. 2026-08-01 04:14 UTCEPSS rescore
  27. 2026-07-30 16:26 UTCEPSS rescore
  28. 2026-07-30 01:29 UTCEPSS rescore
  29. 2026-07-28 15:35 UTCEPSS rescore
  30. 2026-07-27 14:12 UTCEPSS rescore
  31. 2026-07-27 06:39 UTCOSV refresh
  32. 2026-07-26 14:53 UTCEPSS rescore
  33. 2026-07-25 14:17 UTCEPSS rescore
  34. 2026-07-24 14:16 UTCEPSS rescore
  35. 2026-07-23 14:17 UTCEPSS rescore
  36. 2026-07-23 02:48 UTCEG score recompute
  37. 2026-07-22 14:07 UTCEPSS rescore
  38. 2026-07-22 14:07 UTCEPSS rescore
  39. 2026-07-19 14:30 UTCEPSS rescore
  40. 2026-07-19 14:30 UTCEPSS rescore
  41. 2026-07-19 02:28 UTCEPSS rescore
  42. 2026-07-19 02:28 UTCEPSS rescore
  43. 2026-07-18 10:03 UTCEPSS rescore
  44. 2026-07-16 17:02 UTCEPSS rescore
  45. 2026-07-16 17:02 UTCEPSS rescore
  46. 2026-07-15 16:57 UTCEPSS rescore
  47. 2026-07-15 16:57 UTCEPSS rescore
  48. 2026-07-15 01:59 UTCEPSS rescore
  49. 2026-07-15 01:59 UTCEPSS rescore
  50. 2026-07-13 22:29 UTCEPSS rescore
  51. 2026-07-13 22:29 UTCEPSS rescore
  52. 2026-07-13 06:12 UTCEPSS rescore
  53. 2026-07-12 05:46 UTCEPSS rescore
  54. 2026-07-12 05:45 UTCEPSS rescore
  55. 2026-07-11 08:26 UTCEPSS rescore
  56. 2026-07-11 08:26 UTCEPSS rescore
  57. 2026-07-10 01:17 UTCOSV refresh
  58. 2026-07-09 19:09 UTCEPSS rescore
  59. 2026-07-08 15:14 UTCEPSS rescore
  60. 2026-07-07 13:45 UTCEPSS rescore
  61. 2026-07-06 16:26 UTCEPSS rescore
  62. 2026-07-06 02:22 UTCEPSS rescore
  63. 2026-07-06 02:22 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 06:30 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:21 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:08 UTCEPSS rescore
  73. 2026-06-27 03:08 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-13470?
CVE-2025-13470 is a high vulnerability published on November 21, 2025. 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…
When was CVE-2025-13470 disclosed?
CVE-2025-13470 was first published in the National Vulnerability Database on November 21, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-13470 actively exploited?
CVE-2025-13470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2025-13470?
CVE-2025-13470 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2025-13470?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-13470, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-13470

Explore →

Is Your Infrastructure Affected by CVE-2025-13470?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs