dbcve.org
Futuresmart 3Operating system · Hp

CVE-2025-26507

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-14
Fix available
A fix is available. Upgrade to 2309118_002274 / 2309118_002275 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

HP LaserJet printers (Pro, Enterprise, and Managed models) contain a critical vulnerability in PostScript print job processing. A specially crafted malicious PostScript print job can trigger remote code execution and privilege escalation on the affected device, allowing an attacker to gain full control of the printer firmware.

MitigationApply HP firmware patches when released; until then, isolate printers on restricted network segments, disable unnecessary printing protocols, and implement print job authentication where possible.

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 5Operating system
Affected:< 2508402_000067< 2508402_000106< 2508402_000090< 2508125_000009< 2508402_000058< 2508402_000098< 2508402_000072< 2508402_000117< 2508402_000116< 2508402_000089< 2508402_000053< 2508402_000081
Futuresmart 4Operating system
Affected:< 2411278_068111< 2411278_068112< 2411278_068114< 2411278_068113

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 series
    Access the printer's embedded web server (EWS) via its IP address, or print a configuration page from the control panel. Confirm the printer is an HP LaserJet Pro, Enterprise, or Managed model.
    Affected if The printer is not one of these three lines
  2. Determine the Futuresmart firmware version
    In the printer EWS, navigate to the General or Support Information page to find the Futuresmart version (3, 4, or 5). This determines which version range applies.
    Affected if Futuresmart version cannot be determined or is not 3, 4, or 5
  3. Locate the installed firmware version
    In the printer EWS, go to the Firmware Update or General Information section. Record the full firmware version number (for example, a number like those listed in the affected versions).
    Affected if Firmware version cannot be retrieved from the printer
  4. Compare firmware against affected version ranges
    Using the identified Futuresmart version, compare your installed firmware number against the affected version thresholds: Futuresmart 3: < 2309118_002276, _002274, or _002275; Futuresmart 5: < 2508402_000067 or any of the other listed versions; Futuresmart 4: < 2411278_068111, _068112, _068114, or _068113.
    Affected if The installed firmware version is lower than any of the listed thresholds for your Futuresmart version
  5. Verify if PostScript processing is enabled
    In the printer EWS, navigate to the Print Settings or Security settings. Look for a setting related to PostScript, PDL (Page Description Language), or printer language. Check if PostScript is turned on or set to Auto.
    Affected if PostScript is enabled and the firmware version is below the fixed releases

The environment is affected if the printer runs an HP LaserJet Pro, Enterprise, or Managed model with Futuresmart 3, 4, or 5 firmware versions lower than the listed thresholds AND PostScript processing is 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 2309118_002274 / 2309118_002275 / 2309118_002276 or later
Fixed in 2309118_0022742309118_0022752309118_002276
Interim mitigation

Apply HP firmware patches when released; until then, isolate printers on restricted network segments, disable unnecessary printing protocols, and implement print job authentication where possible.

Recommended fix Moderate confidence

HP FutureSmart firmware 2309118 (FS3), 2411278 (FS4), or 2508402/2508125 (FS5) - specific build numbers depend on exact printer model

  1. 1. Identify the specific Futuresmart version running on the HP LaserJet printer (3, 4, or 5).
  2. 2. Navigate to the HP Support website (support.hp.com) and locate the driver/firmware download page for the specific printer model.
  3. 3. Download the latest HP FutureSmart firmware bundle. For Futuresmart 3, look for version 2309118_002276, 2309118_002274, or 2309118_002275 depending on the printer model.
  4. 4. For Futuresmart 4, look for version 2411278_068111, 2411278_068112, 2411278_068114, or 2411278_068113 depending on the printer model.
  5. 5. For Futuresmart 5, look for version 2508402_000067, 2508402_000106, 2508402_000090, or 2508125_000009 depending on the printer model.
  6. 6. Upload and install the firmware through the printer's embedded web server (EWS) or HP Web JetAdmin.
  7. 7. After installation, verify the firmware version matches the expected fixed version.
  8. 8. Restart the printer to ensure the firmware update is fully applied.
Caveat Firmware updates may temporarily interrupt printer operations; ensure print jobs are paused before upgrading

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

Fix this in Futuresmart 3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26507 — 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-26507 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