CVE-2025-68160

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-01-27. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

January 27, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 9, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 68a7cd2e2816 (openssl/openssl)

Fix landed in openssl/openssl commit 68a7cd2e2816 — awaiting tagged release

https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
github_commit

commit 6845c3b6460a (openssl/openssl)

Fix landed in openssl/openssl commit 6845c3b6460a — awaiting tagged release

https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
github_commit

commit 4c96fbba618e (openssl/openssl)

Fix landed in openssl/openssl commit 4c96fbba618e — awaiting tagged release

https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
github_commit

commit 475c466ef2fb (openssl/openssl)

Fix landed in openssl/openssl commit 475c466ef2fb — awaiting tagged release

https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
github_commit

commit 384011202af9 (openssl/openssl)

Fix landed in openssl/openssl commit 384011202af9 — awaiting tagged release

https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm14) @ xenial2026-06-08ubuntu
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3) @ questing2026-06-08ubuntu
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17708363492026-02-24redhat
redhatrhui5/installer-rhel9:17706469252026-02-11redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17707404052026-02-10redhat
redhatdiscovery/discovery-ui-rhel9:17691117742026-02-02redhat
redhatopenssl-1:3.5.1-7.el9_72026-01-28redhat
redhatopenssl-1:3.5.1-7.el10_12026-01-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 10 ecosystems)
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.19-r0
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
openssl3.3.6-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
openssl3.3.6-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.5-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.5-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.5-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (20 versions)1.1.1w-0+deb11u5
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl3.0.10-1 ... 3.0.9-1 (18 versions)3.0.18-1~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1, 3.5.1-1+deb13u1, 3.5.2-1, 3.5.3-1, 3.5.4-1~deb13u13.5.4-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.5-1~deb13u2 (8 versions)3.5.5-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 176 total refreshes for this CVE.

  1. 2026-08-31 04:03 UTCOSV refresh
  2. 2026-08-30 01:21 UTCEPSS rescore
  3. 2026-08-28 21:40 UTCEPSS rescore
  4. 2026-08-27 14:24 UTCEPSS rescore
  5. 2026-08-26 14:45 UTCEPSS rescore
  6. 2026-08-25 13:48 UTCEPSS rescore
  7. 2026-08-24 14:16 UTCEPSS rescore
  8. 2026-08-23 00:18 UTCEPSS rescore
  9. 2026-08-21 23:48 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:46 UTCEPSS rescore
  14. 2026-08-16 14:55 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 12:11 UTCEG score recompute
  18. 2026-08-14 12:11 UTCVendor advisory
  19. 2026-08-14 12:11 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 04:17 UTCEG score recompute
  22. 2026-08-13 04:17 UTCVendor advisory
  23. 2026-08-13 04:17 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-10 23:59 UTCEPSS rescore
  2. 2026-08-09 17:58 UTCEG score recompute
  3. 2026-08-09 17:58 UTCVendor advisory
  4. 2026-08-09 17:58 UTCGHSA enrichment
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 16:36 UTCEPSS rescore
  7. 2026-08-07 23:25 UTCEG score recompute
  8. 2026-08-07 23:25 UTCVendor advisory
  9. 2026-08-07 23:25 UTCGHSA enrichment
  10. 2026-08-07 16:27 UTCEPSS rescore
  11. 2026-08-06 13:46 UTCEPSS rescore
  12. 2026-08-06 04:53 UTCEG score recompute
  13. 2026-08-06 04:53 UTCVendor advisory
  14. 2026-08-06 04:53 UTCGHSA enrichment
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 10:37 UTCEPSS rescore
  17. 2026-08-03 10:35 UTCEPSS rescore
  18. 2026-08-02 22:02 UTCEG score recompute
  19. 2026-08-02 22:02 UTCVendor advisory
  20. 2026-08-02 22:02 UTCGHSA enrichment
  21. 2026-08-02 02:26 UTCEPSS rescore
  22. 2026-08-01 04:15 UTCEPSS rescore
  23. 2026-07-31 06:42 UTCOSV refresh
  24. 2026-07-30 16:27 UTCEPSS rescore
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-27 14:13 UTCEPSS rescore
  27. 2026-07-25 14:17 UTCEPSS rescore
  28. 2026-07-25 14:17 UTCEPSS rescore
  29. 2026-07-24 14:17 UTCEPSS rescore
  30. 2026-07-23 14:18 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 03:02 UTCEG score recompute
  33. 2026-07-22 14:08 UTCEPSS rescore
  34. 2026-07-21 15:24 UTCEPSS rescore
  35. 2026-07-20 17:08 UTCEPSS rescore
  36. 2026-07-19 14:30 UTCEPSS rescore
  37. 2026-07-19 14:30 UTCEPSS rescore
  38. 2026-07-19 02:28 UTCEPSS rescore
  39. 2026-07-19 02:28 UTCEPSS rescore
  40. 2026-07-18 10:04 UTCEPSS rescore
  41. 2026-07-18 10:04 UTCEPSS rescore
  42. 2026-07-16 17:02 UTCEPSS rescore
  43. 2026-07-16 17:02 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-15 01:59 UTCEPSS rescore
  48. 2026-07-13 14:08 UTCOSV refresh
  49. 2026-07-13 06:12 UTCEPSS rescore
  50. 2026-07-12 05:46 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-08 15:15 UTCEPSS rescore
  56. 2026-07-07 13:46 UTCEPSS rescore
  57. 2026-07-06 16:27 UTCEPSS rescore
  58. 2026-07-05 02:30 UTCEPSS rescore
  59. 2026-07-05 02:30 UTCEPSS rescore
  60. 2026-07-04 06:31 UTCEPSS rescore
  61. 2026-07-04 06:31 UTCEPSS rescore
  62. 2026-07-01 15:06 UTCEPSS rescore
  63. 2026-06-30 23:22 UTCEPSS rescore
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-29 14:06 UTCEPSS rescore
  66. 2026-06-29 14:06 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 14:07 UTCEPSS rescore
  69. 2026-06-28 04:56 UTCEPSS rescore
  70. 2026-06-28 04:56 UTCEPSS rescore
  71. 2026-06-27 03:08 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-25 13:49 UTCEPSS rescore
  74. 2026-06-25 11:01 UTCOSV refresh
  75. 2026-06-24 14:05 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-68160?
CVE-2025-68160 is a medium vulnerability published on January 27, 2026. 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…
When was CVE-2025-68160 disclosed?
CVE-2025-68160 was first published in the National Vulnerability Database on January 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68160 actively exploited?
CVE-2025-68160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.7% of all scored CVEs.
What is the CVSS score of CVE-2025-68160?
CVE-2025-68160 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2025-68160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68160, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68160

Explore →

Is Your Infrastructure Affected by CVE-2025-68160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.