CVE-2025-68160

Heap out-of-bounds write in BIO_f_linebuffer on short writes

MEDIUM
4.7
CVSS Score
Published: January 27, 2026 at 04:01 PM UTC
Updated: October 15, 2026 at 01:09 AM UTC
2 products affected across 2 vendorsOpenSSLSIMATIC S7-1500 TM MFP

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.0.2 ≤ v < 1.0.2zn1.1.1 ≤ v < 1.1.1ze3.0.0 ≤ v < 3.0.193.3.0 ≤ v < 3.3.63.4.0 ≤ v < 3.4.43.5.0 ≤ v < 3.5.53.6.0 ≤ v < 3.6.11.0.21.1.13.0.03.3.03.4.03.5.03.6.0
Affected range stops below 1.0.2zn, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1ze, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6.1, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.7MEDIUM134c704f-9b21-4f2e-91b3-4a467353bcc0
Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card