Finding and attribution
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.
Product: curl curl. AI system: AISLE AI-native discovery engine (model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2025-14819.
AI and human contribution (source account): AISLE’s CVE Discoveries index lists this CVE among those its AI-native engine discovered, and the individual AISLE page says “Discovered by AISLE”. The CNA record credits “Stanislav Fort (Aisle Research); Daniel Stenberg”; a credited human name is not itself AI attribution, which rests on AISLE’s page. The model/version and the division of work between the engine and human researchers are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Public CVE disclosure is dated 2026-01-08. AISLE’s case page timeline shows 2026-01-08, used as the AI-attribution date. The cited sources establish an assigned vulnerability, not exploitation in the wild or zero-day status.
Remediation status: not established. The CVE record does not state a fix or patch reference. Confirm the distribution-specific backport before relying on a version number.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 8 Jan 2026. AI attribution dated 8 Jan 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.
Documented fix: The CVE record does not state a fix or patch reference. Confirm the distribution-specific backport before relying on a version number.