CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:NCVE-2026-123808 Nuxt UI: UAuthForm / UForm SSR markup omits `method`, leaking credentials via GET if submitted before hydration
Medium (5.3) in nuxt ui. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @nuxt/ui 4.8.1.
On this page
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-598 Use of HTTP Request With Sensitive Query String - OWASP Top 10
- A01:2025 Broken Access Control, A06:2025 Insecure Design
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123808 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123808?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123808?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123808 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-123808)
HTML:
<a href="https://cve.bz/cve/CVE-2026-123808"><img src="https://cve.bz/cve/badge/CVE-2026-123808.svg" alt="CVE-2026-123808"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nuxt ui | < 4.8.1 |
Fix and patched versions
@nuxt/ui(npm): fixed in 4.8.1
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-gj2h-2fpw-fhv9 | npm | @nuxt/ui | <4.8.1 | 4.8.1 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).