# CVE-2026-106177: HP Sure Click Kernel Buffer Overflow

> A kernel buffer overflow in HP Sure Click allows local attackers to execute arbitrary code or escalate privileges.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-96gh-wj4m-5438

## What is CVE-2026-106177?

CVE-2026-106177 is a medium-severity memory corruption vulnerability in HP Sure Click Enterprise, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A kernel buffer overflow vulnerability in HP Sure Click versions prior to 4.4.33 may allow local privilege escalation or arbitrary code execution. HP has released version 4.4.33 to address this vulnerability.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-106177?


## How do I fix CVE-2026-106177?

No fix has been published for CVE-2026-106177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106177 being exploited?

There is no known exploitation of CVE-2026-106177 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-106177 and fix it if it is affected.

What it is: CVE-2026-106177 is a medium-severity memory corruption vulnerability in HP Sure Click Enterprise, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106177 in the wild and no public exploit code.

Affected product: HP Sure Click Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-106177/ (Markdown: https://insights.sbomify.com/CVE-2026-106177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-106177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-106177
- OSV: https://osv.dev/vulnerability/CVE-2026-106177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-106177/
Summaries are generated and may contain mistakes; the official description above is the record.