Universal Print DriverApplication · Hp

CVE-2025-43025

HIGH · 7.5 CVSS v3.1 Published 2025-07-02
Fix available
A fix is available. Upgrade to 61.330.01.26178 or later.
See remediation →
84/100
Remediation priority · High
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
HP Universal Print Driver is potentially vulnerable to denial of service due to buffer overflow in versions of UPD 7.4 or older (e.g., v7.3.x, v7.2.x, v7.1.x, etc.).

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 confidence

Buffer overflow vulnerability in HP Universal Print Driver versions 7.4 and older allows remote attackers to cause denial of service. The CVSS 7.5 score indicates network-exploitable attack vector with low complexity and no authentication required.

MitigationUpgrade HP Universal Print Driver to a version newer than 7.4. If immediate upgrade is not feasible, restrict network access to print services via firewall or network segmentation to reduce attack surface.

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
Universal Print DriverApplication
Affected:< 61.330.01.26178

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Verify HP Universal Print Driver is installed
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*HP Universal Print Driver*'}
    Affected if HP Universal Print Driver appears in the installed programs list
  2. Retrieve the installed version number
    In Programs and Features, click on HP Universal Print Driver to view the version, or use: (Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*HP Universal Print Driver*'}).Version
    Affected if The version displayed is 7.4 or older, or shows a build number lower than 61.330.01.26178
  3. Confirm print spooler service is running
    Open Services console (services.msc) and locate Print Spooler, or run: Get-Service Spooler
    Affected if Print Spooler service status is Running and the vulnerable driver is loaded
  4. Check if print services are network-accessible
    Verify the printer ports are bound to network interfaces. In Windows, check Printer Properties > Ports, or run: Get-PrinterPort | Where-Object {$_.Type -eq 'Local' -and $_.Name -notlike 'COM*'}; also verify firewall rules allow print traffic (ports 139, 445, 631)
    Affected if Print services are listening on accessible network interfaces, enabling remote exploitation

You are affected if HP Universal Print Driver version 7.4 or older (below build 61.330.01.26178) is installed and the print service is operational and network-accessible.

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 61.330.01.26178 or later
Fixed in 61.330.01.26178
Interim mitigation

Upgrade HP Universal Print Driver to a version newer than 7.4. If immediate upgrade is not feasible, restrict network access to print services via firewall or network segmentation to reduce attack surface.

Recommended fix High confidence

61.330.01.26178 or later

  1. Navigate to HP support website (support.hp.com) and search for HP Universal Print Driver
  2. Download HP Universal Print Driver version 61.330.01.26178 or later
  3. Uninstall the current version of HP Universal Print Driver from all affected systems
  4. Install the updated version (61.330.01.26178 or newer) on all systems that previously had the vulnerable version
  5. Restart print services or reboot systems if prompted to complete the update

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

Fix this in Universal Print Driver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43025 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