Data Interpreter (MetaGPT, open-source)
- Category
- Data science agent
- Type
- Open-source agent in the MetaGPT framework (MIT licence), FoundationAgents (formerly DeepWisdom); PyPI metagpt
- Source
- Project repository
- Last reviewed
- 2026-10-17 (what this means)
Summary
Data Interpreter is an open-source data-science agent in the MetaGPT framework. It plans analysis and machine-learning tasks as a graph and writes and runs Python code step by step. Nine independent studies that ran it were found (two peer-reviewed). Its results depend heavily on the model and task. On InfiAgent-DABench, independent re-runs scored 54-80%, against the 94.93% the developers reported; two papers say they could not reproduce that figure. Results ranged from mid-pack on Kaggle-style tabular tasks to 3.3% on an urban data benchmark. In a security study it had the lowest attack success rate of four open-source data agents, but the authors attribute this to limited functionality rather than stronger defences. Seven CVEs have been published for MetaGPT, including two that affect Data Interpreter directly. The project has had no release since March 2025 and no commits since January 2026. Informational only; not a guarantee, endorsement, or certification.
Overall score: 49 · Evidence grade: B · Independent sources: 9 performance (2 peer-reviewed), 6 other
Evidence grade describes the amount and type of evidence, not the agent's quality. Grade B rather than A: 9 counted sources, but fewer than three are peer-reviewed (see methodology).
Factor breakdown
| Factor | Weight | Score | Note |
|---|---|---|---|
| Completion rate | 30% | InfiAgent-DABench (independent re-runs): 75.78% GPT-4o, 67.70% GPT-4o-mini (DatawiseAgent); 54.09-67.70% pass@1 across four open models (DataMind); 0.716-0.788 with GPT-4o / DeepSeek-V3.1 / o4-mini (EvoDS), below a plain ReAct agent in each case. Developers report 94.93%. KramaBench: 0.256-0.382 (Fail Loudly), 30.34% with Gemini 2.5 Pro (Blackboard). Kaggle/OpenML tabular tasks: competitive, close to AIDE (SPIO). Execution stability 0.672-0.676 (VDSAgents). UrbanDS-Bench 3.3% overall. | |
| Disputes | 20% | Seven CVEs for MetaGPT. Data Interpreter components: CVE-2026-4516 (write_analysis_code.py, up to 0.8.1) and CVE-2026-19058 (data_interpreter.py, up to 0.8.2). Framework-wide: CVE-2026-0760 and CVE-2026-0761 (ZDI 0-day advisories after no vendor response), CVE-2024-23750, CVE-2026-19059 and CVE-2026-19060. VulDB records that the vendor did not respond for CVE-2026-4516. No GitHub security advisories published. Two independent papers report being unable to reproduce the headline DABench result. No legal or regulatory action found. | |
| Adherence to limits | 25% | Data Agents Under Attack (NTU, June 2026; DeepSeek-V3.2): mean attack success about 12.9% across 14 techniques (0-56%), the lowest of four open-source data agents. The authors attribute this to limited functionality (frequent failure to connect to the database), not stronger defence. When attacks did connect, Data Interpreter had the largest share of the most severe outcome level (BR4, 9.3%). By design it executes model-written code; no built-in sandbox is documented. | |
| Evidence quality | 25% | Nine independent sources, two peer-reviewed (EMNLP 2025, ICLR 2026), several from 2026. Fewer than three peer-reviewed, so grade B rather than A (0025 clarification). Most sources are competing-agent papers (disclosed). |
0.30 × 45 + 0.20 × 35 + 0.25 × 45 + 0.25 × 70 = 49.25, rounded to 49 (rounding rule).
Scope
The open-source Data Interpreter role in MetaGPT (metagpt/roles/di), run with a language model chosen by the user; MetaGPT releases through 0.8.2 (9 March 2025). MetaGPT's other roles and the commercial MGX / MetaGPT X service are not covered. Results depend heavily on the language model and task, so results are reported as ranges by model.
Version and status note
Data Interpreter is treated as one continuous component from its 2024 release through MetaGPT 0.8.2. The project appears dormant: the last PyPI release was 0.8.2 (9 March 2025) and the last commit to the repository was on 21 January 2026. The repository is not archived.
Disclosures for counted sources
Eight of the nine counted studies propose a competing data-science agent and compare it against Data Interpreter. The ninth, Data Agents Under Attack, is a security study.
Disputes: reproduction gap
The developers report 94.93% on InfiAgent-DABench with GPT-4o. DatawiseAgent (EMNLP 2025) and DataMind (ICLR 2026) report that they could not reproduce this; their re-runs scored 54.09–75.78% depending on the model. This is the papers’ finding; the difference may reflect evaluation settings.
Security
Data Interpreter runs Python code written by the model. Published CVEs (scores as assigned by the named scorer; status as listed by NVD on 17 October 2026):
Data Interpreter components
- CVE-2026-4516: injection in metagpt/actions/di/write_analysis_code.py, MetaGPT up to 0.8.1. CVSS 3.1 6.3 (VulDB). NVD status: Analyzed. VulDB records that the vendor did not respond. No fix identified.
- CVE-2026-19058: code injection in metagpt/roles/di/data_interpreter.py, up to 0.8.2, local attack. CVSS 3.1 5.3 (VulDB). NVD status: Deferred. No fix identified.
MetaGPT framework
- CVE-2026-0760 (deserialize_message) and CVE-2026-0761 (actionoutput_str_to_mapping): CVSS 3.0 9.8 (Zero Day Initiative). Reported to the vendor on 19 September 2025 and published as 0-day advisories on 9 January 2026 after no vendor update. NVD status: Analyzed.
- CVE-2024-23750: QaEngineer role, MetaGPT through 0.6.4. CVSS 3.1 8.8 (NIST).
- CVE-2026-19059 (editor.py path traversal) and CVE-2026-19060 (code injection), up to 0.8.2, local attack. CVSS 3.1 3.3 and 5.3 (VulDB). NVD status: Deferred.
The project has not published any GitHub security advisories. In the Data Agents Under Attack study, Data Interpreter had the lowest attack success rate of four open-source data agents (about 12.9% on average). The authors attribute this to limited functionality (it often failed to connect to the database) rather than stronger defences. When attacks did connect, it had the largest share of the most severe outcome level (9.3%).
Uncertainties
- Results vary widely by model and benchmark; no single figure represents the agent.
- Eight of nine sources are competing-agent papers (all disclosed); only two are peer-reviewed.
- Whether 2026 studies used 0.8.2 or later main-branch code is mostly unstated.
- No fixes have been identified for the Data Interpreter CVEs; the project appears dormant.
Sources
Independent performance sources (counted)
- DatawiseAgent (EMNLP 2025; Peking University et al.): InfiAgent-DABench re-run 75.78% (GPT-4o) and 67.70% (GPT-4o-mini) vs 94.93% reported by the developers; "best-effort replication". Competing-author disclosure: proposes a rival agent — accessed 2026-10-17
- DataMind / Scaling Generalist Data-Analytic Agents (ICLR 2026; Zhejiang University, Alibaba): could not reproduce 94.93%; DABench pass@1 54.09-67.70% and TableBench 27.99-61.98% across DeepSeek-V3.1, Qwen-2.5-72B and Qwen-2.5-Coder 7B/14B. Competing-author disclosure — accessed 2026-10-17
- EvoDS (HKUST, preprint June 2026): average over DABench, DA-Code, ScienceAgentBench and MLE-Dojo 0.288 (GPT-4o), 0.299 (DeepSeek-V3.1), 0.316 (o4-mini); DABench 0.716-0.788. Competing-author disclosure — accessed 2026-10-17
- Fail Loudly (independent researchers, preprint Sept 2026): KramaBench overall 0.301 (DeepSeek V4-Flash), 0.283 (GPT-5.6 Luna), 0.256 (GPT-4.1-mini), 0.382 with gold sources supplied; human 0.768. Competing-author disclosure — accessed 2026-10-17
- Blackboard multi-agent system (UMass Amherst, Google Cloud AI Research; preprint, Jan 2026 v2): KramaBench average 30.34% with Gemini 2.5 Pro (AutoGen 19.30%, Blackboard 37.53%). Competing-author disclosure — accessed 2026-10-17
- SPIO (Enhans, Peking University et al.; preprint, v2 Jan 2026): 8 Kaggle and 4 OpenML tabular datasets with GPT-4o, Claude 3.5 Haiku and LLaMA3-8B; Data Interpreter competitive with AIDE and AutoKaggle (e.g. GPT-4o Titanic 0.7679 acc, Obesity 0.8986). Competing-author disclosure — accessed 2026-10-17
- VDSAgents (preprint Oct 2025): nine tabular tasks; execution stability 0.676 (DeepSeek-V3) and 0.672 (GPT-4o) vs AutoKaggle 0.577/0.534 and VDSAgents 0.894/0.950. Competing-author disclosure — accessed 2026-10-17
- UrbanDS (preprint, v2 Sept 2026): UrbanDS-Bench overall 3.3%, CoDA-Bench 5.0% (AutoGen 45.6/31.1%, Claude Code 62.9/42.0%). Competing-author disclosure — accessed 2026-10-17
- Data Agents Under Attack (NTU, PolyU, Tsinghua; preprint June 2026): 14 attack techniques, DeepSeek-V3.2 backend; Data Interpreter per-technique attack success 0-56% (mean about 12.9%), lowest of four open-source systems; lower exposure attributed to limited functionality; largest BR4 share (9.3%) — accessed 2026-10-17
Other sources (not counted)
- CVE-2026-4516: injection in metagpt/actions/di/write_analysis_code.py (Data Interpreter), up to 0.8.1; CVSS 3.1 6.3 / 4.0 2.1 (VulDB); NVD Analyzed; VulDB says the vendor did not respond; no fix identified — accessed 2026-10-17
- CVE-2026-19058: code injection in metagpt/roles/di/data_interpreter.py, up to 0.8.2, local attack; CVSS 3.1 5.3 / 4.0 1.9 (VulDB); NVD Deferred; no fix identified — accessed 2026-10-17
- CVE-2026-0760 (ZDI-26-026, deserialize_message) and CVE-2026-0761 (actionoutput_str_to_mapping): MetaGPT framework, CVSS 3.0 9.8 (ZDI); reported 19 Sept 2025, published as 0-day advisories 9 Jan 2026 after no vendor update; NVD Analyzed — accessed 2026-10-17
- CVE-2024-23750: MetaGPT through 0.6.4, QaEngineer role RunCode passes shell metacharacters to subprocess; CVSS 3.1 8.8 (NIST); not Data Interpreter — accessed 2026-10-17
- CVE-2026-19059 (editor.py path traversal, CVSS 3.1 3.3) and CVE-2026-19060 (code injection, CVSS 3.1 5.3), up to 0.8.2, local; VulDB; NVD Deferred — accessed 2026-10-17
- Repository status: MIT, about 70.9k stars, not archived; last commit 21 Jan 2026; last PyPI release 0.8.2 (9 Mar 2025); no GitHub security advisories published — accessed 2026-10-17
Not counted
- Data Interpreter paper (Findings of ACL 2025; DeepWisdom/MetaGPT authors): 94.93% InfiAgent-DABench (GPT-4o), ML and MATH results. Developer results, not counted — accessed 2026-10-17
- MetricsAI econometrics study: tests Data Interpreter as a baseline but includes a Data Interpreter co-author (Tuo Zhou). Not counted as independent — accessed 2026-10-17
- Jupiter: reports Data Interpreter 67.7/75.78, copied from DatawiseAgent rather than re-run. Not counted — accessed 2026-10-17
- Studies that mention or wrap Data Interpreter without a standalone test: LAMBDA (qualitative case study), DataSciBench (uses it to generate data), I-MCTS (runs it inside the MetaGPT team’s SELA), surveys, and MetaGPT-team follow-ups (SELA, AFlow).
Decision record: 0029.