CVE-2025-68160: Heap out-of-bounds write in OpenSSL BIO_f_linebuffer
- Vendor
- OpenSSL Software Foundation
CVE-2025-68160 is a heap-based out-of-bounds write vulnerability in OpenSSL's line-buffering BIO filter, BIO_f_linebuffer. Writing large amounts of newline-free data through this filter can trigger an out-of-bounds write when the next BIO in the chain performs short writes. The resulting heap corruption typically crashes the application. Affected release branches include OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1, and 1.0.2. The filter is not used by default in TLS/SSL data paths; OpenSSL command-line applications typically attach it to standard output or standard error only on VMS systems. The issue is assessed as Low severity because the necessary application behavior and attacker influence are uncommon. OpenSSL FIPS modules in branches 3.6, 3.5, 3.4, 3.3, and 3.0 are unaffected because the BIO implementation is outside the FIPS module boundary.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can corrupt application heap memory and typically terminate the affected process, causing denial of service. Practical exposure depends on application-specific use of the line-buffering filter rather than ordinary TLS/SSL processing. Arbitrary code execution, information disclosure, and privilege escalation are not established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Remove or avoid BIO_f_linebuffer in paths that process attacker-influenced large, newline-free data. If the filter must remain, ensure the downstream BIO does not perform short writes in the affected usage. Prevent untrusted output from reaching susceptible filter chains until a fixed implementation can be deployed.
Remediation
Patch, then assume compromise.
Install an OpenSSL security update that fixes CVE-2025-68160, or the corresponding operating-system or product-vendor update for bundled OpenSSL. Fixed releases identified for maintained branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19; use the appropriate fixed release or a later security update for the deployed branch. Vendor packages may incorporate backported fixes without adopting these upstream version numbers. Fixed 1.1.1 and 1.0.2 release numbers are not available here.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-68160 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2025-68160 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2025-68160?
- As of Nov 7, 2026, Mallory has found no public exploit for CVE-2025-68160.
- Is there a patch for CVE-2025-68160?
- Install an OpenSSL security update that fixes CVE-2025-68160, or the corresponding operating-system or product-vendor update for bundled OpenSSL. Fixed releases identified for maintained branches are 3.6.1, 3.5.5, 3.4.4, 3.3.6, and 3.0.19; use the appropriate fixed release or a later security update for the deployed branch.
- What products are affected by CVE-2025-68160?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2025-68160?
- CVE-2025-68160 has a CVSS v3.1 score of 4.7 (Medium) and an EPSS score of 0.19% (9th percentile) as of Nov 7, 2026.
Recent activity
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.