# CVE-2026-24474: Dioxus Components has JavaScript injection via user-supplied IDs

> Attackers can execute arbitrary JavaScript in Dioxus applications by supplying malicious IDs to the use_animated_open hook.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jan 2026
- **Updated:** 26 Jan 2026
- **Also known as:** GHSA-34pj-292j-xr69

## What is CVE-2026-24474?

CVE-2026-24474 is a medium-severity code injection vulnerability in DioxusLabs components, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Dioxus Components is a shadcn-style component library for the Dioxus app framework. Prior to commit 41e4242ecb1062d04ae42a5215363c1d9fd4e23a, `use_animated_open` formats a string for `eval` with an `id` that can be user supplied. Commit 41e4242ecb1062d04ae42a5215363c1d9fd4e23a patches the issue.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2026-24474 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24474 is a medium-severity code injection vulnerability in DioxusLabs components, published on 23 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-24474 in the wild and no public exploit code.

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

## Sources

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

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