mXSS Vulnerability in @builder.io/qwik
Summary
CVE-2024-41677: Qwik has a potential mXSS vulnerability due to improper HTML escaping. Affects @builder.io/qwik versions < 1.7.3. Fixed in 1.7.3. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @builder.io/qwik package is an npm package that provides functionality for building web components. It is commonly used for server-side rendering and handling user input. The package is vulnerable to a potential mXSS (mutation XSS) vulnerability due to improper HTML escaping.
Vulnerability Detail
The vulnerability in @builder.io/qwik arises from the improper HTML escaping performed during server-side rendering. This can lead to a situation where the final DOM tree rendered on browsers differs from what is expected on the server-side. This discrepancy can be leveraged to perform XSS attacks, specifically mXSS. An attacker could inject malicious code that would be executed when the vulnerable component is rendered on the client-side.
How To Fix
Latest published version: 1.20.2 as of 23 Oct 2026
npm install @builder.io/qwik@1.20.2Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
1.7.3
This is the first release that contains the fix.
npm install @builder.io/qwik@1.7.3Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
If updating to the latest version is not immediately possible, a temporary workaround can be implemented by manually sanitizing user input before using it in the vulnerable component. This can be done using a library like DOMPurify to sanitize the input and prevent any potential XSS attacks.
Conclusion
The @builder.io/qwik package is vulnerable to a potential mXSS vulnerability due to improper HTML escaping. This vulnerability can be mitigated by updating to version 1.7.3 or later of the package or by implementing a temporary workaround to sanitize user input. It is important to address this vulnerability promptly to prevent potential XSS attacks and ensure the security of the application.
See every vulnerability recorded for @builder.io/qwik →
FAQ
mXSS (mutation XSS) is a type of XSS attack where the injected malicious code mutates the original DOM tree, leading to unexpected behavior and potential security vulnerabilities.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide the package-lock.json file of your application and Vulert will analyze it for any open-source vulnerabilities, including this mXSS vulnerability in @builder.io/qwik.
The impact of this vulnerability is that an attacker can inject malicious code that will be executed when the vulnerable component is rendered on the client-side. This can lead to unauthorized access, data theft, or other malicious activities depending on the capabilities of the injected code.
At the time of this report, there are no known public exploits of this vulnerability. However, it is important to promptly update to the fixed version or apply the recommended workaround to mitigate the risk of potential attacks.
Yes, the CVSS score for this vulnerability is 6.3, indicating a moderate level of severity. It is important to address this vulnerability to prevent potential security breaches.
References
Related vulnerabilities
Recent vulnerabilities recorded for @builder.io/qwik.
