# CVE-2026-130629: react-native-webview 13.8.0 through 17.1.0 Code Injection via injectedJavaScriptObject


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-w27x-w7q6-r5gm

## What is CVE-2026-130629?

CVE-2026-130629 is a low-severity vulnerability in react-native-webview, published on 17 Nov 2026. 

### Official description

react-native-webview 13.8.0 through 17.1.0 contains a code injection vulnerability that allows attackers to execute JavaScript by placing unescaped backticks or ${} sequences in injectedJavaScriptObject string values. Attackers who control values like profile fields or API responses can break out of the template literal to access the page DOM, non-HttpOnly cookies, and the ReactNativeWebView message bridge.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

1 open source package ship an affected version, including react-native-webview.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `react-native-webview` | npm | `pkg:npm/react-native-webview` | From 13.8.0 to 17.1.0 | None |

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

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

## Is CVE-2026-130629 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130629 is a low-severity vulnerability in react-native-webview, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130629 in the wild and no public exploit code.

Affected packages and fixed versions:
- react-native-webview (npm): affected from 13.8.0 up to 17.1.0; no fix listed

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-130629/ (Markdown: https://insights.sbomify.com/CVE-2026-130629/index.md)
```

## Sources

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

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