# CVE-2026-17639: Certain HP Smart Tank All in One – Potential Denial of Service

> An unauthenticated attacker can cause HP Smart Tank printers to become unavailable by sending multiple concurrent HTTP requests.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-396p-r4hm-g85w

## What is CVE-2026-17639?

CVE-2026-17639 is a medium-severity denial of service vulnerability in HP Smart Tank 210 Printer, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain HP Smart Tank All-in-One printers may be potentially vulnerable to a denial of service condition that allows an unauthenticated attacker to cause the device to become unavailable by sending multiple concurrent HTTP requests.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-17639 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17639 is a medium-severity denial of service vulnerability in HP Smart Tank 210 Printer, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17639 in the wild and no public exploit code.

Affected product: HP Smart Tank 210 Printer. 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-17639/ (Markdown: https://insights.sbomify.com/CVE-2026-17639/index.md)
```

## Sources

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

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