# CVE-2026-42626: Denial of service in n/a

> An unauthenticated remote attacker can cause a persistent denial of service on HP ENVY printers by exhausting session threads via TCP connections.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2026
- **Updated:** 22 May 2026
- **Also known as:** GHSA-wghp-f8qf-wg62

## What is CVE-2026-42626?

CVE-2026-42626 is a medium-severity denial of service vulnerability in n/a, published on 22 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HP ENVY 5000 series printers VERBASPP1N003.2237A.00 do not properly manage concurrent TCP connections to port 9100 (JetDirect/RAW printing). An unauthenticated remote attacker on the same network can establish a persistent connection to port 9100 and send keep-alive packets, causing the printer's session threads to remain locked in a waiting state. The firmware lacks connection timeouts and concurrent session limits, resulting in a persistent Denial of Service (DoS) that renders the printer unresponsive to all user commands and print jobs. Physical intervention (manual restart) is required to restore functionality, and the attack can be immediately re-initiated.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-42626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42626 is a medium-severity denial of service vulnerability in n/a, published on 22 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42626 in the wild and no public exploit code.

Affected product: n/a. 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-42626/ (Markdown: https://insights.sbomify.com/CVE-2026-42626/index.md)
```

## Sources

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

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