CVE-2025-68160: Heap out-of-bounds write in BIO_f_linebuffer on short writes

Published Jan 16, 2026
·
Updated

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 (BIOflinebuffer) 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 BIOflinebuffer 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.

Other sources

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 (BIOflinebuffer) 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 BIOflinebuffer 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.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.1.

OpenSSL 3.5 users should upgrade to OpenSSL 3.5.5.

OpenSSL 3.4 users should upgrade to OpenSSL 3.4.4.

OpenSSL 3.3 users should upgrade to OpenSSL 3.3.6.

OpenSSL 3.0 users should upgrade to OpenSSL 3.0.19.

OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1ze (premium support customers only).

OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zn (premium support customers only).

Red Hat

Affected Software

12 affected components
OpenSSL OpenSSL>=1.0.2<=1.1.1, >=3.0<=3.6
OpenSSL OpenSSL>=1.0.2<1.0.2zn
OpenSSL OpenSSL>=1.1.1<1.1.1ze
OpenSSL OpenSSL>=3.0.0<3.0.19
OpenSSL OpenSSL>=3.3.0<3.3.6
OpenSSL OpenSSL>=3.4.0<3.4.4
OpenSSL OpenSSL>=3.5.0<3.5.5
OpenSSL OpenSSL>=3.6.0<3.6.1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade OpenSSL 1.0.2 to a version that resolves this vulnerability.

    Fixed in 1.0.2zn
  2. Upgrade

    Upgrade OpenSSL 1.1.1 to a version that resolves this vulnerability.

    Fixed in 1.1.1ze
  3. Upgrade

    Upgrade OpenSSL 3.0 to a version that resolves this vulnerability.

    Fixed in 3.0.19
  4. Upgrade

    Upgrade OpenSSL 3.3 to a version that resolves this vulnerability.

    Fixed in 3.3.6
  5. Upgrade

    Upgrade OpenSSL 3.4 to a version that resolves this vulnerability.

    Fixed in 3.4.4
  6. Upgrade

    Upgrade OpenSSL 3.5 to a version that resolves this vulnerability.

    Fixed in 3.5.5
  7. Upgrade

    Upgrade OpenSSL 3.6 to a version that resolves this vulnerability.

    Fixed in 3.6.1

Event History

Jan 16, 2026
Data Sourced
via Red Hat·02:33 PM
DescriptionSeverityAffected Software
Jan 27, 2026
CVE Published
via MITRE·04:01 PM
Data Sourced
via MITRE·04:01 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-68160?

CVE-2025-68160 has a high severity due to the potential for a heap out-of-bounds write, which can lead to memory corruption and application crashes.

2

How do I fix CVE-2025-68160?

To fix CVE-2025-68160, upgrade to a version of OpenSSL that is not affected, specifically versions later than OpenSSL 1.1.1 and 3.0.

3

What are the affected versions of OpenSSL for CVE-2025-68160?

CVE-2025-68160 affects OpenSSL versions from 1.0.2 to 1.1.1 and from 3.0 to 3.6.

4

What impact does CVE-2025-68160 have on applications?

CVE-2025-68160 can cause applications to experience memory corruption, potentially leading to crashes or arbitrary code execution.

5

How does CVE-2025-68160 exploit the vulnerability?

CVE-2025-68160 exploits a flaw in the BIO_f_linebuffer function when performing short writes in a BIO chain with large data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203