CVE-2025-14819

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

January 8, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Aug 9, 2026
No patch confirmed yet.
generic

oss-security - [ADVISORY] curl CVE-2025-14819: OpenSSL partial chain store policy bypass

http://www.openwall.com/lists/oss-security/2026/01/07/5
generic
https://curl.se/docs/CVE-2025-14819.json
generic

curl - OpenSSL partial chain store policy bypass - CVE-2025-14819

https://curl.se/docs/CVE-2025-14819.html

Vendor Advisories for CVE-2025-14819(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.14.1-2ubuntu1.1) @ questing2026-09-15ubuntu
redhatcurl-0:8.12.1-4.el10_2.32026-08-17redhat
redhatcurl-main-8.19.0-3.hum12026-04-07redhat

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

(5 across 5 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
curl—8.18.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl—8.18.0-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
curl7.88.1-10 ... 7.88.1-10+deb12u9 (18 versions)7.88.1-10+deb12u15—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2, 8.14.1-2+deb13u1, 8.14.1-2+deb13u2, 8.14.1-2+deb13u2~bpo13+1, 8.14.1-2+deb13u38.14.1-2+deb13u4—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.18.0~rc2-1 (27 versions)8.18.0~rc3-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 11× in last 7d / 33× 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 162 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-14819?
CVE-2025-14819 is a medium vulnerability published on January 8, 2026. When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPTNOPARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl…
When was CVE-2025-14819 disclosed?
CVE-2025-14819 was first published in the National Vulnerability Database on January 8, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-14819 actively exploited?
CVE-2025-14819 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.0% of all scored CVEs.
What is the CVSS score of CVE-2025-14819?
CVE-2025-14819 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2025-14819?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-14819, 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-14819

Explore →

Is Your Infrastructure Affected by CVE-2025-14819?

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

Start Free Scan →Browse All CVEs