Answer in brief
CVE-2026-117680 records a Low severity (CVSS 2.1) vulnerability in jsv treats regex match budget exhaustion as a non-match, bypassing patternProperties and not. The current sources do not mark it as known exploited. The current feed maps lud/jsv (generic), lud/lud/jsv (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 2.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps lud/jsv (generic), lud/lud/jsv (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| lud/jsvgeneric | >=0.1.0 <0.26.2 | 0.26.2 |
| lud/lud/jsvgeneric | >=302a5d0803468f81a1cf08e3b67d8b14cee759ca <defdb8a68ac7f218aa5dfe85190d484017cb8817 | defdb8a68ac7f218aa5dfe85190d484017cb8817 |
Published upstream
Nov 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.