# CVE-2016-1656: Path traversal in n/a

> Remote attackers can bypass pathname restrictions in the Chrome Android download implementation, potentially accessing restricted files.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g375-749q-973m, UBUNTU-CVE-2016-1656

## What is CVE-2016-1656?

CVE-2016-1656 is a high-severity path traversal vulnerability in Google Chrome, published on 18 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The download implementation in Google Chrome before 50.0.2661.75 on Android allows remote attackers to bypass intended pathname restrictions via unspecified vectors.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


Products: Google Chrome, Opensuse Leap, Suse Linux Enterprise.

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

Upgrade to a fixed version.

## Is CVE-2016-1656 being exploited?

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

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1656 is a high-severity path traversal vulnerability in Google Chrome, published on 18 Apr 2016. 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-2016-1656 in the wild and no public exploit code.

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

## Sources

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

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