CyberSecBulletin
CVE-2025-26508NVD status: Analyzed

Certain HP LaserJet Pro, HP LaserJet…: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2025-26508 is a critical-severity out-of-bounds write vulnerability in Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers from HP, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers versions: See HP security bulletin reference for affected versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.97% chance of exploitation within 30 days, higher than 62% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Futuresmart 3 to 2309118_002276 or 2309118_002274 or 2309118_002275, whichever matches your release line, or a later version.
  2. Update Futuresmart 4 to 2411278_068111 or 2411278_068112 or 2411278_068114 or 2411278_068113, whichever matches your release line, or a later version.
  3. Update Futuresmart 5 to 2508402_000090 or 2508125_000009 or 2508402_000058 or 2508402_000098, whichever matches your release line, or a later version.
  4. Read the advisory on support.hp.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
HPCertain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed PrintersSee HP security bulletin reference for affected versionsNot stated
HPFuturesmart 3before 2309118_002276; before 2309118_002274; before 2309118_0022752309118_002276, 2309118_002274, 2309118_002275
HPFuturesmart 4before 2411278_068111; before 2411278_068112; before 2411278_068114; before 2411278_0681132411278_068111, 2411278_068112, 2411278_068114, 2411278_068113
HPFuturesmart 5before 2508402_000090; before 2508125_000009; before 2508402_000058; before 2508402_000098; before 2508402_000106; before 2508402_000072; before 2508402_000067; before 2508402_000117; and 32 more ranges2508402_000090, 2508125_000009, 2508402_000058, 2508402_000098, 2508402_000106, 2508402_000072
HP499m7a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499m8a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499m9a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499n0a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499n1a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499n4a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499n5a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499n6a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q3a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q3e Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q3f Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q4e Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q4f Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q5a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q5e Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q5f Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q5fr Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q6a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q6e Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q6f Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146
HP499q7a Firmwarebefore 6.17.5.34-2024121221466.17.5.34-202412122146

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.3HighCNA (hp.com)
CVSS 3.19.8CriticalNVD

Official description

Certain HP LaserJet Pro, HP LaserJet Enterprise, and HP LaserJet Managed Printers may potentially be vulnerable to Remote Code Execution and Elevation of Privilege when processing a PostScript print job.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers

All Certain HP LaserJet Pro, HP LaserJet Enterprise, HP LaserJet Managed Printers vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.