Skip to content
VulniPulse
Sign in
Highest advisory severityCritical 3 vendors · 3 advisories

CVE-2026-8927

Libcurl Vulnerability in NetApp Products

CVE-2026-8927: Libcurl Vulnerability in NetApp Products. Not in the CISA KEV catalog. Critical advisory severity (CVSS 9.1, NetApp).

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

NVD detail CVE.org

Get an email when NetApp publishes the next one.

VulniPulse checks NetApp's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

CVE-2026-8927 key facts

CISA KEV
Not listed (catalog checked )
Highest advisory severity
Critical
CVSS base score
9.1 (NetApp), 7.5 (Red Hat)
CVSS vector
  • CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (Red Hat)
Weakness
CWE-201
Fixed releases
  • Red Hat: curl-0:8.12.1-4.el10_2.4, curl-0:8.12.1-1.el10_0.10, curl-0:7.76.1-40.el9_8.7, libcurl-1.dll, cert-manager/jetstack-cert-manager-rhel9:1790223279, cert-manager/cert-manager-istio-csr-rhel9:1790223719 and 27 more in the advisory
Vendor advisories
3 from NetApp, Red Hat, Veeam
VulniPulse record
Published · Updated

Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-8927; bulletin-wide values are not repeated here.

Is CVE-2026-8927 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-8927 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-8927?

Upgrade to a fixed release named by the vendor:

  • Red Hat: curl-0:8.12.1-4.el10_2.4, curl-0:8.12.1-1.el10_0.10, curl-0:7.76.1-40.el9_8.7, libcurl-1.dll, cert-manager/jetstack-cert-manager-rhel9:1790223279, cert-manager/cert-manager-istio-csr-rhel9:1790223719
  • To mitigate this issue, applications utilizing libcurl should avoid reusing handles when switching between different proxy configurations. This operational control prevents the unintended leakage of `Proxy-Authorization` headers to incorrect proxies. (Red Hat)

Vendor advisory comparison

NetApp

1 advisory
  • Advisory severityCritical9.1

    Critical [CVE-2026-8927] Libcurl Vulnerability in NetApp Products

    NTAP-20260731-0008Source published Source updated

    Libcurl versions 7.12.0 prior to 8.21.0 are susceptible to a vulnerability which when successfully exploited could lead to disclosure of sensitive information or addition or modification of data. NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 7.12.0
    • 8.21.0
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-8927] Information disclosure due to uncleared proxy authentication state

    CVE-2026-8927Source published Source updated

    When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`. A flaw was found in libcurl. This oversight can lead to the unintended disclosure of `Proxy-Authorization` headers to an incorrect proxy, potentially exposing sensitive authentication information to an unauthorized entity. This flaw leads only to a confidentiality impact. There has been no observed integrity impact. Red Hat severity: Important — CVSS 7.5…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10.0 Extended Update Support
    • Red Hat Enterprise Linux 9
    • Red Hat JBoss Core Services 2.4.62.SP5
    • Cert Manager support for Red Hat OpenShift release 1.20

    11 more entries in the full advisory.

    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • curl-0:8.12.1-4.el10_2.4
    • curl-0:8.12.1-1.el10_0.10
    • curl-0:7.76.1-40.el9_8.7
    • libcurl-1.dll

    29 more entries in the full advisory.

    Mitigation guidance
    • To mitigate this issue, applications utilizing libcurl should avoid reusing handles when switching between different proxy configurations. This operational control prevents the unintended leakage of `Proxy-Authorization` headers to incorrect proxies.
    Full advisory and evidenceOpen source bulletin

Veeam

1 advisory
  • Advisory severityCritical

    Critical [CVE-2020-14040 +102] List of Security Fixes and Improvements in Veeam Kasten for Kubernetes

    KB4825Source published

    This bulletin covers 103 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: Purpose This article aims to provide our customers' security and compliance teams with detailed information on security improvements. - Veeam Kasten for Kubernetes — Release Notes - Upgraded the frontend's bundled JavaScript dependencies to resolve GHSA-g2v6-rqmx-r4w6 in @vue/server-renderer (High). - Also resolves 7 Medium severity CVEs in the same and other packages. - Upgraded to latest UBI base image to resolve multiple CVEs in base OS packages. - Updated the Go runtime to resolve additional upstream Go CVEs. - Updated the bundled Prometheus Helm chart to resolve security issues. - Upgraded the Prometheus base…

    Related products — impact not confirmed
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • 8.5.10
    • 8.5.5
    • 1.26.1
    • 8.5.3

    20 more entries in the full advisory.

    Mitigation guidance
    • List of Security Fixes and Improvements in Veeam Kasten for Kubernetes KB ID: 4825 Product: Veeam Kasten for Kubernetes | 7 | 7.5 | 8 | 8.5 | 9 Kasten K10 by Veeam | 3 | 5 | 5.5 | 6 | 6.5 Published: 2026-03-02 Last Modified: 2026-10-23 Purpose This article describes all security-related fixes and improvements introduced in each release or update of Veeam Kasten for Kubernetes.
    • It is recommended to upgrade Veeam Kasten and to refresh the token by manually logging out.
    • Mitigation: Configure a bucket-level Default Object Lock retention so the object store stamps new objects at write time, or upgrade to Kasten 8.5.10.
    • Veeam Kasten for Kubernetes 8.5.5 Upgrade to Go 1.26.1 to address CVE-2026-25679 and CVE-2026-27142 Updated the UBI base image to address CVE-2026-4111 Veeam Kasten for Kubernetes 8.5.3 Upgrade to Go 1.25.7 to address CVE-2025-61732.

    4 more entries in the full advisory.

    Workarounds
    • Veeam Kasten for Kubernetes 8.0.14 Improved logging security for specific block mode datamover upload Pod invocations.
    Full advisory and evidenceOpen source bulletin

More NetApp advisories

All NetApp advisories

Follow CVE-2026-8927 in the free weekly digest

Every Monday: whether it was added to CISA KEV, reported exploited, got a fix or changed severity, plus the week's critical and high advisories.

Free, no account. Confirm by email; unsubscribe in one click. Choose vendors and severity

Browse the latest tracked CVEs or the CVEs listed in CISA KEV.

Android app · Google Play

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features