Skip to main content
Mallory
MediumVulnerability

CVE-2025-68160: Heap out-of-bounds write in OpenSSL BIO_f_linebuffer

Published Jan 27, 2026 · Updated 10 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 4 in a dayToday
CVSS4.7Medium · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2025-68160CWE-787 · Out-of-bounds Write

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
OpenSSL Software FoundationOpensslapplication
FAQ

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.
Activity feed

Recent activity

50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : openssl (EulerOS-SA-2026-4609) | Tenable®OpenSSL's BIO_f_linebuffer filter can corrupt heap memory when processing large, newline-free writes through a downstream BIO that performs short writes. The typical impact is a crash and denial of service. The filter is not used by default in TLS/SSL data paths, and the advisory considers attacker control of the required conditions unlikely.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : edk2 (EulerOS-SA-2026-4683) | Tenable®A heap-based out-of-bounds write in OpenSSL's BIO_f_linebuffer can corrupt memory and crash applications. Exploitation requires unusual application behavior involving attacker-influenced, newline-free data and short writes. Default TLS/SSL data paths and OpenSSL FIPS modules are unaffected. The advisory assesses the issue as Low severity.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.1 : openssl (EulerOS-SA-2026-4567) | Tenable®OpenSSL's BIO_f_linebuffer filter can corrupt heap memory when handling large, newline-free input and downstream short writes, typically causing denial of service. Exposure requires applications to explicitly use this filter under the described conditions; default TLS/SSL data paths do not use it. The advisory rates this issue Low severity, and the listed FIPS modules are unaffected.Read more ↗tenable nessus pluginsNews · Nov 7, 2026EulerOS Virtualization 2.15.0 : edk2 (EulerOS-SA-2026-4741) | Tenable®A heap-based out-of-bounds write in OpenSSL's BIO_f_linebuffer can corrupt memory and crash applications. Exploitation requires large, attacker-influenced, newline-free input and a downstream BIO that performs short writes. Normal TLS/SSL paths do not use this filter. The advisory assesses the issue as Low severity; OpenSSL FIPS modules are unaffected. The plugin reports exploit availability collectively but does not identify whether an exploit exists specifically for this CVE.Read more ↗
+20 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity17Community discussion across Reddit, Mastodon, and other social sources.