A high-severity vulnerability has been identified in multiple Valibot products, which are used for data validation. An attacker could exploit this flaw by sending specially crafted data to an application using the vulnerable library, potentially bypassing security checks to access or modify information, or even cause the application to crash. Organizations are urged to apply the vendor-provided security patches immediately to mitigate the risk of data compromise and service disruption.

The vulnerability is a prototype pollution flaw within the schema validation logic of the Valibot library. An unauthenticated remote attacker can submit a malicious JSON object containing a __proto__ or constructor.prototype payload. When the vulnerable Valibot schema parses this object, it fails to properly sanitize the keys, allowing the attacker to modify the prototype of the base Object in the JavaScript environment. This can lead to a variety of impacts, including denial of service, security control bypasses, and potentially remote code execution if the application's logic subsequently relies on properties of the polluted prototype.

This vulnerability is rated as High severity with a CVSS score of 7.5. Successful exploitation could have a significant negative impact on the business. Bypassing data validation could lead to data integrity violations, where malicious or malformed data is written to databases. In scenarios where Valibot is used to validate authorization tokens or user permissions, this flaw could result in privilege escalation or unauthorized access to sensitive data and application functionality. The potential for denial of service could lead to application downtime, impacting business operations and customer trust, while a remote code execution scenario would represent a full compromise of the affected server.

Immediate Action: The primary remediation is to apply the security updates provided by the vendor across all affected applications immediately. Prioritize patching for internet-facing systems. After patching, it is crucial to monitor application logs for any signs of attempted or successful exploitation and review historical access logs for suspicious patterns predating the patch.

Proactive Monitoring: Implement enhanced monitoring on systems running the affected software. Security teams should look for inbound web requests containing suspicious JSON payloads with keys such as __proto__, constructor, or prototype. Monitor application performance for unexpected crashes or high resource utilization, which could indicate a denial-of-service attempt. Check for any anomalous outbound network traffic from application servers, which could signal a successful compromise.

Compensating Controls: If immediate patching is not feasible, consider implementing the following compensating controls:

• Deploy a Web Application Firewall (WAF) with rules specifically designed to detect and block common prototype pollution attack patterns in JSON bodies.
• If possible within the application code, freeze the Object prototype (Object.freeze(Object.prototype)) at startup to prevent runtime modifications. This should be tested thoroughly to ensure it does not break application functionality.
• Run the application process with the lowest possible privileges to limit the impact of a potential code execution exploit.

Public Exploit Available: false

Given the high severity (CVSS 7.5) of this vulnerability and its potential for significant business impact, we strongly recommend that organizations prioritize the immediate application of vendor-supplied patches. Although this CVE is not currently listed on the CISA KEV catalog, its high score and the widespread use of data validation libraries make it a prime candidate for future inclusion and active exploitation. If patching is delayed, the compensating controls outlined above should be implemented as a temporary mitigation while a permanent patching plan is executed.