{"answers":{"affected":"2 open source packages ship an affected version, including @asymmetric-effort/specifyjs.","exploited":"There is no known exploitation of CVE-2026-50288 in the wild and no public exploit code.","fix":"Upgrade @asymmetric-effort/specifyjs to 0.2.136 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-50288 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-50288 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.136\n- @asymmetric-effort/specifyjs (npm): affected all versions; fixed in 0.2.136\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50288/ (Markdown: https://insights.sbomify.com/CVE-2026-50288/index.md)","id":"CVE-2026-50288","markdown":"https://insights.sbomify.com/CVE-2026-50288/index.md","name":"CVE-2026-50288","record":{"aliases":["GHSA-8882-frvv-92w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeScript UI framework","requires_auth":"none","summary":"Attackers can bypass HTTPS validation in SpecifyJS by triggering URL parse errors, allowing insecure requests to proceed.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@asymmetric-effort/specifyjs: URL parse failure silently allows request","id":"CVE-2026-50288","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"systeminformation: OS command injection in networkInterfaces() via interfaces(5) source-directive path on Linux","id":"CVE-2026-50289"},"packages":[{"ecosystem":"npm","fixed":["0.2.136"],"introduced":["0"],"last_affected":[],"package":"@asymmetric-effort/specifyjs","purl":null,"source":"GHSA-8882-frvv-92w4"},{"ecosystem":"npm","fixed":["0.2.136"],"introduced":["0"],"last_affected":[],"package":"@asymmetric-effort/specifyjs","purl":"pkg:npm/%40asymmetric-effort/specifyjs","source":"GHSA-8882-frvv-92w4"}],"prev":{"headline":"Missing Authentication for Critical Function in @agenticmail/mcp","id":"CVE-2026-50287"},"products":["specifyjs"],"published":"2026-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["asymmetric-effort"]},"summary":"Attackers can bypass HTTPS validation in SpecifyJS by triggering URL parse errors, allowing insecure requests to proceed.","url":"https://insights.sbomify.com/CVE-2026-50288/"}