Vulnerability in ua-parser-js (CVE-2026-48125)
Summary
Vulnerability in ua-parser-js (CVE-2026-48125). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.10 or later.
Original description
The description as published by the source.
UAParser.js is a JavaScript library to detect browsers, operating systems, CPUs, and devices from user-agent data. From 2.0.1 until 2.0.10, a regular expression denial-of-service vulnerability exists when using the Client Hints API. By sending a crafted Sec-CH-UA-Model header to an application that calls UAParser(headers).withClientHints(), an attacker can cause excessive CPU time due to catastrophic backtracking in the device regex because Client Hints values are copied without the UA_MAX_LENGTH limit used for User-Agent values. This issue is fixed in version 2.0.10.
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-48125 has been found in ua-parser-js.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade ua-parser-js to 2.0.10 or later.
If unsure, ask your IT team or search "ua-parser-js CVE-2026-48125" on the vendor's site.
CVE-2026-48125 (ua-parser-js) — CWE-1333 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.10 — 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.
A vulnerability (CWE-1333) exists in ua-parser-js.
Check the vendor advisory for the affected versions of ua-parser-js.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.10.
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 'ua-parser-js' . 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 'ua-parser-js' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
ua-parser-jsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade ua-parser-js to 2.0.10ステージング環境で 2.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-48125 node-ua-parser-js
- Ubuntu UBUNTU-CVE-2026-48125 node-ua-parser-js
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com