# CVE-2026-123808: Nuxt UI: UAuthForm / UForm SSR markup omits `method`, leaking credentials via GET if submitted before hydration


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-gj2h-2fpw-fhv9

## What is CVE-2026-123808?

CVE-2026-123808 is a medium-severity vulnerability in nuxt ui, published on 9 Nov 2026. 

### Official description

Nuxt UI is an intuitive Vue UI library powered by Reka UI and Tailwind CSS. Prior to 4.8.1, the server-rendered form element produced by UForm in src/runtime/components/Form.vue omits the method and action attributes and relies solely on the hydrated @submit.prevent handler to stop native submission. UAuthForm composes UForm and can render named credential fields, including an input with type password, inside the same markup. If a user submits before Vue hydration completes, or when the client bundle is blocked or unavailable, the browser performs its default GET submission and serializes the named fields into the current URL query string. The credentials can then appear in the address bar, browser history, reverse-proxy, CDN, or WAF request logs, and Referer headers sent with same-origin subresource requests. This issue is fixed in version 4.8.1.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

1 open source package ship an affected version, including @nuxt/ui.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@nuxt/ui` | npm | All versions | 4.8.1 |

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

Upgrade @nuxt/ui to 4.8.1 or later.

## Is CVE-2026-123808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123808 is a medium-severity vulnerability in nuxt ui, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123808 in the wild and no public exploit code.

Affected packages and fixed versions:
- @nuxt/ui (npm): affected all versions; fixed in 4.8.1

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

## Sources

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

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