# CVE-2026-33966: Information disclosure in Exynos 1330 firmware

> An attacker can leak sensitive information from the camera driver due to debug code insertion in Samsung Exynos processors.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-6hw8-32rp-r4vx

## What is CVE-2026-33966?

CVE-2026-33966 is a low-severity vulnerability in Samsung Exynos 1330 firmware, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in camera in Samsung Mobile Processor Exynos 1330, 1380, 1480, 2400, 1580, 2500, 2600, and 1680. An information Leak occurs in the camera driver due to Insertion of Sensitive Information Into Debugging Code.

Weakness: CWE-215 (Insertion of Sensitive Information Into Debugging Code)

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


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

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

## Is CVE-2026-33966 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33966 is a low-severity vulnerability in Samsung Exynos 1330 firmware, published on 14 Sep 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-33966 in the wild and no public exploit code.

Affected product: Samsung Exynos 1330 firmware. 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-33966/ (Markdown: https://insights.sbomify.com/CVE-2026-33966/index.md)
```

## Sources

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

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