hackervlogofficial/cve-2026-23918This is a proactive tool for security auditing. For your GitHub repository, you’ll want a description that highlights its safety (non-intrusive) and its specific utility for system administrators.
This is a proactive tool for security auditing. For your GitHub repository, you’ll want a description that highlights its safety (non-intrusive) and its specific utility for system administrators.
Here are a few options for your GitHub description and a template for your README.md.
GitHub Repository Description CVE-2026-23918 Scanner: A non-intrusive Python-based tool to detect the Apache HTTP/2 Double-Free vulnerability. Safely audit production servers for vulnerable versions and HTTP/2 configurations without exploitation.
README.md Template You can copy and paste this into your README.md file to give users a clear understanding of how the tool works.
CVE-2026-23918 Apache HTTP/2 Scanner This repository contains a simple, safe-to-run Python scanner designed to identify servers vulnerable to CVE-2026-23918, a critical double-free vulnerability in Apache HTTP/2.
🔍 Key Features Version Detection: Checks the Server header to identify if Apache 2.4.66 is in use.
HTTP/2 Audit: Uses ALPN (Application-Layer Protocol Negotiation) to verify if HTTP/2 is enabled, which is a requirement for this vulnerability.
MPM Heuristics: Attempts to determine the Multi-Processing Module (MPM) type (prefork vs. event/worker) to assess the risk of Remote Code Execution (RCE) vs. Denial of Service (DoS).
Production Safe: Unlike exploit scripts, this tool only performs version and configuration checks; it does not attempt to crash or compromise the target server.
🚀 Usage Bash python3 scanner.py 📊 Risk Assessment Logic The scanner provides a final risk score based on the following:
CRITICAL (8.8): Apache 2.4.66 is detected and HTTP/2 is enabled.
MEDIUM: HTTP/2 is enabled, but the specific Apache version is hidden or inconclusive.
LOW: HTTP/2 is disabled, meaning the server is not vulnerable to this specific CVE.
🛠 Mitigation Advice If a vulnerability is found, the tool provides immediate actionable steps, such as upgrading to Apache 2.4.67 or disabling mod_http2.
Note: Since the code includes a risk score and specific mitigation commands (like a2dismod http2), including them in your README makes the tool significantly more useful for DevOps and SecOps teams.
