CVE-2026-50288
SpecifyJS allows bypass of HTTPS validation when URL parsing fails
Is CVE-2026-50288 being exploited?
Not confirmed. CVE-2026-50288 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-50288?
CVE-2026-50288 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50288?
Yes. A fix has been recorded for CVE-2026-50288. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50288 affect?
CVE-2026-50288 affects SpecifyJS < 0.2.136, Web apps using SpecifyJS, Client-side TypeScript UI components. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50288?
Upgrade to SpecifyJS v0.2.136 or later
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypasses client-side HTTPS validation when new URL() parse errors occur; attacker-controlled URLs can force insecure HTTP requests, enabling interception or tampering.
Patch when possible
- affected< 0.2.136
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.