Answer in brief
CVE-2026-50290 records a Medium severity (CVSS 5.3) vulnerability in @asymmetric-effort/specifyjs: CSS expression sanitization is bypassable in renderToString. The current sources do not mark it as known exploited. The current feed maps asymmetric-effort/specifyjs (generic), @asymmetric-effort/specifyjs (npm). 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 5.3. 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 asymmetric-effort/specifyjs (generic), @asymmetric-effort/specifyjs (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| asymmetric-effort/specifyjsgeneric | < 0.2.136 | Not reported |
| @asymmetric-effort/specifyjsnpm | <0.2.136 | 0.2.136 |
Published upstream
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 2, 2026
SpecifyJS is a declarative TypeScript user interface framework. Prior to version 0.2.136, CSS value sanitization stripped `expression(` and `url(javascript:` using simple regex, but could be bypassed with CSS unicode escapes (`\65xpression(`), null bytes, or CSS comments (`exp/**/ression(`). These CSS injection vectors only work in legacy browsers (IE6-IE10). SpecifyJS targets modern browsers. Starting in version 0.2.136, CSS sanitization now normalizes unicode escapes and strips CSS comments before pattern matching. Also checks for `behavior:`, `-moz-binding`, and `-o-link` patterns.
Quoted source text, attributed separately from HOL analysis.