# CVE-2026-78178: jQWidgets jqx-all.js jqxBaseFramework.extend prototype pollution

> Remote attackers can exploit prototype pollution in jQWidgets to achieve code execution, though the vendor has marked the issue as not planned for fixing.

- **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:** 27 Aug 2026
- **Also known as:** GHSA-hhpq-pm9g-crh9

## What is CVE-2026-78178?

CVE-2026-78178 is a medium-severity code injection vulnerability in jQWidgets, 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 vulnerability was determined in jQWidgets up to 24.0.1. This affects the function JQXLite.extend/jqxBaseFramework.extend of the file jqwidgets/jqx-all.js. This manipulation causes improperly controlled modification of object prototype attributes. The attack can be initiated remotely. The reported GitHub issue was closed with the label "not planned".

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-78178?


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

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

## Is CVE-2026-78178 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78178 is a medium-severity code injection vulnerability in jQWidgets, published on 24 Aug 2026. 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-2026-78178 in the wild and no public exploit code.

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

## Sources

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

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