# CVE-2026-78180: alibaba-fusion next deepMerge index.tsx ConfigProvider.getContextProps prototype pollution

> Prototype pollution in Alibaba Fusion Next allows remote attackers to modify object prototypes, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-8mfc-fm4w-pgff

## What is CVE-2026-78180?

CVE-2026-78180 is a medium-severity code injection vulnerability in alibaba-fusion next, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in alibaba-fusion next up to 1.27.34. This issue affects the function ConfigProvider.getContextProps of the file components/dialog/index.tsx of the component deepMerge. Performing a manipulation of the argument locale results in improperly controlled modification of object prototype attributes. The attack may be initiated remotely. The reported GitHub issue was closed automatically due to inactivity.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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


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

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

## Is CVE-2026-78180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78180 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78180 is a medium-severity code injection vulnerability in alibaba-fusion next, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-78180 exists.

Affected product: alibaba-fusion next. 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-78180/ (Markdown: https://insights.sbomify.com/CVE-2026-78180/index.md)
```

## Sources

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

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