dbcve.org
Futuresmart 3Operating system · Hp

CVE-2025-26508

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-14
Fix available
A fix is available. Upgrade to 6.17.5.34-202412122146 / 2309118_002274 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

Certain HP LaserJet Pro, Enterprise, and Managed Printers contain a vulnerability when processing PostScript print jobs, allowing remote code execution and elevation of privilege. The attack vector is through malicious PostScript data sent to the print service, potentially giving attackers full control over the printer firmware.

MitigationApply vendor-released firmware updates for affected HP LaserJet models. Until patches are available, consider network segmentation of printers, disabling PostScript printing if not required, and implementing print job authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Futuresmart 3Operating system
Affected:< 2309118_002276< 2309118_002274< 2309118_002275
Futuresmart 4Operating system
Affected:< 2411278_068111< 2411278_068112< 2411278_068114< 2411278_068113
Futuresmart 5Operating system
Affected:< 2508402_000090< 2508125_000009< 2508402_000058< 2508402_000098< 2508402_000106< 2508402_000072< 2508402_000067< 2508402_000117< 2508402_000116< 2508402_000089< 2508402_000111< 2508402_000172
499m7a FirmwareOperating system
Affected:< 6.17.5.34-202412122146
499m8a FirmwareOperating system
Affected:< 6.17.5.34-202412122146
499m9a FirmwareOperating system
Affected:< 6.17.5.34-202412122146
499n0a FirmwareOperating system
Affected:< 6.17.5.34-202412122146
499n1a FirmwareOperating system
Affected:< 6.17.5.34-202412122146

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify printer model and firmware version
    Access the printer web interface (embedded web server) or print a configuration page. Navigate to the General or Information tab to view the product name and firmware version. For command-line access, use SNMP or HP Web Jetadmin to query the device.
    Affected if The printer model is an HP LaserJet Pro, Enterprise, or Managed Printer running Futuresmart 3, 4, or 5, or firmware 499m7a/499m8a/499m9a/499n0a/499n1a.
  2. Compare firmware version against affected Futuresmart 3 versions
    Locate the firmware version string in the printer settings. For Futuresmart 3, compare it against: 2309118_002276, 2309118_002274, 2309118_002275. The printer is vulnerable if the installed version is lower than any of these three values.
    Affected if Futuresmart 3 version is less than 2309118_002276, 2309118_002274, or 2309118_002275.
  3. Compare firmware version against affected Futuresmart 4 versions
    Locate the firmware version string in the printer settings. For Futuresmart 4, compare it against: 2411278_068111, 2411278_068112, 2411278_068114, 2411278_068113. The printer is vulnerable if the installed version is lower than any of these four values.
    Affected if Futuresmart 4 version is less than 2411278_068111, 2411278_068112, 2411278_068114, or 2411278_068113.
  4. Compare firmware version against affected Futuresmart 5 versions
    Locate the firmware version string in the printer settings. For Futuresmart 5, compare it against: 2508402_000090, 2508125_000009, 2508402_000058, 2508402_000098, 2508402_000106, 2508402_000072, 2508402_000067, 2508402_000117, 2508402_000116, 2508402_000089, 2508402_000111, 2508402_000172. The printer is vulnerable if the installed version is lower than any of these twelve values.
    Affected if Futuresmart 5 version is less than any of the twelve listed version numbers.
  5. Compare firmware version against affected 499mXa versions
    For models 499m7a, 499m8a, 499m9a, 499n0a, and 499n1a, locate the firmware version in the printer web interface or configuration page. Compare against: 6.17.5.34-202412122146. The printer is vulnerable if the installed version string is lexicographically or numerically lower than this value.
    Affected if Firmware version is less than 6.17.5.34-202412122146 on models 499m7a, 499m8a, 499m9a, 499n0a, or 499n1a.
  6. Verify if PostScript printing is enabled
    Access the printer web interface and navigate to the Print Settings or Device Settings section. Look for PostScript, PS, or Adobe PostScript settings. Check whether PostScript printing is enabled or set to Auto. Alternatively, print a configuration page and look for PostScript in the installed languages list.
    Affected if PostScript printing is enabled or set to Auto, making the printer vulnerable to malicious PostScript-based exploitation.

The printer is affected if it is an HP LaserJet Pro, Enterprise, or Managed Printer running a firmware version lower than the specified thresholds AND has PostScript printing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 6.17.5.34-202412122146 / 2309118_002274 / 2309118_002275 or later
Fixed in 6.17.5.34-2024121221462309118_0022742309118_002275
Interim mitigation

Apply vendor-released firmware updates for affected HP LaserJet models. Until patches are available, consider network segmentation of printers, disabling PostScript printing if not required, and implementing print job authentication.

Recommended fix High confidence

Futuresmart 3: 2309118_002276 or higher; Futuresmart 4: 2411278_068111 or higher; Futuresmart 5: 2508402_000090 or higher; 499m7a/499m8a/499m9a/499n0a/499n1a: 6.17.5.34-202412122146 or higher

  1. Identify the current firmware version of the HP LaserJet printer by accessing the printer's embedded web server or control panel
  2. Determine the Futuresmart generation (3, 4, or 5) or the specific firmware model (499m7a, 499m8a, 499m9a, 499n0a, or 499n1a) from the product documentation or printer display
  3. Navigate to HP Support (support.hp.com) and locate the specific printer model firmware download page
  4. Download the latest firmware version that meets or exceeds the fixed version thresholds: Futuresmart 3: >= 2309118_002276/002274/002275; Futuresmart 4: >= 2411278_068111/068112/068113/068114; Futuresmart 5: >= 2508402_000090/000009/000058/000098; 499mX/499nX firmware: >= 6.17.5.34-202412122146
  5. Access the printer's administration web interface and locate the Firmware Update or Device Maintenance section
  6. Upload and install the downloaded firmware file following the on-screen instructions
  7. After the firmware update completes, verify the new version is installed correctly
  8. Restart the printer if prompted and confirm normal operation
Caveat Firmware updates may temporarily interrupt printer availability; verify compatibility with existing print workflows before deploying in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Futuresmart 3 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation10.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,620
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-26508 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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