Cross-Site Scripting (XSS) in @asymmetric-effort/specifyjs (CVE-2026-50290)
Summary
Cross-site scripting in @asymmetric-effort/specifyjs (CVE-2026-50290). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.2.136 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50290 has been found in @asymmetric-effort/specifyjs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.
If unsure, ask your IT team or search "@asymmetric-effort/specifyjs CVE-2026-50290" on the vendor's site.
CVE-2026-50290 (@asymmetric-effort/specifyjs) — CWE-79
Patched: 0.2.136 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in @asymmetric-effort/specifyjs.
Check the vendor advisory for the affected versions of @asymmetric-effort/specifyjs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.2.136.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@asymmetric-effort/specifyjs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@asymmetric-effort/specifyjs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@asymmetric-effort/specifyjsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @asymmetric-effort/specifyjs to 0.2.136ステージング環境で 0.2.136 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com