CVE-2026-50288: @asymmetric-effort/specifyjs: URL parse failure silently allows request
Finding Location: core/src/shared/secure-fetch.ts:42-45 When new URL() throws a parse error, the assertSecureUrl function returned without throwing, silently allowing the request to proceed without HTTPS validation. Status Fixed in v0.2.136 — The catch block now throws an error instead of silently returning.
Published Jul 2, 2026
Affected packages
@asymmetric-effort/specifyjs
- Ecosystem
- npm
- Affected
- < 0.2.136
- Fixed in
- 0.2.136
- Check
npm ls @asymmetric-effort/specifyjs
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Finding
Location: core/src/shared/secure-fetch.ts:42-45
When new URL() throws a parse error, the assertSecureUrl function returned without throwing, silently allowing the request to proceed without HTTPS validation.
Status
Fixed in v0.2.136 — The catch block now throws an error instead of silently returning.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-50290
@asymmetric-effort/specifyjs: CSS expression sanitization is bypassable in renderToString
medium5.3Jul 2, 2026GHSA-2944-57xv-2682
@asymmetric-effort/specifyjs: `data:` URI allowed without size restriction
medium6.9Jul 2, 2026GHSA-5c7w-4wm3-85vw
@asymmetric-effort/specifyjs: GraphQL gql tag allows metacharacter injection
medium6.9Jul 2, 2026GHSA-j5qp-p44g-2m49
@asymmetric-effort/specifyjs: No redirect target validation in secureFetch
medium6.9Jul 2, 2026GHSA-qcr8-x557-7cp3
@asymmetric-effort/specifyjs: Production console warnings may leak internal framework state
medium6.9Jul 2, 2026GHSA-xw57-23p8-9wc5
@asymmetric-effort/specifyjs: Localhost bypass incomplete (IPv6, 0.0.0.0, 127.x range)
medium6.9Jul 2, 2026
