DHI-zpqq-uqkt-l6hs-kvxw

Source
https://scout.docker.com/v/DHI-zpqq-uqkt-l6hs-kvxw
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-zpqq-uqkt-l6hs-kvxw.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-zpqq-uqkt-l6hs-kvxw
Upstream
  • CVE-2026-121481
Published
2026-11-21T16:31:30Z
Modified
2026-11-21T17:45:03Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX
Details

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.

Database specific
{
    "coverage": "partial",
    "coverage_exclusions": [
        "legacy_package_image_owner"
    ]
}
References

Affected packages

Docker Hardened Images:Debian:13 / openssl

Package

Name
openssl
Purl
pkg:deb/dhi/openssl

Affected ranges

Affected versions

3.*
3.5.5-1~deb13u2dhi0
3.5.6-1~deb13u1dhi0
3.5.6-1~deb13u1+dhi0
3.5.6-1~deb13u1+dhi1
3.5.6-1~deb13u1+dhi2
3.5.6-1~deb13u1+fips+dhi0
3.5.6-1~deb13u1+fips+dhi1
3.5.6-1~deb13u1+fips+dhi2
3.5.6-1~deb13u2+dhi0
3.5.6-1~deb13u2+dhi1
3.5.6-1~deb13u2+dhi2
3.5.6-1~deb13u2+dhi3
3.5.6-1~deb13u2+fips+dhi0
3.5.6-1~deb13u2+fips+dhi1
3.5.7-1~deb13u2+dhi0
3.5.7-1~deb13u2+dhi1
3.5.7-1~deb13u2+fips+dhi0
3.5.7-1~deb13u3+dhi0
3.5.7-1~deb13u3+dhi1
3.5.7-1~deb13u3+dhi2
3.5.7-1~deb13u3+dhi3
3.5.7-1~deb13u3+fips+dhi0
3.5.9-1~deb13u1+dhi0
3.5.9-1~deb13u1+fips+dhi0

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-zpqq-uqkt-l6hs-kvxw.json"