CVE-2026-51917
Deferred Deferred - Pending Action

BaseFortify

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

Publication date: 2026-10-02

Last updated on: 2026-10-05

Assigner: MITRE

Description

FinRobot v1.0.0 is vulnerable to Code Injection in CodingUtils.modify_code.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-05
Generated
2026-10-19
AI Q&A
2026-10-02
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
n/a n/a n/a

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-51917 is a code injection flaw in FinRobot v1.0.0 affecting the CodingUtils.modify_code method. The issue occurs because the method accepts file paths from LLM tool calls without validation. When FinRobot's autogen session is exposed via HTTP or an interactive interface, attackers can use prompt injection to manipulate the LLM into invoking modify_code with file paths outside the intended workspace, enabling arbitrary file modifications.

Detection Guidance

Check FinRobot logs for suspicious file modification attempts or unexpected tool invocations. Look for prompts containing path traversal sequences like ../ in the autogen session logs. Inspect file changes in directories outside the intended workspace, especially configuration files or application code.

Impact Analysis

This vulnerability allows attackers to overwrite configuration files, inject backdoors, or corrupt application code by modifying files outside the intended workspace. If FinRobot is exposed via HTTP or an interactive interface, attackers could manipulate the LLM into executing malicious file modifications through prompt injection.

Compliance Impact

This vulnerability could lead to unauthorized file modifications, potentially exposing sensitive data or violating data protection requirements under GDPR and HIPAA. Unrestricted file access may result in data breaches, unauthorized code execution, or configuration tampering, all of which are compliance violations for these standards.

Mitigation Strategies

Upgrade FinRobot to a patched version if available. Implement strict input validation for file paths in CodingUtils.modify_code to reject paths outside the workspace. Restrict LLM tool invocation permissions to prevent unauthorized file modifications. Monitor file system changes and network traffic for signs of exploitation.

Chat Assistant

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

EPSS Chart