VibeSurf EUVD-2026-52704

Q: What is the CVSS score of EUVD-2026-52704?

EUVD-2026-52704 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

| CVE-2026-18770 MEDIUM

Code Injection (CWE-94)

2026-08-04 VulDB

GHSA-c46v-j7qf-v42g

RCE Python Code Injection Vibesurf

5.5

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

5.5 MEDIUM

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.3 HIGH

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.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 04, 2026 - 15:27 vuln.today

CVSS changed

Aug 04, 2026 - 15:23 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

DescriptionCVE.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.

AnalysisAI

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.

Technical ContextAI

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.

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.