BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-80229High confidence

OpenSSL provider use-after-free

curl · curl

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.56% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs curl curl and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.22.0-r0Alpine Security Database ↗Source updated 3 Nov 2026
Debian trixietrixie · sourcecurlAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · sourcecurlNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 4 Nov 2026
Debian forkyforky · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.8.22.0~rc3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.8.22.0~rc3-1Debian Security Tracker ↗Source updated 4 Nov 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-80229 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycurl: libcurl: Memory corruption vulnerability via OpenSSL 3 provider use-after-free
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openvox-agent.src as a component of Red Hat Satellite 6
Summary
A flaw was found in libcurl when performing transfers via its multi interface with OpenSSL 3 provider configurations. Pooled TLS connections can outlive their originating easy handles, causing an allocated library context to be prematurely freed. This leaves the active connection with a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations. This memory corruption vulnerability could allow a remote attacker to cause a denial of service or potentially execute arbitrary code.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
CVE-2026-80229 · CSAF 2.0 · revision 18 · interimSUSE Product Security TeamCVE-2026-80229
114 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • curl as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • libcurl-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • libcurl4 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • curl as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • libcurl-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • libcurl4 as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • curl as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • libcurl-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • libcurl4 as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
Summary
When performing transfers via libcurl's multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-72167

No EUVD known-exploited evidence

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

What

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-416Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-72167Official EUVD mapping

When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3642Meinberg LANTIME: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Meinberg LANTIME ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen oder zu manipulieren, Denial-of-Service-Zustände herbeizuführen, sowie weitere, nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
BSI · German · WID-SEC-2026-3149cURL: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsmechanismen zu umgehen, Informationen offenzulegen und einen Denial-of-Service-Zustand herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260909Security Bulletin 9 Sep 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 9 Sep 2026, published on 9 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1583Avis du CERT-FR

ord?id=CVE-2026-73636 Référence CVE CVE-2026-73637 https://www.cve.org/CVERecord?id=CVE-2026-73637 Référence CVE CVE-2026-7383 https://www.cve.org/CVERecord?id=CVE-2026-7383 Référence CVE CVE-2026-75803 https://www.cve.org/CVERecord?id=CVE-2026-75803 Référence CVE CVE-2026-75804 https://www.cve.org/CVERecord?id=CVE-2026-75804 Référence CVE CVE-2026-75805 https://www.cve.org/CVERecord?id=CVE-2026-75805 Référence CVE CVE-2026-75806 https://www.cve.org/CVERecord?id=CVE-2026-75806 Référence CVE CVE-2026-77696 https://www.cve.org/CVERecord?id=CVE-2026-77696 Référence CVE CVE-2026-79768 https://www.cve.org/CVERecord?id=CVE-2026-79768 Référence CVE CVE-2026-80229 https://www.cve.org/CVERecord?id=CVE-2026-80229 Référence CVE CVE-2026-80230 https://www.cve.org/CVERecord?id=CVE-2026-80230 Référence CVE CVE-2026-80231 https://www.cve.org/CVERecord?id=CVE-2026-80231 Référence CVE CVE-2026-80255 https://www.cve.org/CVERecord?id=CVE-2026-80255 Référence CVE CVE-2026-82208 https://www.cve.org/CVERecord?id=CVE-2026-82208 Référence CVE CVE-2026-82209 https://www.cve.org/CVERecord?id=CVE-2026-82209 Référence CVE CVE-2026-82631 https://www.cve.org/CVERecord?id=CVE-2026-82631 Référence CVE CVE-2026-82677 https://www.cve.org/CVERecord?id=CVE-2026-82677 Référence CVE CVE-2026-8286 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1486Avis du CERT-FR

d?id=CVE-2026-79674 Référence CVE CVE-2026-79675 https://www.cve.org/CVERecord?id=CVE-2026-79675 Référence CVE CVE-2026-79676 https://www.cve.org/CVERecord?id=CVE-2026-79676 Référence CVE CVE-2026-79677 https://www.cve.org/CVERecord?id=CVE-2026-79677 Référence CVE CVE-2026-79921 https://www.cve.org/CVERecord?id=CVE-2026-79921 Référence CVE CVE-2026-80047 https://www.cve.org/CVERecord?id=CVE-2026-80047 Référence CVE CVE-2026-80205 https://www.cve.org/CVERecord?id=CVE-2026-80205 Référence CVE CVE-2026-80206 https://www.cve.org/CVERecord?id=CVE-2026-80206 Référence CVE CVE-2026-80225 https://www.cve.org/CVERecord?id=CVE-2026-80225 Référence CVE CVE-2026-80229 https://www.cve.org/CVERecord?id=CVE-2026-80229 Référence CVE CVE-2026-80230 https://www.cve.org/CVERecord?id=CVE-2026-80230 Référence CVE CVE-2026-80231 https://www.cve.org/CVERecord?id=CVE-2026-80231 Référence CVE CVE-2026-80274 https://www.cve.org/CVERecord?id=CVE-2026-80274 Référence CVE CVE-2026-80489 https://www.cve.org/CVERecord?id=CVE-2026-80489 Référence CVE CVE-2026-81634 https://www.cve.org/CVERecord?id=CVE-2026-81634 Référence CVE CVE-2026-81642 https://www.cve.org/CVERecord?id=CVE-2026-81642 Référence CVE CVE-2026-81722 https://www.cve.org/CVERecord?id=CVE-2026-81722 Référence CVE CVE-2026-81723 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1385Avis du CERT-FR

