Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-8932 — CVE-2026-8932 | Kitploit
Tools/GitHubGitHub/0xblackash/cve-2026-8932
Vulnerability AnalysisExploitationWeb SecurityNetwork SecurityCryptographyAuthentication
GitHub0xblackash/cve-2026-8932

CVE-2026-8932

CVE-2026-8932

View Repository
1374 months agoNot yet reviewed
Share

🚨 CVE-2026-8932 - The Oldest libcurl Security Bug

ChatGPT Image Jun 27, 2026, 12_36_55 AM

Incomplete mTLS Configuration Matching in libcurl

Severity Affected Fixed Status

The oldest security vulnerability ever fixed in libcurl—remaining unnoticed for over 25 years.


📖 Overview

CVE-2026-8932 is a security vulnerability in libcurl where the library may incorrectly reuse an existing TLS connection after mutual TLS (mTLS) client authentication settings have changed.

Because certain private key-related options were not included in libcurl's connection matching logic, an existing authenticated connection could be reused even when a different client certificate configuration should have forced a new TLS handshake.

Note: The standalone curl command-line tool is not affected. Only applications embedding libcurl are vulnerable.


⚠️ Technical Details

PropertyValue
CVECVE-2026-8932
Componentlibcurl
TypeIncomplete Connection Matching
CWECWE-305 (Authentication Bypass)
SeverityLow
Affected Versions7.7 – 8.20.0
Fixed Version8.21.0

🔍 Root Cause

When libcurl evaluates whether an existing TLS connection can be reused, several SSL parameters are compared.

However, some mTLS private key configuration options were omitted from this comparison.

As a result:

  • Connection reuse succeeds
  • TLS handshake is skipped
  • Previous client credentials remain associated with the connection
  • Authentication context becomes inconsistent

💥 Impact

Possible consequences include:

  • Authentication confusion
  • Incorrect mTLS identity reuse
  • Unexpected client certificate usage
  • Security policy violations
  • Incorrect credential isolation

Although exploitation requires specific application behavior, environments relying heavily on mutual TLS authentication should update immediately.


📌 Affected Versions

VersionStatus
7.7❌ Vulnerable
7.x❌ Vulnerable
8.0.x❌ Vulnerable
8.20.0❌ Vulnerable
8.21.0+✅ Fixed

🛠 Mitigation

  • Upgrade to libcurl 8.21.0 or later.
  • Apply the official security patch if upgrading is not immediately possible.
  • Avoid reusing libcurl handles after changing mTLS client certificate or private key settings.
  • Validate TLS session behavior in applications that dynamically switch client certificates.

🔬 Attack Scenario

Application
      │
      ▼
Creates TLS connection
      │
      ▼
Authenticates with Client Certificate A
      │
      ▼
Application switches to Certificate B
      │
      ▼
libcurl incorrectly reuses old TLS connection
      │
      ▼
Certificate A remains in use
      │
      ▼
Authentication mismatch

📸 Demo

CVE-2026-8932

🧠 Why It Matters

Unlike memory corruption vulnerabilities, this issue affects the logic governing TLS connection reuse.

Applications expecting a new authenticated session after changing client credentials may unknowingly continue using an old session, potentially violating authentication boundaries.


🏆 Historical Significance

This vulnerability is notable because it:

  • 🕒 Existed for more than 25 years
  • 📚 Originated in curl 7.7 (2001)
  • 🛡 Became the oldest known security issue ever fixed in libcurl

📚 References

  • Official curl Security Advisory
  • CVE-2026-8932
  • CWE-305 Authentication Bypass

⭐ If this repository helped you, consider giving it a star!

Stay patched • Stay secure • Happy hacking responsibly

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    708
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    500
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    398
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    341
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    259
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    257

Explore all tools

Browse our collection of tools

View all tools →