Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25150: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in QwikDev qwik

0
Critical
VulnerabilityCVE-2026-25150cvecve-2026-25150cwe-1321
Published: Tue Feb 03 2026 (02/03/2026, 21:12:50 UTC)
Source: CVE Database V5
Vendor/Project: QwikDev
Product: qwik

Description

CVE-2026-25150 is a critical prototype pollution vulnerability in the Qwik JavaScript framework versions prior to 1. 19. 0. The flaw exists in the formToObj() function of the @builder. io/qwik-city middleware, which improperly handles form field names containing dot notation and fails to sanitize dangerous property names like __proto__, constructor, and prototype. This allows unauthenticated attackers to send crafted HTTP POST requests that modify Object. prototype, potentially leading to privilege escalation, authentication bypass, or denial of service. The vulnerability has a CVSS score of 9. 3, indicating high severity and ease of exploitation without authentication or user interaction. Although no known exploits are currently in the wild, organizations using affected Qwik versions should urgently update to 1.

AI-Powered Analysis

AILast updated: 02/03/2026, 21:44:43 UTC

Technical Analysis

CVE-2026-25150 is a prototype pollution vulnerability identified in the Qwik JavaScript framework, specifically in the formToObj() function within the @builder.io/qwik-city middleware. Qwik is designed for high-performance web applications, and the vulnerable function converts form field names using dot notation (e.g., user.name) into nested JavaScript objects. However, prior to version 1.19.0, this function does not properly sanitize or restrict dangerous property names such as __proto__, constructor, and prototype. Attackers can exploit this by sending specially crafted HTTP POST requests with form fields named to manipulate the Object.prototype, a fundamental JavaScript object from which all objects inherit properties. By polluting Object.prototype, attackers can alter application behavior globally, potentially escalating privileges, bypassing authentication mechanisms, or causing denial of service by corrupting application logic or state. The vulnerability is remotely exploitable without authentication or user interaction, making it highly dangerous. The CVSS v3.1 score of 9.3 reflects the critical nature of this flaw, with network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change that impacts integrity significantly and availability to a lesser extent. Although no public exploits have been reported yet, the widespread use of Qwik in modern web applications means the risk of exploitation is substantial if unpatched. The issue was publicly disclosed and patched in version 1.19.0, and users are strongly advised to upgrade immediately. The vulnerability falls under CWE-1321, which relates to improper control of object prototype attributes, a known vector for severe JavaScript-based attacks.

Potential Impact

For European organizations, the impact of this vulnerability can be severe. Many enterprises and service providers use modern JavaScript frameworks like Qwik to build interactive web applications, including e-commerce platforms, financial services portals, and government websites. Exploitation could allow attackers to escalate privileges within the application, bypass authentication controls, or disrupt service availability, leading to data breaches, fraud, or service outages. This is particularly critical for sectors handling sensitive personal data under GDPR, as unauthorized access or data manipulation could result in regulatory penalties and reputational damage. Additionally, denial of service conditions could affect business continuity and customer trust. The vulnerability’s ease of exploitation without authentication increases the risk of automated attacks and widespread scanning. Organizations with public-facing Qwik-based applications are especially vulnerable, and the cross-cutting nature of prototype pollution means that even indirect impacts on downstream services or integrations could occur. The lack of known exploits currently provides a window for proactive mitigation, but the critical severity necessitates urgent action.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should immediately upgrade all Qwik framework instances to version 1.19.0 or later, where the prototype pollution flaw has been patched. Beyond patching, developers should implement strict input validation and sanitization on all form field names, explicitly disallowing dangerous property names such as __proto__, constructor, and prototype. Web application firewalls (WAFs) can be configured to detect and block suspicious POST requests containing these payloads. Security teams should monitor application logs for anomalous form submissions or unexpected changes in object properties. Conducting code reviews and static analysis focusing on object prototype manipulation can help identify similar risks. Organizations should also consider implementing runtime application self-protection (RASP) solutions to detect and prevent prototype pollution attacks dynamically. Finally, maintaining an inventory of applications using Qwik and integrating vulnerability management processes will ensure timely updates and reduce exposure.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-01-29T15:39:11.821Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 698268e3f9fa50a62fe1ecbe

Added to database: 2/3/2026, 9:30:11 PM

Last enriched: 2/3/2026, 9:44:43 PM

Last updated: 2/4/2026, 12:01:41 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats