CVE records
Every CVE as the CVE Program publishes it, refreshed every ten minutes, with NVD's analysis, CISA's known-exploited status and a healthcare tag. Subscribers get the CVEs that match their own systems on My program, by email as they are published. Where the data comes from: sources.
Updated under an hour ago ()
What this means for you
This week: 5,437 CVEs published, 355 critical, and 7 newly confirmed exploited. Add your stack to see whether any of them hit you.
Do this next
Free account, 1 product
- Published in the last 7 days
- 5,437
- Show in the list
- Critical, last 7 days
- 355
- Show in the list
- Healthcare-tagged, last 7 days
- 4
- Show in the list
- Known exploited (CISA KEV)
- 1,747
- Show in the list
Showing CVEs that name the product sync_in:server. Show all products
| CVE | Severity | Title | Published |
|---|---|---|---|
| CVE-2026-58272 | Medium 5.3 | Sync-in Server has Username/Login Enumeration via Timing Side-Channel on POST /api/auth/login (incomplete fix of the prior timing-attack advisory) Assigned by GitHub_M | Sep 21, 2026 |
| CVE-2026-58270 | Medium 6.5 | Sync-in Server has a ReDoS via Unsanitized Regex in Sync Diff `pathFilters` Assigned by GitHub_M | Sep 21, 2026 |
| CVE-2026-58269 | High 8.1 | Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token` Assigned by GitHub_M | Sep 21, 2026 |
| CVE-2026-58271 | Medium 6.8 | @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register` Assigned by GitHub_M | Sep 21, 2026 |
CVSS is the assigning CNA's score where it gives one, otherwise NVD's. The healthcare tag is a documented heuristic (a list of clinical and health IT vendors, and clinical terms in the description), not a classification. The CVE record is authoritative.