CVE-2026-130768
Deferred Deferred - Pending Action

Server-Side Request Forgery in Obot Before 0.27.0

Vulnerability report for CVE-2026-130768, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: VulnCheck

Description

Obot from 0.14.0 before 0.27.0 contains a server-side request forgery vulnerability that allows Power Users to bypass outbound protections by supplying unspecified addresses, IPv6 transition addresses, or registry icon URLs. Attackers can add remote MCP servers pointing to 0.0.0.0, ::, or NAT64/6to4/Teredo addresses embedding blocked IPv4 addresses to probe internal services for reachability.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
obot obot From 0.14.0 (inc) to 0.27.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-184 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in the Obot platform affecting versions 0.14.0 to 0.26.3. It allows Power Users to bypass outbound protections by using unspecified addresses like 0.0.0.0, ::, or IPv6 transition addresses embedding blocked IPv4 addresses. Attackers can probe internal services for reachability by adding remote MCP servers pointing to these addresses.

Detection Guidance

Monitor for outbound requests to loopback addresses (0.0.0.0, ::) or IPv6 transition addresses (NAT64/6to4/Teredo) from Obot instances. Check logs for registry icon URL fetches without proper egress restrictions. Use network traffic analysis tools to detect SSRF attempts targeting internal services.

Impact Analysis

An attacker with Power User privileges could exploit this to send requests to internal services, potentially mapping your network or probing for further vulnerabilities. However, the impact is limited to blind requests as Obot only reports status codes and content types, not data, unless the destination speaks MCP.

Compliance Impact

This vulnerability primarily enables unauthorized internal network probing via SSRF, which could expose sensitive internal services. While it does not directly leak data, it may facilitate reconnaissance for further attacks. Compliance impact depends on whether such probing violates specific controls in GDPR (e.g., unauthorized access risks under Article 32) or HIPAA (e.g., network security under 45 CFR Β§ 164.312). The vulnerability's limited confidentiality impact (CVSS) suggests minimal direct compliance violations, but organizations should assess if internal network exposure aligns with their security policies.

Mitigation Strategies

Upgrade Obot to version 0.27.0 or later. Implement stricter outbound request controls for registry icon fetches. Block requests to loopback and IPv6 transition addresses in firewall rules. Restrict Power User privileges to reduce attack surface.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130768. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...