Approved changes feed: RSS · Atom

cpe:2.3:a:open-circle:valibot:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorOpen Circle (13b89114-4734-53c3-9d86-8b166b85507e)
ProductValibot (a86f92c9-e515-576e-aa0d-14a507a6545c)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-59952 vulnerable 2026-09-16 04:32:46.704092 Valibot: record() issue paths can make flatten() throw for inherited Object property names
Valibot helps validate data using a schema. Versions prior to 1.4.2 can throw a TypeError inside its flatten() helper when validation issues contain attacker-controlled object keys such as toString, valueOf, or hasOwnProperty. The issue is reachable through normal record() validation. record() intentionally filters __proto__, prototype, and constructor, but it still accepts other own keys that collide with inherited Object.prototype properties. If the record key schema or value schema rejects such an entry, Valibot creates an issue path containing that key. Passing the resulting issues to Valibot's documented flatten() helper causes flatErrors.nested[dotPath] to resolve to the inherited method instead of an own error array, and the helper calls .push(...) on that function. This is not a global prototype pollution issue. The impact is availability/error handling: applications that validate user-controlled objects with record() and flatten validation errors for API responses can crash the request path with a TypeError instead of returning structured validation errors. This issue has been fixed in version 1.4.2.
Published: 2026-07-30T00:10:32.598Z
Updated: 2026-07-30T14:42:29.575Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-66020 vulnerable 2026-06-08 07:39:21.126846 Valibot has a ReDoS vulnerability in `EMOJI_REGEX`
HIGH (7.5)
Valibot helps validate data using a schema. In versions from 0.31.0 to 1.1.0, the EMOJI_REGEX used in the emoji action is vulnerable to a Regular Expression Denial of Service (ReDoS) attack. A short, maliciously crafted string (e.g., <100 characters) can cause the regex engine to consume excessive CPU time (minutes), leading to a Denial of Service (DoS) for the application. This issue has been patched in version 1.2.0.
Published: 2025-11-26T01:49:38.276Z
Updated: 2025-11-26T14:16:54.610Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.