Integer Overflow or Wraparound Affecting rust-bootupd package, versions <0:0.3.2-1.1.hum1


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.46% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-RUSTBOOTUPD-22697599
  • published21 Nov 2026
  • disclosed18 Nov 2026

Introduced: 18 Nov 2026

NewCVE-2026-121481  (opens in a new tab)
CWE-190  (opens in a new tab)

How to fix?

Upgrade RHEL:10 rust-bootupd to version 0:0.3.2-1.1.hum1 or higher.
This issue was patched in RHSA-2026:80572.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-bootupd package and not the rust-bootupd package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer.

Impact summary: No path by which an attacker can trigger this has been identified. An application that passes an input length near INT_MAX to EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting its own memory, but it must itself supply such a length.

CWE: CWE-190: Integer Overflow or Wraparound

Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied length into an output buffer that the caller allocates. The caller is expected to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the arithmetic that computes the encoded length overflows a signed integer, so the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process.

Reaching this requires an application to pass an input length near INT_MAX to EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode buffers of that size, and the command line tools cannot practically be made to do so: the limits on reading a proxy password from a file and on bignum sizes prevent it. An application that accepts an attacker-controlled length and forwards it to EVP_EncodeBlock() without its own bound check is exposed.

The severity is Low because no attacker-controlled path to the overflow is known. The caller must already hold a buffer of about two gigabytes before the defect can be reached.

FIPS impact: no The affected code is outside the FIPS module boundary.

CVSS Base Scores

version 3.1