Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed /code HTTP endpoint
-
DeliverySend crafted request with injected Python payload
-
ExploitPython Validation Handler evaluates injected code
-
ExecutionExecute arbitrary Python in server context
-
ImpactRead secrets/files or invoke subprocess for OS commands
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No authentication is required - the CVSS 4.0 vector confirms PR:N, meaning the /code endpoint is reachable and exploitable by any unauthenticated network client. No user interaction is required (UI:N). No special attack conditions are imposed (AT:N/AC:L). The sole limiting factor is network reachability: if the VibeSurf instance is exposed on a public or semi-public network interface, exploitation is unrestricted. The constrained Low impact ratings (VC:L/VI:L/VA:L) suggest the executing process may run with limited OS privileges or in a partially isolated context - defenders should verify whether the VibeSurf process has access to sensitive credentials, environment variables, or internal network services, as Python code execution can pivot through those regardless of the process privilege level. |
| Impact | The CVSS 4.0 base score of 5.5 (Medium) is arguably conservative for an unauthenticated remote code injection primitive: the base metrics AV:N/AC:L/AT:N/PR:N/UI:N describe trivially exploitable network conditions with zero prerequisites, while the Low C/I/A ratings on the vulnerable system suggest a constrained execution context - possibly a sandboxed or low-privilege process, or that the product's data footprint is inherently limited. The E:P threat metric confirms a public PoC exists, lowering the skill bar for exploitation. There is no CISA KEV listing, suggesting no confirmed mass or critical-infrastructure exploitation at time of analysis. The vendor's non-response to disclosure eliminates the likelihood of a coordinated patch, and the rolling-release model means no clear 'fixed version' signal exists for defenders to track. Net assessment: real exploitation is plausible given trivial conditions and existing PoC, but the limited product footprint (niche tool) and constrained impact scope reduce priority relative to ubiquitous-product RCE vulnerabilities. |
| Exploit ScenarioDerived | An attacker with network access to the VibeSurf /code endpoint sends a crafted HTTP request containing injected Python code as the manipulated input parameter - requiring no authentication and no prior reconnaissance beyond endpoint discovery. A public PoC (asciinema recording at https://asciinema.org/a/1230301) demonstrates the technique, meaning exploitation steps are publicly scripted. Once the injected code executes server-side, the attacker can read environment variables, exfiltrate files accessible to the process, or pivot to OS-level commands via Python's subprocess or os modules. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 04, 2026
Code injection in VibeSurf's Python Validation Handler enables remote unauthenticated attackers to inject and execute arbitrary Python code by manipulating the /code endpoint. All versions up to commit cd6e519d507cdd4d63061300bf60fb176e1f57e0 are confirmed affected per EUVD-2026-52704. No patch is available - the vendor did not respond to disclosure - and a public proof-of-concept exists (CVSS 4.0 E:P, corroborated by an asciinema recording in the references), making exploitation accessible to low-skilled attackers.
RemediationAI
No vendor-released patch has been identified at time of analysis - the vendor did not respond to disclosure and no fixed commit has been published. Operators using VibeSurf should immediately restrict network access to the /code endpoint at the reverse proxy or firewall layer (e.g., allow only trusted internal IP ranges), accepting the trade-off that this disables the affected functionality for external users. If the /code endpoint cannot be blocked without breaking core workflows, consider placing a Web Application Firewall rule to block requests containing Python built-ins commonly used in injection payloads (eval, exec, __import__, os.system, subprocess) - note this is a partial control and bypassable via obfuscation. Monitor VulDB entry https://vuldb.com/vuln/385776 and the project's GitHub repository for any upstream commit that addresses the issue; once a fix commit is identified, redeploy from that revision. Until a patch is available, treating this endpoint as untrusted and isolating the service from sensitive internal networks is the most reliable compensating control.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
VibeSurf (CPE: cpe:2.3:a:vibesurf-ai:vibesurf:*:*:*:*:*:*:*:*) is an AI-surfing/code-assistance tool with a Python backend. The vulnerable component is the Python Validation Handler exposed at the /code HTTP endpoint, which processes user-supplied input insufficiently before passing it into Python code evaluation logic. CWE-94 (Improper Control of Generation of Code - Code Injection) indicates the root cause: unsanitized user data is incorporated into dynamically generated or evaluated Python code (e.g., via eval(), exec(), or similar mechanisms), allowing an attacker to inject arbitrary Python statements that are then executed in the server-side interpreter context. This is distinct from OS command injection (CWE-78) - the injection occurs at the language level, though Python's os/subprocess libraries make lateral escalation to OS commands straightforward once code execution is achieved.
Know when Vibesurf gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Network-reachable endpoint with no auth (PR:N), trivial conditions (AC:L), no scope change, and constrained Low C/I/A per CVSS 4.0 vulnerable-system impact signals.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
1DescriptionCVE.org
A vulnerability has been found in vibesurf-ai VibeSurf up to cd6e519d507cdd4d63061300bf60fb176e1f57e0. Impacted is an unknown function of the file /code of the component Python Validation Handler. The manipulation leads to code injection. Remote exploitation of the attack is possible. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-52704
GHSA-c46v-j7qf-v42g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB