Linux Imaging And PrintingApplication · Hp

CVE-2026-8631

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-20
Fix available
A fix is available. Upgrade to 3.26.4 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
A potential security vulnerability has been identified in the HP Linux Imaging and Printing Software. This potential vulnerability may allow escalation of privileges and/or arbitrary code execution via an integer overflow in the hpcups processing path when handling crafted print data.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 3mo ago

Surfaced from public web coverage — external links open in a new tab.

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

An integer overflow vulnerability exists in the hpcups processing path of HP Linux Imaging and Printing Software when handling crafted print data. This can lead to privilege escalation or arbitrary code execution with high severity (CVSS 9.8).

MitigationApply vendor patches for HP Linux Imaging and Printing Software. As an interim measure, restrict access to printing services or disable the hpcups component until patching can be completed.

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
Linux Imaging And PrintingApplication
Affected:< 3.26.4

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. Check if HP Linux Imaging and Printing is installed
    On RHEL/CentOS: rpm -q hplip. On Debian/Ubuntu: dpkg -l hplip. On any system: which hp-info or which hpcups
    Affected if The package or binaries are not found, meaning the product is not installed and not affected
  2. Determine the installed version
    Run: rpm -q --queryformat '%{VERSION}.%{RELEASE}' hplip (RHEL) or dpkg -s hplip | grep Version (Debian). Alternatively: hp-info -v 2>/dev/null | grep -i version
    Affected if The version number returned is less than 3.26.4 (e.g., 3.24.5, 3.25.0, etc.)
  3. Verify the hpcups component is present
    Check for the hpcups binary: which hpcups or find /usr -name 'hpcups' 2>/dev/null. Also check CUPS printer configuration: lpstat -t
    Affected if The hpcups binary exists and CUPS printing is configured or active
  4. Confirm CUPS printing service is enabled
    Check CUPS service status: systemctl status cups (systemd) or service cups status (SysV). Also check if any printers are defined in /etc/cups/printers.conf
    Affected if CUPS service is running and printers are configured, making the hpcups processing path active

A system is affected if HP Linux Imaging and Printing (hplip) version 3.26.4 or higher is NOT installed AND the hpcups component with CUPS printing is enabled and in use.

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

Apply vendor patches for HP Linux Imaging and Printing Software. As an interim measure, restrict access to printing services or disable the hpcups component until patching can be completed.

Recommended fix High confidence

HP Linux Imaging and Printing (HPLIP) version 3.26.4 or later

  1. 1. Identify the current installed version of HP Linux Imaging and Printing (HPLIP) on the system
  2. 2. If the installed version is earlier than 3.26.4, download and install HPLIP version 3.26.4 or later from the official HP support website (support.hp.com) or your distribution's package repository
  3. 3. Restart the CUPS printing service after upgrade: sudo systemctl restart cups
  4. 4. Verify the installed version is 3.26.4 or later: hp-check -v or check the package version

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

Fix this in Linux Imaging And Printing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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