# CVE-2026-119723: Denial of service in HHVM

> Unauthenticated attackers can crash HHVM servers with crafted nested array request variables.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-cr6x-jqxp-2v2p

## What is CVE-2026-119723?

CVE-2026-119723 is a denial of service vulnerability in Facebook HHVM, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When parsing request variables such as query-string and form parameters, HHVM did not check that appending a nested array succeeded before descending into it. A remote, unauthenticated attacker could send a GET or POST request which would crash the HHVM server process before any application code runs, leading to denial of service. This issue affected HHVM prior to 23c061f4e804a51badd5f85227e65185651253b5.

## Which versions are affected by CVE-2026-119723?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-119723?

No fix has been published for CVE-2026-119723 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119723 being exploited?

There is no known exploitation of CVE-2026-119723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119723 and fix it if it is affected.

What it is: CVE-2026-119723 is a denial of service vulnerability in Facebook HHVM, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-119723 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Facebook HHVM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119723/ (Markdown: https://insights.sbomify.com/CVE-2026-119723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119723
- OSV: https://osv.dev/vulnerability/CVE-2026-119723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119723/
Summaries are generated and may contain mistakes; the official description above is the record.