fixnx
highCVE-2026-9080

CVE-2026-9080 curl vulnerability

Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.

Productcurl
CVSS7.3
EPSS0.00494
UpdatedJuly 14, 2026

Quick answer

haxx curl should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • from 8.13.0 before 8.21.0

Fixed versions

  • 8.21.0

How to fix it

CVE-2026-9080 affects curl or libcurl. It may crash the app or corrupt memory. Upgrade curl and libcurl to 8.21.0, or apply the vendor patch and rebuild affected apps.

  1. List every system, container, and app that uses curl or libcurl.
  2. Check the curl and libcurl versions on each system.
  3. Upgrade curl and libcurl to 8.21.0 or a distro backport that includes the fix.
  4. Rebuild apps and containers that statically link libcurl.
  5. Restart services that load libcurl after the update.
  6. Avoid risky options or workflows from the advisory until patched.
  7. Review proxy, TLS, SSH, and HTTP logs for unexpected data leaks.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Run curl --version or package checks and confirm 8.21.0 or a patched vendor build.
  • Confirm rebuilt apps link to the patched libcurl.
  • Retest affected SCP, SFTP, proxy, TLS, or HTTP flows as relevant.
  • Confirm logs no longer show the unsafe behavior.
  • Record package versions and rebuild evidence.

Related categories

Memory Corruption

Trusted references

Source advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVD

FAQ

What is affected by CVE-2026-9080?

haxx curl versions listed as affected should be reviewed: from 8.13.0 before 8.21.0.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.