Sync-in Server has a ReDoS via Unsanitized Regex in Sync Diff `pathFilters`

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Sync-in/server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Sync-in/server.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 21, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 21, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 21, 2026

Sources and claim methodology

• GitHub security advisorygithub.com

Related CVEs

• Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`Same sync-in/server package
• @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`Same sync-in/server package
• Sync-in Server has Username/Login Enumeration via Timing Side-Channel on POST /api/auth/login (incomplete fix of the prior timing-attack advisory)Same sync-in/server package
• Tautulli: Reflected XSS in `/search` endpointSame generic ecosystem
• Joplin: SSO Auth Code Login Missing Rate Limiting — 9-Digit Numeric Code Brute-Forceable via Unprotected EndpointSame generic ecosystem
• Envoy: HTTP/3 connection pool selection null-derefs in ProdClusterManagerFactory::allocateConnPool when transport_socket_options is nullSame generic ecosystem