4.7
/ 10
MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Description
Issue summary: Writing large, newline-free data into a BIO chain using the
line-buffering filter where the next BIO performs short writes can trigger
a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which
typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in
TLS/SSL data paths. In OpenSSL command-line applications, it is typically
only pushed onto stdout/stderr on VMS systems. Third-party applications that
explicitly use this filter with a BIO chain that can short-write and that
write large, newline-free data influenced by an attacker would be affected.
However, the circumstances where this could happen are unlikely to be under
attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated
data controlled by an attacker. For that reason the issue was assessed as
Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
line-buffering filter where the next BIO performs short writes can trigger
a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which
typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in
TLS/SSL data paths. In OpenSSL command-line applications, it is typically
only pushed onto stdout/stderr on VMS systems. Third-party applications that
explicitly use this filter with a BIO chain that can short-write and that
write large, newline-free data influenced by an attacker would be affected.
However, the circumstances where this could happen are unlikely to be under
attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated
data controlled by an attacker. For that reason the issue was assessed as
Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,
as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Basic Information
ID
CVE-2025-68160
Source
openssl
Published
Jan 27, 2026 at 16:01
Modified
Jan 29, 2026 at 15:06
Affected Product
Vendor
OpenSSL
Product
OpenSSL
Version
3.6.0
Affected Versions
OpenSSL OpenSSL 3.6.0
OpenSSL OpenSSL 3.5.0
OpenSSL OpenSSL 3.4.0
OpenSSL OpenSSL 3.3.0
OpenSSL OpenSSL 3.0.0
OpenSSL OpenSSL 1.1.1
OpenSSL OpenSSL 1.0.2
OpenSSL OpenSSL 3.5.0
OpenSSL OpenSSL 3.4.0
OpenSSL OpenSSL 3.3.0
OpenSSL OpenSSL 3.0.0
OpenSSL OpenSSL 1.1.1
OpenSSL OpenSSL 1.0.2
CWE Classification
References
- openssl-library.org /news/secadv/20260127.txt
- github.com /openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- github.com /openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- github.com /openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- github.com /openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- github.com /openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6