CVE-2026-28677
SSRF Vulnerability in OpenSift URL Ingest Pipeline
Publication date: 2026-03-06
Last updated on: 2026-03-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| opensift | opensift | to 1.6.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-28677 is a Server-Side Request Forgery (SSRF) vulnerability in the OpenSift AI study tool, specifically in its URL ingest pipeline before version 1.6.3-alpha.
The vulnerability occurs because the system accepts user-controlled remote URLs without fully restricting where those URLs can point. Although it blocks private or localhost addresses, it fails to block URLs that contain embedded credentials, use non-standard ports, or perform cross-host redirects.
This incomplete validation allows attackers who can submit URLs to trick the server into making requests to unintended internal endpoints or infrastructure components, potentially exposing sensitive internal resources.
The issue was fixed in version 1.6.3-alpha by blocking URLs with embedded credentials, restricting allowed ports to standard HTTP/HTTPS ports (80 and 443), and preventing cross-host redirects.
How can this vulnerability impact me? :
This vulnerability can allow an attacker to make the OpenSift server send requests to internal or protected network resources that are normally inaccessible from outside.
Because the attacker can control the URLs the server accesses, they might gain access to sensitive internal data or services, potentially leading to information disclosure.
The CVSS score of 8.2 indicates a high severity, with a high impact on confidentiality, meaning sensitive information could be exposed.
The attack requires no privileges and no user interaction, making it easier for attackers to exploit if they have access to the URL ingest functionality.
Workarounds include disabling URL ingest for untrusted users or limiting deployments to localhost or environments protected by trusted proxies.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'Detection of this SSRF vulnerability involves monitoring and analyzing the URL ingest pipeline for requests containing user-controlled remote URLs with embedded credentials, non-standard ports, or cross-host redirects.'}, {'type': 'paragraph', 'content': 'You can look for suspicious HTTP requests or logs where URLs include embedded credentials (e.g., user:password@host), use non-standard ports other than 80 or 443, or where redirects lead to unexpected hosts.'}, {'type': 'paragraph', 'content': 'Commands to help detect such activity might include:'}, {'type': 'list_item', 'content': "Using grep or similar tools to search logs for URLs with embedded credentials: grep -E 'https?://[^@]+@' /path/to/logs"}, {'type': 'list_item', 'content': "Searching for URLs using non-standard ports: grep -E 'https?://[^:/]+:[0-9]{1,5}' /path/to/logs | grep -vE ':80|:443'"}, {'type': 'list_item', 'content': 'Monitoring for redirects in logs that point to hosts different from the original domain.'}, {'type': 'paragraph', 'content': 'Additionally, network monitoring tools can be configured to detect outbound requests to internal or unexpected IP ranges originating from the OpenSift ingest process.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading OpenSift to version 1.6.3-alpha or later, where the vulnerability has been patched.
The patch implements backend restrictions that block URLs with embedded credentials, restrict allowed ports to standard HTTP/HTTPS ports (80 and 443), and prevent cross-host redirects during the ingest process.
If upgrading is not immediately possible, consider disabling the URL ingest functionality for untrusted users.
Also, limit deployments to localhost or environments protected by strict trusted proxy controls to reduce exposure.