GHSA-8882-frvv-92w4: @asymmetric-effort/specifyjs: URL parse failure silently allows request
A vulnerability in @asymmetric-effort/specifyjs prior to version 0.2.136 allows requests to bypass HTTPS validation due to a URL parse failure. Specifically, when the URL constructor throws a parse error, the assertSecureUrl function fails to throw an error and silently permits the request. This issue was fixed in version 0.2.136 by modifying the catch block to throw an error instead of returning silently.
AI Analysis
Technical Summary
The vulnerability exists in the assertSecureUrl function within core/src/shared/secure-fetch.ts lines 42-45 of the @asymmetric-effort/specifyjs package. When new URL() throws a parse error, the function previously caught the error but returned without throwing, allowing insecure requests to proceed without HTTPS validation. This flaw is classified under CWE-918 (Server-Side Request Forgery). The issue is fixed in version 0.2.136 by ensuring the catch block throws an error, preventing silent bypass of security checks.
Potential Impact
Requests with malformed URLs that cause new URL() to throw a parse error could bypass HTTPS validation, potentially allowing insecure or unintended network requests. This could lead to security risks such as server-side request forgery or data leakage if exploited. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to @asymmetric-effort/specifyjs version 0.2.136 or later, where the vulnerability is fixed by throwing an error on URL parse failures. No other mitigation is required as the official fix addresses the issue.
GHSA-8882-frvv-92w4: @asymmetric-effort/specifyjs: URL parse failure silently allows request
Description
A vulnerability in @asymmetric-effort/specifyjs prior to version 0.2.136 allows requests to bypass HTTPS validation due to a URL parse failure. Specifically, when the URL constructor throws a parse error, the assertSecureUrl function fails to throw an error and silently permits the request. This issue was fixed in version 0.2.136 by modifying the catch block to throw an error instead of returning silently.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists in the assertSecureUrl function within core/src/shared/secure-fetch.ts lines 42-45 of the @asymmetric-effort/specifyjs package. When new URL() throws a parse error, the function previously caught the error but returned without throwing, allowing insecure requests to proceed without HTTPS validation. This flaw is classified under CWE-918 (Server-Side Request Forgery). The issue is fixed in version 0.2.136 by ensuring the catch block throws an error, preventing silent bypass of security checks.
Potential Impact
Requests with malformed URLs that cause new URL() to throw a parse error could bypass HTTPS validation, potentially allowing insecure or unintended network requests. This could lead to security risks such as server-side request forgery or data leakage if exploited. No known exploits in the wild have been reported.
Mitigation Recommendations
Upgrade to @asymmetric-effort/specifyjs version 0.2.136 or later, where the vulnerability is fixed by throwing an error on URL parse failures. No other mitigation is required as the official fix addresses the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8882-frvv-92w4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-50288"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46ecbd27e9c7971943ce6c
Added to database: 07/02/2026, 22:57:01 UTC
Last enriched: 07/02/2026, 23:15:05 UTC
Last updated: 07/03/2026, 00:00:47 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.