# CVE-2016-3916: Privilege escalation in n/a

> Attackers can gain privileges via a crafted application exploiting a flaw in the Android Camera service.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f4cv-f6h5-c5j9, UBUNTU-CVE-2016-3916

## What is CVE-2016-3916?

CVE-2016-3916 is a high-severity vulnerability in Google Android, published on 10 Oct 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

camera/src/camera_metadata.c in the Camera service in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, 6.x before 2016-10-01, and 7.0 before 2016-10-01 allows attackers to gain privileges via a crafted application, aka internal bug 30741779.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2016-3916?

It affects 1 product.


Products: Google Android.

## How do I fix CVE-2016-3916?

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

## Is CVE-2016-3916 being exploited?

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

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3916 and fix it if it is affected.

What it is: CVE-2016-3916 is a high-severity vulnerability in Google Android, published on 10 Oct 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-3916 in the wild and no public exploit code.

Affected product: Google Android. 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-2016-3916/ (Markdown: https://insights.sbomify.com/CVE-2016-3916/index.md)
```

## Sources

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

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