Alerts This Week
Warning Icon 1 764
Alerts This Week
Warning Icon 1 764

Gentoo: librnp High Weak Random Ending Generation GLSA-202511-07

gentoo
Calendar Grey November 26, 2025
Dist Gentoo Esm H88
librnp uses weak random number generation, risking encrypted messages. Users must upgrade to prevent exposure of sensitive information.
librnp uses weak random number generation such that generated keys can be easily cracked.

Summary

The affected librnp version generated weak session keys for its public key encryption (PKESK) mode.

Resolution

All librnp users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-util/librnp-0.18.1"
If sensitive information was sent using e.g. Thunderbird (with USE=system-librnp, the default), it should be considered potentially viewable by an attacker.

References

[ 1 ] CVE-2025-13470 https://nvd.nist.gov/vuln/detail/CVE-2025-13470

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202511-07
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
critical
Lowest
Low
Medium
High
Critical

Severity: High
Title: librnp: Weak random number generation
Date: November 26, 2025
Bugs: #966299
ID: 202511-07

Synopsis

librnp uses weak random number generation such that generated keys can be easily cracked.

Background

librnp is a high performance C++ OpenPGP library.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected --------------- ------------ ------------ dev-util/librnp = 0.18.0 >= 0.18.1

Impact

Messages encrypted using the affected librnp version might be readable by an attacker with just the public key.

Workaround

There is no known workaround at this time.

Your message here