PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-42626 HP CVE debrief

CVE-2026-42626 details a Denial of Service (DoS) vulnerability in HP ENVY 5000 series printers, specifically VERBASPP1N003.2237A.00. An unauthenticated remote attacker on the same network can establish a persistent connection to port 9100 (JetDirect/RAW printing) 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 DoS that renders the printer unresponsive to all user commands and print jobs. Physical intervention (manual restart) is required to restore functionality. The vulnerability has a CVSS score of 5.9 and is considered Medium severity. Organizations should prioritize patching to prevent potential disruptions.

Vendor
HP
Product
ENVY 5000 series printers
CVSS
MEDIUM 5.9
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-22
Original CVE updated
2026-07-23
Advisory published
2026-05-22
Advisory updated
2026-07-23

Who should care

Organizations using HP ENVY 5000 series printers should prioritize patching this vulnerability to prevent potential disruptions. Network administrators and security teams responsible for printer management should be aware of this issue and take necessary precautions.

Technical summary

The HP ENVY 5000 series printers, specifically 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.

Defensive priority

Medium priority should be given to patching this vulnerability, as it can cause significant disruptions to printing services.

Recommended defensive actions

  • Apply the vendor-provided patch or firmware update to address the vulnerability.
  • Implement network segmentation to limit the attack surface.
  • Monitor printer logs for suspicious activity.
  • Consider disabling JetDirect/RAW printing if not necessary.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record was published on 2026-05-22T17:16:47.500Z and was last modified on 2026-07-23T16:10:00.137Z. The NVD entry is currently Awaiting Analysis. Limited details are available about the affected scope and vendor remediation efforts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-42626 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-42626

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-42626 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-42626

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://medium.com/@jacobmasse/hp-envy-5000-printer-dos-vulnerability-8cae52c87b41

    [email protected]

  • Source reference

    Unverified legacy reference

    URL: https://jacobmasse.medium.com/hp-envy-5000-printer-dos-vulnerability-8cae52c87b41

    134c704f-9b21-4f2e-91b3-4a467353bcc0

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.