CVE-2026-50288 @asymmetric-effort/specifyjs: URL parse failure silently allows request
Attackers can bypass HTTPS validation in SpecifyJS by triggering URL parse errors, allowing insecure requests to proceed.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-50288?
CVE-2026-50288 is a high-severity server-side request forgery vulnerability in asymmetric-effort specifyjs, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
SpecifyJS is a declarative TypeScript user interface framework. Prior to version 0.2.136, when `new URL()` throws a parse error, the `assertSecureUrl` function returned without throwing, silently allowing the request to proceed without HTTPS validation. Starting in version 0.2.136, the catch block now throws an error instead of silently returning.
Weakness: CWE-918
Which versions are affected by CVE-2026-50288?
2 open source packages ship an affected version, including @asymmetric-effort/specifyjs.
| Package | Affected | Fixed in |
|---|---|---|
@asymmetric-effort/specifyjs npm | All versions | 0.2.136 |
@asymmetric-effort/specifyjs npm | All versions | 0.2.136 |
How do I fix CVE-2026-50288?
Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-50288 being exploited?
There is no known exploitation of CVE-2026-50288 in the wild and no public exploit code.
Sources
Also known as GHSA-8882-frvv-92w4.