{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27170 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27170 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27170 is a high-severity server-side request forgery vulnerability in OpenSift, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27170 and fix it if it is affected.\n\nWhat it is: CVE-2026-27170 is a high-severity server-side request forgery vulnerability in OpenSift, published on 20 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27170 in the wild and no public exploit code.\n\nAffected product: OpenSift. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-27170/ (Markdown: https://insights.sbomify.com/CVE-2026-27170/index.md)","id":"CVE-2026-27170","markdown":"https://insights.sbomify.com/CVE-2026-27170/index.md","name":"CVE-2026-27170","record":{"aliases":["GHSA-3w2r-hj5p-h6pp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI study tool","requires_auth":"low_privilege","summary":"Attackers can coerce the OpenSift URL ingestion endpoint to access private network resources via Server-Side Request Forgery.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opensift","vendor":"opensift"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"OpenSift is an AI study tool that sifts through large datasets using semantic search and generative AI. In versions 1.1.2-alpha and below, URL ingest allows overly permissive server-side fetch behavior and can be coerced into requesting unsafe targets. Potential access/probing of private/local network resources from the OpenSift host process when ingesting attacker-controlled URLs. This issue has been fixed in version 1.1.3-alpha. To workaround when using trusted local-only exceptions, use OPENSIFT_ALLOW_PRIVATE_URLS=true with caution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OpenSift: SSRF risk in URL ingestion endpoint","id":"CVE-2026-27170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in zlib","id":"CVE-2026-27171"},"packages":[],"prev":{"headline":"OpenSift: Persistent XSS Chat Tool Rendering","id":"CVE-2026-27169"},"products":["OpenSift"],"published":"2026-02-20","related":[{"cvss_score":8.9,"headline":"OpenSift: Persistent XSS Chat Tool Rendering","id":"CVE-2026-27169","kev_date_added":null,"published":"2026-02-20"},{"cvss_score":8.8,"headline":"OpenSift: Insufficient path containment checks in storage helpers could allow path traversal-style file operations","id":"CVE-2026-28676","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.2,"headline":"OpenSift: Insufficient URL destination restrictions in ingest flow could enable SSRF-style internal access","id":"CVE-2026-28677","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":6.6,"headline":"OpenSift: Race-prone local persistence could cause state corruption/loss","id":"CVE-2026-27189","kev_date_added":null,"published":"2026-02-21"},{"cvss_score":5.3,"headline":"OpenSift: Sensitive implementation details exposed via raw exception messages and token-returning endpoints","id":"CVE-2026-28675","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["OpenSift"]},"summary":"Attackers can coerce the OpenSift URL ingestion endpoint to access private network resources via Server-Side Request Forgery.","url":"https://insights.sbomify.com/CVE-2026-27170/"}