https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 30 Sep 2026 01:49:11 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-30910 <p>Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.</p> <p>Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.</p> <p>Encountering this issue is unlikely as the message length would need to be very large.</p> <p>For bin2hex the input size would have to be &gt; SIZE_MAX / 2 For aegis encryption the input size would need to be &gt; SIZE_MAX - 32U For other encryption the input size would need to be &gt; SIZE_MAX - 16U For signatures the input size would need to be &gt; SIZE_MAX - 64U</p> <p>Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.</p> <p>Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.</p> <p>Encountering this issue is unlikely as the message length would need to be very large.</p> <p>For bin2hex the input size would have to be &gt; SIZE_MAX / 2 For aegis encryption the input size would need to be &gt; SIZE_MAX - 32U For other encryption the input size would need to be &gt; SIZE_MAX - 16U For signatures the input size would need to be &gt; SIZE_MAX - 64U</p> https://db.gcve.eu/vuln/fkie_cve-2026-30910 https://db.gcve.eu/vuln/ghsa-2qjg-jrhf-99vr <p>Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.</p> <p>Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.</p> <p>Encountering this issue is unlikely as the message length would need to be very large.</p> <p>For bin2hex the input size would have to be &gt; SIZE_MAX / 2 For aegis encryption the input size would need to be &gt; SIZE_MAX - 32U For other encryption the input size would need to be &gt; SIZE_MAX - 16U For signatures the input size would need to be &gt; SIZE_MAX - 64U</p> <p>Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.</p> <p>Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.</p> <p>Encountering this issue is unlikely as the message length would need to be very large.</p> <p>For bin2hex the input size would have to be &gt; SIZE_MAX / 2 For aegis encryption the input size would need to be &gt; SIZE_MAX - 32U For other encryption the input size would need to be &gt; SIZE_MAX - 16U For signatures the input size would need to be &gt; SIZE_MAX - 64U</p> https://db.gcve.eu/vuln/ghsa-2qjg-jrhf-99vr