CVE-2026-119618

validatingZero is analyzing and reversing it now.

GHSA-hjhf-gpg9-qqfj ↗EUVD-2026-123532 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache HTTP Server
ETK-2026-4183Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache HTTP Server versions 2.4.55 through 2.4.70 are affected when using mod_http2 versions 2.0.8 through 2.0.42. The flaw may permit remote code execution through the HTTP/2 module. The advisory does not state authentication or other access prerequisites; treat systems serving HTTP/2 with affected versions as potentially exposed.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Disable mod_http2 or HTTP/2 where it is not required, and restrict exposure to affected servers. Upgrade beyond the affected versions after confirming the selected Apache HTTP Server release includes the vendor's remediation; the supplied evidence does not name a fixed version.

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 14:54Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 14:54Z
    ghsa: trigger signal, started the run
  2. 2026-11-11 14:54Z

this entry in the feed

GET /api/v1/feed/CVE-2026-119618

{
  "etk_id": "ETK-2026-4183",
  "cve_id": "CVE-2026-119618",
  "display_id": "CVE-2026-119618",
  "ghsa_id": "GHSA-hjhf-gpg9-qqfj",
  "euvd_id": "EUVD-2026-123532",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Race condition in Apache HTTP Server mod_http2",
  "summary": "Apache HTTP Server versions 2.4.55 through 2.4.70 are affected when using mod_http2 versions 2.0.8 through 2.0.42. The flaw may permit remote code execution through the HTTP/2 module. The advisory does not state authentication or other access prerequisites; treat systems serving HTTP/2 with affected versions as potentially exposed.",
  "mitigation": "Disable mod_http2 or HTTP/2 where it is not required, and restrict exposure to affected servers. Upgrade beyond the affected versions after confirming the selected Apache HTTP Server release includes the vendor's remediation; the supplied evidence does not name a fixed version.",
  "vendor": "Apache Software Foundation",
  "product": "Apache HTTP Server",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-11T14:54:08.155000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T14:54:08.155000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T14:54:08.155000+00:00",
      "url": "https://github.com/advisories/GHSA-hjhf-gpg9-qqfj"
    }
  }
}

published 2026-11-11 15:57Z
last change 2026-11-11 16:16Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.