Skip to main content
EPSS 0.3%top 80%

CVE-2026-50288: CWE-918: Server-Side Request Forgery (SSRF) in asymmetric-effort specifyjs

0
High
Published: 08/21/2026 (08/21/2026, 19:29:45 UTC)
Source: GCVE Database
Vendor/Project: asymmetric-effort
Product: specifyjs

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.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
None
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Affected software

npmghsa
@asymmetric-effort/specifyjs
Affected versions
<0.2.136

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/22/2026, 11:08:37 UTC

Technical Analysis

SpecifyJS is a TypeScript UI framework. Before version 0.2.136, when the new URL() constructor threw a parse error, the assertSecureUrl function caught the error but returned silently without throwing, effectively allowing insecure requests to proceed without HTTPS validation. This behavior constitutes a security vulnerability (CWE-918: Insecure Default Initialization) that could lead to insecure network communication. The issue is resolved in version 0.2.136 by modifying the catch block to throw an error, preventing silent bypass of HTTPS validation.

Potential Impact

Requests with malformed URLs could bypass HTTPS validation, potentially allowing insecure or unintended network requests. This could lead to data exposure or man-in-the-middle attacks if insecure HTTP requests are allowed where HTTPS is expected. The vulnerability does not require privileges or user interaction and is exploitable remotely.

Mitigation Recommendations

Upgrade SpecifyJS to version 0.2.136 or later, where the vulnerability is fixed by throwing an error on URL parse failure instead of silently allowing the request. No other mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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: 08/22/2026, 11:08:37 UTC

Last updated: 09/13/2026, 16:57:16 UTC

Views: 211

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses