# CVE-2026-6111: FoundationAgents MetaGPT common.py decode_image server-side request forgery

> Attackers can exploit a server-side request forgery flaw in MetaGPT's image decoding function to access internal resources or bypass security controls.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-r5v8-c28h-f8r8, PYSEC-2026-2642

## What is CVE-2026-6111?

CVE-2026-6111 is a medium-severity server-side request forgery vulnerability in FoundationAgents MetaGPT, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in FoundationAgents MetaGPT up to 0.8.1. This impacts the function decode_image of the file metagpt/utils/common.py. The manipulation of the argument img_url_or_b64 results in server-side request forgery. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-6111?

3 open source packages ship an affected version, including metagpt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `metagpt` | PyPI | All versions to 0.8.2 | None |
| `metagpt` | PyPI | All versions to 0.8.2 | None |
| `metagpt` | PyPI | All versions to 0.8.2 | None |

Products: Deepwisdom Metagpt.

## How do I fix CVE-2026-6111?

No fix has been published for CVE-2026-6111 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6111 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6111 exists.

Public exploit code:

- this is poc test job (github_poc): https://github.com/MonsterWsr-hub/CVE-2026-6111

## Other vulnerabilities in FoundationAgents MetaGPT

- [CVE-2026-0760](https://insights.sbomify.com/CVE-2026-0760/): Foundation Agents MetaGPT deserialize_message Deserialization of Untrusted Data Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-0761](https://insights.sbomify.com/CVE-2026-0761/): Foundation Agents MetaGPT actionoutput_str_to_mapping Code Injection Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-23750](https://insights.sbomify.com/CVE-2024-23750/): Code execution in metagpt (high 8.8)
- [CVE-2026-6110](https://insights.sbomify.com/CVE-2026-6110/): FoundationAgents MetaGPT Tree-of-Thought Solver tot.py generate_thoughts code injection (medium 6.9)
- [CVE-2026-5970](https://insights.sbomify.com/CVE-2026-5970/): FoundationAgents MetaGPT HumanEvalBenchmark/MBPPBenchmark check_solution code injection (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6111 and fix it if it is affected.

What it is: CVE-2026-6111 is a medium-severity server-side request forgery vulnerability in FoundationAgents MetaGPT, published on 12 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6111 exists.

Affected packages and fixed versions:
- metagpt (PyPI): affected all versions up to 0.8.2; no fix listed
- metagpt (PyPI): affected all versions up to 0.8.2; no fix listed
- metagpt (PyPI): affected all versions up to 0.8.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6111/ (Markdown: https://insights.sbomify.com/CVE-2026-6111/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6111
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6111
- OSV: https://osv.dev/vulnerability/CVE-2026-6111

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6111/
Summaries are generated and may contain mistakes; the official description above is the record.