# CVE-2026-27170: OpenSift: SSRF risk in URL ingestion endpoint

> Attackers can coerce the OpenSift URL ingestion endpoint to access private network resources via Server-Side Request Forgery.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-3w2r-hj5p-h6pp

## What is CVE-2026-27170?

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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-27170?

It affects 1 product.


Products: Opensift Opensift.

## How do I fix CVE-2026-27170?

No fix has been published for CVE-2026-27170 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27170 being exploited?

There is no known exploitation of CVE-2026-27170 in the wild and no public exploit code.

## Other vulnerabilities in OpenSift

- [CVE-2026-27169](https://insights.sbomify.com/CVE-2026-27169/): OpenSift: Persistent XSS Chat Tool Rendering (high 8.9)
- [CVE-2026-28676](https://insights.sbomify.com/CVE-2026-28676/): OpenSift: Insufficient path containment checks in storage helpers could allow path traversal-style file operations (high 8.8)
- [CVE-2026-28677](https://insights.sbomify.com/CVE-2026-28677/): OpenSift: Insufficient URL destination restrictions in ingest flow could enable SSRF-style internal access (high 8.2)
- [CVE-2026-27189](https://insights.sbomify.com/CVE-2026-27189/): OpenSift: Race-prone local persistence could cause state corruption/loss (medium 6.6)
- [CVE-2026-28675](https://insights.sbomify.com/CVE-2026-28675/): OpenSift: Sensitive implementation details exposed via raw exception messages and token-returning endpoints (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27170 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-27170 in the wild and no public exploit code.

Affected product: OpenSift. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27170/ (Markdown: https://insights.sbomify.com/CVE-2026-27170/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27170
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27170
- OSV: https://osv.dev/vulnerability/CVE-2026-27170

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27170/
Summaries are generated and may contain mistakes; the official description above is the record.