CVE-2026-117680

jsv treats regex match budget exhaustion as a non-match, bypassing patternProperties and not

Published Nov 1, 2026 CVSS 4.0 · 2.1 Low EPSS < 1% KEV · Not listed
Description
Improper Check for Unusual or Exceptional Conditions vulnerability in the pattern and patternProperties keywords in lud jsv allows an unauthenticated remote attacker to bypass schema validation via a string that matches a schema regex only after heavy backtracking. JSV.Helpers.RegexExt.bounded_match?/2 runs schema regexes with a backtracking budget but calls :re.run/3 without :report_errors, so a match that exhausts the budget returns the same :nomatch as a real non-match. A key that matches a patternProperties regex is then checked against additionalProperties or not at all, and a string that matches a not subschema with a pattern is accepted. Before the budget existed, Regex.match?/2 failed the same way at Erlang's default match limit.

Only schemas whose regex explores a catastrophic branch before the branch that matches are affected. The attacker controls the data, not the schema, and linear patterns never exhaust the budget.

This issue affects jsv: from 0.1.0 before 0.26.2.

Analysis

AI-generated

Technical impact

Improper handling of regex backtracking budget in the pattern and patternProperties keywords causes a regex that exhausts its backtracking budget to be treated the same as a normal non‑match. An attacker can supply a string that triggers heavy backtracking, causing patternProperties to think the key does not match and consequently skip further validation. This allows arbitrary keys that would normally be rejected or validated to pass the schema unchecked, effectively bypassing input validation.

Affected Systems

The flaw exists in all releases of the jsv library from version 0.1.0 through 0.26.1. Versions starting at 0.26.2 incorporate the fix. The vulnerability is confined to the jsv JavaScript/Elixir JSON Schema Validator component operated by applications that include it in their code base.

Risk and Exploitability

The CVSS score of 2.1 indicates limited impact, and the EPSS is not available, placing it as a low overall risk. However, the flaw can be exploited when an application relies on jsv to enforce strict schema compliance, and an attacker can supply specifically crafted input. The absence from the KEV catalog and the need for controlled regex patterns make the likelihood of widespread exploitation modest, but any dependency on jsv should be updated promptly.

Remediation

Vendor Workaround

Pair patternProperties with additionalProperties: false. A key whose match exhausts the budget is then rejected instead of accepted unchecked. Valid keys that need heavy backtracking are rejected as well. Write schema regexes without nested quantifiers or overlapping alternatives, and do not express deny-lists as a not subschema with a pattern on untrusted input.


OpenCVE Recommended Actions

  • Upgrade to jsv version 0.26.2 or later to receive the patch that prevents regex match budget exhaustion from being treated as a non‑match.
  • If an upgrade is not possible, apply the official workaround by pairing patternProperties with additionalProperties: false so that keys matching an exhaustive pattern are rejected instead of accepted unchecked.
  • Rewrite any schema regexes to avoid nested quantifiers or overlapping alternatives, ensuring that catastrophic backtracking cannot occur.

Generated by OpenCVE AI on November 1, 2026 at 14:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Improper Check for Unusual or Exceptional Conditions vulnerability in the pattern and patternProperties keywords in lud jsv allows an unauthenticated remote attacker to bypass schema validation via a string that matches a schema regex only after heavy backtracking. JSV.Helpers.RegexExt.bounded_match?/2 runs schema regexes with a backtracking budget but calls :re.run/3 without :report_errors, so a match that exhausts the budget returns the same :nomatch as a real non-match. A key that matches a patternProperties regex is then checked against additionalProperties or not at all, and a string that matches a not subschema with a pattern is accepted. Before the budget existed, Regex.match?/2 failed the same way at Erlang's default match limit. Only schemas whose regex explores a catastrophic branch before the branch that matches are affected. The attacker controls the data, not the schema, and linear patterns never exhaust the budget. This issue affects jsv: from 0.1.0 before 0.26.2.
Title jsv treats regex match budget exhaustion as a non-match, bypassing patternProperties and not
First Time appeared Lud
Lud jsv
Weaknesses CWE-754
CPEs cpe:2.3:a:lud:jsv:*:*:*:*:*:*:*:*
Vendors & Products Lud
Lud jsv
References
Metrics cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-754

    Improper Check for Unusual or Exceptional Conditions

Sources

Status
PUBLISHED
Assigner
EEF
Published
Updated
Nov 19, 2026, 6:57 AM
Reserved
Oct 30, 2026, 12:45 PM
Status
Deferred
Published
Nov 1, 2026, 2:18 PM
Modified
Nov 2, 2026, 8:17 PM