CVE-2026-119723

validatingZero is analyzing and reversing it now.

GHSA-cr6x-jqxp-2v2p ↗EUVD-2026-123609 ↗

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.
Facebook HHVM
fixed in 23c061f4e804a51badd5f85227e65185651253b5
ETK-2026-4194Zero'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

HHVM releases before 23c061f4e804a51badd5f85227e65185651253b5 mishandle certain nested HTTP request parameters. A remote unauthenticated attacker can cause the HHVM server process to terminate before the hosted application handles the request, provided they can send GET or POST requests to the service.

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

mitigation

Upgrade HHVM to a release containing 23c061f4e804a51badd5f85227e65185651253b5. Until upgraded, restrict untrusted access to endpoints served by HHVM where feasible.

fixed in 23c061f4e804a51badd5f85227e65185651253b5

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 16:57Z
Δ 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 16:57Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4194",
  "cve_id": "CVE-2026-119723",
  "display_id": "CVE-2026-119723",
  "ghsa_id": "GHSA-cr6x-jqxp-2v2p",
  "euvd_id": "EUVD-2026-123609",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Unauthenticated request parsing denial of service in HHVM",
  "summary": "HHVM releases before 23c061f4e804a51badd5f85227e65185651253b5 mishandle certain nested HTTP request parameters. A remote unauthenticated attacker can cause the HHVM server process to terminate before the hosted application handles the request, provided they can send GET or POST requests to the service.",
  "mitigation": "Upgrade HHVM to a release containing 23c061f4e804a51badd5f85227e65185651253b5. Until upgraded, restrict untrusted access to endpoints served by HHVM where feasible.",
  "vendor": "Facebook",
  "product": "HHVM",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 23c061f4e804a51badd5f85227e65185651253b5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "23c061f4e804a51badd5f85227e65185651253b5"
      ],
      "package_name": "HHVM",
      "purl": null
    }
  ],
  "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-11T16:57:01.125000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T16:57:01.125000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T16:57:01.125000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119723"
    }
  }
}

published 2026-11-11 17:33Z
last change 2026-11-11 18:28Z

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.