SSRF via fail-open URL parse handling
Published Aug 21, 2026 · Updated Aug 21, 2026
Server-side request forgery in SpecifyJS before 0.2.136 allows remote attackers to bypass HTTPS enforcement using a malformed URL. The assertSecureUrl function in core/src/shared/secure-fetch.ts catches a new URL parse error and returns, so secureFetch fetches the unvalidated input. Exploitation requires a consuming application to pass attacker-controlled input that fetch accepts but the URL constructor rejects; the request can then bypass the HTTPS-only policy.
Summary
What happened
Server-side request forgery in SpecifyJS before 0.2.136 allows remote attackers to bypass HTTPS enforcement using a malformed URL. The assertSecureUrl function in core/src/shared/secure-fetch.ts catches a new URL parse error and returns, so secureFetch fetches the unvalidated input. Exploitation requires a consuming application to pass attacker-controlled input that fetch accepts but the URL constructor rejects; the request can then bypass the HTTPS-only policy.
The record
- CVE
- CVE-2026-50288
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- Asymmetric Effort
- Product
- SpecifyJS
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.2.136
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo