# CVE-2026-3291: Samsung Print Service Plugin – Potential Information Disclosure

> An attacker can potentially disclose information via an outdated Samsung Print Service Plugin on Android devices, requiring users to update the application.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-j5hx-w4cq-6522

## What is CVE-2026-3291?

CVE-2026-3291 is a medium-severity vulnerability in HP, Inc Samsung Print Service Plugin, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Samsung Print Service Plugin for Android is potentially vulnerable to information disclosure when using an outdated version of the application via mobile devices. HP is releasing updates to mitigate these potential vulnerabilities.

Weakness: CWE-926 (Improper Export of Android Application Components)

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

It affects 1 product.


Products: Hp Samsung Print Service Plugin.

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

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

## Is CVE-2026-3291 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3291 is a medium-severity vulnerability in HP, Inc Samsung Print Service Plugin, published on 6 May 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-3291 in the wild and no public exploit code.

Affected product: HP, Inc Samsung Print Service Plugin. 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-3291/ (Markdown: https://insights.sbomify.com/CVE-2026-3291/index.md)
```

## Sources

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

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