# CVE-2025-8083: Vuetify Prototype Pollution via Preset options

> Prototype pollution in Vuetify allows attackers to inject properties into JavaScript objects, potentially causing denial of service or data exposure.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Dec 2025
- **Updated:** 12 Dec 2025
- **Also known as:** CLSA-2026-1775176071, GHSA-3jp5-5f8r-q2wg, ROOT-APP-NPM-CVE-2025-8083

## What is CVE-2025-8083?

CVE-2025-8083 is a high-severity code injection vulnerability in Vuetify, published on 12 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The  Preset configuration https://v2.vuetifyjs.com/en/features/presets  feature of Vuetify is vulnerable to  Prototype Pollution https://cheatsheetseries.owasp.org/cheatsheets/Prototype_Pollution_Prevention_Cheat_Sheet.html  due to the internal 'mergeDeep' utility function used to merge options with defaults. Using a specially-crafted, malicious preset can result in polluting all JavaScript objects with arbitrary properties, which can further negatively affect all aspects of the application's behavior. This can lead to a wide range of security issues, including resource exhaustion/denial of service or unauthorized access to data.

If the application utilizes Server-Side Rendering (SSR), this vulnerability could affect the whole server process.

This issue affects Vuetify versions greater than or equal to 2.2.0-beta.2 and less than 3.0.0-alpha.10.

Note:
Version 2.x of Vuetify is End-of-Life and will not receive any updates to address this issue. For more information see  here https://v2.vuetifyjs.com/en/about/eol/ .

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-8083?

2 open source packages ship an affected version, including vuetify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vuetify` | npm | From 2.2.0-beta.2 | 3.0.0-alpha.10 |
| `vuetify` | npm | From 2.2.0-beta.2 | 3.0.0-alpha.10 |

## How do I fix CVE-2025-8083?

Upgrade vuetify to 3.0.0-alpha.10 or later.

## Is CVE-2025-8083 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8083 and fix it if it is affected.

What it is: CVE-2025-8083 is a high-severity code injection vulnerability in Vuetify, published on 12 Dec 2025. 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-2025-8083 exists.

Affected packages and fixed versions:
- vuetify (npm): affected from 2.2.0-beta.2; fixed in 3.0.0-alpha.10
- vuetify (npm): affected from 2.2.0-beta.2; fixed in 3.0.0-alpha.10

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

## Sources

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

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