dbcve.org
OpensiftApplication

CVE-2026-27170

HIGH · 7.1 CVSS v3.1 Published 2026-02-21
Fix available
A fix is available. Upgrade to 1.1.3 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenSift versions 1.1.2-alpha and below contain a Server-Side Request Forgery (SSRF) vulnerability in the URL ingest feature. When processing attacker-controlled URLs, the application can be coerced into making requests to arbitrary targets, including private/local network resources. This allows external attackers to probe internal services, cloud metadata endpoints, and other internal infrastructure accessible from the OpenSift host.

MitigationUpgrade to version 1.1.3-alpha to obtain the security fix. If private URL access is required for legitimate use cases, carefully evaluate the risk before setting OPENSIFT_ALLOW_PRIVATE_URLS=true and consider implementing network segmentation to limit the application's ability to reach sensitive internal resources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpensiftApplication
Affected:< 1.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenSift version
    Run 'opensift --version' or check the installed package version via your package manager (e.g., 'npm list opensift', 'pip show opensift', or equivalent for your installation method)
    Affected if The installed version is 1.1.2-alpha or below (any version < 1.1.3)
  2. Identify if URL ingest feature is in use
    Review your OpenSift configuration files, logs, or dashboard for any feeds, integrations, or modules that process URLs from external or untrusted sources
    Affected if URL ingest functionality is actively configured or being used in your environment
  3. Check for private network access configuration
    Inspect environment variables and configuration files for 'OPENSIFT_ALLOW_PRIVATE_URLS' or similar settings that control whether the application can make requests to private/internal network addresses
    Affected if OPENSIFT_ALLOW_PRIVATE_URLS is set to 'true' or the application has no restrictions on fetching URLs from private IP ranges
  4. Verify network exposure of URL processing
    Review network access rules, firewall policies, or API gateways protecting the URL ingest endpoint to determine if it is reachable from untrusted networks or the internet
    Affected if The URL ingest endpoint is exposed to untrusted networks without authentication or rate limiting

You are affected if you are running OpenSift version 1.1.2-alpha or below AND the URL ingest feature is enabled, particularly if private URL access is allowed or the endpoint is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.3 or later
Fixed in 1.1.3
Interim mitigation

Upgrade to version 1.1.3-alpha to obtain the security fix. If private URL access is required for legitimate use cases, carefully evaluate the risk before setting OPENSIFT_ALLOW_PRIVATE_URLS=true and consider implementing network segmentation to limit the application's ability to reach sensitive internal resources.

Recommended fix High confidence

1.1.3-alpha

  1. Upgrade OpenSift to version 1.1.3-alpha or later to resolve the improper input validation vulnerability in URL ingest functionality
  2. After upgrading, verify that URL ingest functionality works correctly with the security fix in place

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Opensift Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data