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-119618---RCE-in-APACHE — Python proof-of-concept for a mod_http2 request-header race condition in Apache HTTP Server, with check, exploit, probe, and mitigation modes plus a minimal HTTP/2 client. | Kitploit
Tools/GitHubGitHub/doseuser/cve-2026-119618---rce-in-apache
Web Vulnerability ScannersVulnerability AnalysisExploitationWeb SecurityFuzzingNetwork Security
GitHubdoseuser/cve-2026-119618---rce-in-apache

CVE-2026-119618---RCE-in-APACHE

Python proof-of-concept for a mod_http2 request-header race condition in Apache HTTP Server, with check, exploit, probe, and mitigation modes plus a minimal HTTP/2 client.

View Repository
5 days agoNot yet reviewed

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.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    627
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    416
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    379
  • 5

    ARTEX

    baarai/artex

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

    330
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    AI powered OSINT engine to discover and map 7,700+ social media identities across the web

    288

Explore all tools

Browse our collection of tools

View all tools →
Share
8a34cc0c-9101-4b06-ba5f-32cf5a5c8a30

CVE-2026-119618 — Apache HTTP Server mod_http2 PoC Research and lab use only. Run this proof of concept only against Apache HTTP Server instances that you own or are explicitly authorized to test. The exploit mode generates concurrent HTTP/2 traffic and may cause service instability or a crash.

Proof-of-concept tooling for investigating a race condition in Apache HTTP Server's mod_http2 request-header handling, in assign_headers(). Overview The issue described by this repository concerns a shared h2_request.headers table associated with an HTTP/2 stream. In the vulnerable code path, assign_headers() may add a synthesized Content-Length: 0 entry to that shared table instead of the request-private r->headers_in table.

Because the stream pool can be accessed by the connection thread and a worker thread, concurrent APR table allocation can race. The resulting behavior may include heap corruption.

The upstream change identified by the PoC is commit 824beab9b9424d6cfb29595248fdbf6c3dddeab1, included in Apache HTTP Server 2.4.71 according to the project notes.

Important: this PoC is designed to detect or reproduce memory-corruption symptoms. A successful corruption result is not, by itself, proof of reliable arbitrary code execution (RCE). Repository contents File Description poc.py Main PoC. Provides check, exploit, probe, and mitigation modes. h2.py Minimal HTTP/2 client and frame/HPACK helpers used by the PoC.

The implementation uses the Python standard library; no third-party Python packages are required. Requirements

  • Python 3.8 or newer.
  • Network access to the test Apache HTTP Server.
  • An isolated, disposable test environment is strongly recommended.
  • For sanitizer-based confirmation, a lab build of Apache httpd instrumented with AddressSanitizer, ThreadSanitizer, or UndefinedBehaviorSanitizer, with its reports and error log available to the PoC. The client speaks cleartext HTTP/2 (h2c). The target must accept HTTP/2 on the selected host and port for the HTTP/2 checks to work. Usage Run commands from the repository directory.
  1. Check mode Performs a non-race functional check and classifies the target based on the observed request behavior and available lab build metadata. python3 poc.py check --target 127.0.0.1:8080
  2. Exploit mode Drives concurrent HTTP/2 request traffic to attempt to reproduce the race. Use only in a controlled lab. python3 poc.py exploit --target 127.0.0.1:8080 Optional parameters: Option Default Purpose --connections 16 Number of parallel HTTP/2 connections. --streams 32 Streams in flight per connection. --duration 20 Traffic-generation duration in seconds. --shape PoC-defined primary shape Request shape used by exploit mode. --fill 78 Filler headers for the bodyless_ct_full shape. --pad 0 Extra bytes appended to the final filler-header value. --logs /lab-logs Directory containing the server error log and sanitizer reports.

For available request shapes and options: python3 poc.py exploit --help 3. Probe mode Exercises additional request shapes that reach related header-handling paths: python3 poc.py probe --target 127.0.0.1:8080 4. Mitigation mode Checks whether the target still accepts HTTP/2. If the HTTP/2 preface is refused, the script reports the mitigation as active. python3 poc.py mitigation --target 127.0.0.1:8080 Target and log configuration The target defaults to 127.0.0.1:8080. It can be supplied with --target or through the TARGET environment variable.

The log directory defaults to /lab-logs. It can be changed with --logs or through the LAB_LOGS environment variable.

For sanitizer-based results, make the target's sanitizer report files (asan., tsan., ubsan.*) and error.log available in that directory. The PoC does not build or instrument Apache httpd itself. Exit codes Code Meaning 0 Safe / not affected, or no corruption observed in the run. 1 Vulnerable behavior detected or corruption confirmed. 2 Target unreachable. 3 Target answered, but the exploit run did not deliver a valid test. 4 Mitigation detected: HTTP/2 is not offered.

Interpret results in context. In particular, “no corruption observed” does not prove that a target is not vulnerable; race conditions can be timing-dependent. Mitigation The workaround documented in the PoC is to disable HTTP/2 for the affected virtual host/server by removing h2 and h2c from the Apache Protocols directive, then validate the configuration and reload Apache according to the deployment's change procedure.

The preferred remediation is to upgrade to a vendor-supported Apache HTTP Server release that contains the upstream fix, and verify the package/version supplied by your operating-system vendor. Technical notes

  • The helper client implements the subset of HTTP/2 framing and HPACK needed by this PoC.
  • The PoC uses request shapes involving Content-Type without Content-Length.
  • Sanitizer reports are inspected to distinguish reports associated with assign_headers() from unrelated findings.
  • A target crash or sanitizer finding should be preserved with the corresponding server logs and build details for analysis. Disclaimer This repository is provided for vulnerability research, defensive validation, and controlled testing. The author and contributors assume no responsibility for damage, disruption, or unauthorized use. Obtain written authorization before testing systems you do not own.
Download Tool