ecord?id=CVE-2026-78662 Référence CVE CVE-2026-78663 https://www.cve.org/CVERecord?id=CVE-2026-78663 Référence CVE CVE-2026-78667 https://www.cve.org/CVERecord?id=CVE-2026-78667 Référence CVE CVE-2026-78669 https://www.cve.org/CVERecord?id=CVE-2026-78669 Référence CVE CVE-2026-7899 https://www.cve.org/CVERecord?id=CVE-2026-7899 Référence CVE CVE-2026-7902 https://www.cve.org/CVERecord?id=CVE-2026-7902 Référence CVE CVE-2026-79650 https://www.cve.org/CVERecord?id=CVE-2026-79650 Référence CVE CVE-2026-79677 https://www.cve.org/CVERecord?id=CVE-2026-79677 Référence CVE CVE-2026-79921 https://www.cve.org/CVERecord?id=CVE-2026-79921 Référence CVE CVE-2026-80229 https://www.cve.org/CVERecord?id=CVE-2026-80229 Référence CVE CVE-2026-80230 https://www.cve.org/CVERecord?id=CVE-2026-80230 Référence CVE CVE-2026-80231 https://www.cve.org/CVERecord?id=CVE-2026-80231 Référence CVE CVE-2026-80255 https://www.cve.org/CVERecord?id=CVE-2026-80255 Référence CVE CVE-2026-80274 https://www.cve.org/CVERecord?id=CVE-2026-80274 Référence CVE CVE-2026-80489 https://www.cve.org/CVERecord?id=CVE-2026-80489 Référence CVE CVE-2026-80591 https://www.cve.org/CVERecord?id=CVE-2026-80591 Référence CVE CVE-2026-80592 https://www.cve.org/CVERecord?id=CVE-2026-80592 Référence CVE CVE-2026-80593 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1108Multiples vulnérabilités dans Curl

De multiples vulnérabilités ont été découvertes dans Curl. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une atteinte à l'intégrité des données et un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-033365HaxxのcURLにおける解放済みメモリの使用に関する脆弱性

libcurlのマルチインターフェースを介して転送を行う際、プールされたTLS接続がそれを生成したイージーハンドルの寿命を超えてしまうことがあります。OpenSSL 3のプロバイダ構成では、libcurlは割り当てられたライブラリコンテキストをイージーハンドルの状態に付加し、所有権の参照を取得せずにそれをOpenSSLに渡します。イージーハンドルが早期に破棄されると、このコンテキストが解放されてしまい、アクティブな接続がデングリングポインタを保持することになり、その後のI/O操作やハンドシェイク後の処理時にヒープの使用後解放(use-after-free)が発生します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
openvox-agent.src as a component of Red Hat Satellite 6
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 6 Sept 2026 · Last source change 15 Sept 2026, 06:03 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-08
European sourceENISA EUVD · EUVD-2026-72167
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    curl: 8.14.0 < 8.14.2, 8.15.0 < 8.16.1, 8.17.0 < 8.20.1, 8.21.0 < 8.22.0, f2ce6c46b9dcc46ced0ce43fa95176ea7599a854 < 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb, 8.21.0, 8.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    curl: 8.14.0 < 8.14.2, 8.15.0 < 8.16.1, 8.17.0 < 8.20.1, 8.21.0 < 8.22.0, f2ce6c46b9dcc46ced0ce43fa95176ea7599a854 < 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb, 8.21.0, 8.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    curl: 8.21.0 ≤ 8.21.0, 8.20.0 ≤ 8.20.0, 8.19.0 ≤ 8.19.0, 8.18.0 ≤ 8.18.0, 8.17.0 ≤ 8.17.0, 8.16.0 ≤ 8.16.0, 8.15.0 ≤ 8.15.0, 8.14.1 ≤ 8.14.1, 8.14.0 ≤ 8.14.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    curl: 8.14.0 < 8.14.2, 8.15.0 < 8.16.1, 8.17.0 < 8.20.1, 8.21.0 < 8.22.0, f2ce6c46b9dcc46ced0ce43fa95176ea7599a854 < 7ea37abc6ac0120ba5f6d94be8d196f7cf1506bb, 8.21.0, 8.20.0, 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  3. ENISA EUVD mappingEUVD-2026-72167 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-72167"}
    ENISA EUVD ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: hackerone.com/3969255; added patch: curl.se/CVE-2026-80229.html; 2 further additions.
    Before
    no authoritative guidance recorded
    After
    mitigation: hackerone.com/3969255 · patch: curl.se/CVE-2026-80229.html · remediation: curl.se/CVE-2026-80229.html · 1 more references
    curl.se ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    8.21.0 ≤ 8.21.0; 8.20.0 ≤ 8.20.0; 8.19.0 ≤ 8.19.0; 8.18.0 ≤ 8.18.0; 8.17.0 ≤ 8.17.0; 8.16.0 ≤ 8.16.0; 8.15.0 ≤ 8.15.0; 8.14.1 ≤ 8.14.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    curl: 8.21.0 ≤ 8.21.0, 8.20.0 ≤ 8.20.0, 8.19.0 ≤ 8.19.0, 8.18.0 ≤ 8.18.0, 8.17.0 ≤ 8.17.0, 8.16.0 ≤ 8.16.0, 8.15.0 ≤ 8.15.0, 8.14.1 ≤ 8.14.1, 8.14.0 ≤ 8.14.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  6. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    curl.se ↗
  7. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    hackerone.com ↗
  8. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CISA ADP ↗
  9. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    7.5 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
    CISA ADP ↗
  10. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-80229 · cve.blacktree.nl