SASL double-free

Why this deserves its current priority

CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps curl/curl (generic), curl/curl (generic), curl/curl (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for curl/curl, curl/curl, curl/curl.
2. 2Review the reported fix. Update curl/curl to 8.16.1; curl/curl to 3da249e1f0716c06644ed3522a37a8bf81808012 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Jul 3, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 15, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Jul 3, 2026

Sources and claim methodology

• Source referencecurl.se
• Source referencecurl.se
• Source referencehackerone.com

Related CVEs

• Eventin <= 4.1.23 - Authenticated (Custom+) Stored Cross-Site Scripting via 'etn_shedule_objective' schedule_slot ParameterSame generic ecosystem
• 3D FlipBook <= 1.16.20 - Unauthenticated Sensitive Information Exposure in 'id' ParameterSame generic ecosystem
• WP Directory Kit <= 1.5.7 - Contributor+ Non-Public Listing Field Disclosure via ShortcodesSame generic ecosystem
• WP Directory Kit <= 1.5.7 - Editor+ SQL Injection via Elementor Category and Location Widget SettingsSame generic ecosystem
• moment vulnerable to Path Traversal via crafted non-string locale nameSame generic ecosystem
• Job Postings <= 2.8.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'position_button' ParameterSame generic ecosystem