CVE-2026-42626
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHP 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHP ENVY 5000 series printers with firmware VERBASPP1N003.2237A.00 lack proper TCP connection management for port 9100 (JetDirect/RAW printing). An unauthenticated attacker on the local network can establish persistent connections with keep-alive packets that lock session threads in waiting state indefinitely. The firmware includes no connection timeouts or concurrent session limits, causing a permanent DoS that requires manual printer restart.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the printer modelAccess the printer's web interface or print a configuration page to confirm the model is HP ENVY 5000 seriesAffected if The printer model is not an HP ENVY 5000 series device, then this CVE does not apply
-
Check the firmware versionPrint a configuration page or access the printer's embedded web server to view the firmware versionAffected if The firmware version matches VERBASPP1N003.2237A.00; if the version is different or unknown, compare to the affected version and check vendor release notes for updates
-
Verify port 9100 accessibilityUse a network scanner or run 'telnet <printer-ip> 9100' or 'nc -zv <printer-ip> 9100' from a client on the same network to confirm the JetDirect port is open and reachableAffected if Port 9100 is open and responds to connection attempts, indicating the vulnerable service is exposed
-
Assess network exposureReview network configuration to determine if the printer is accessible from untrusted network segments or the internet; check firewall rules and VLAN placementAffected if Port 9100 is reachable from untrusted network segments, guest networks, or the internet without proper access controls
A user is affected if they have an HP ENVY 5000 series printer running firmware VERBASPP1N003.2237A.00 with port 9100 exposed to untrusted or untrusted network segments.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataContact HP for available firmware updates addressing this vulnerability. Implement network segmentation and access controls to restrict port 9100 access to trusted hosts only, as a compensating control until vendor firmware patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data