Is CVE-2026-6111 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-6111 being exploited in the wild.

How severe is CVE-2026-6111?

Medium severity, with a CVSS score of 6.3, published 12 April 2026.

Which products and versions are affected?

metagpt (PyPI) ECOSYSTEM:introduced=0,last_affected=0.8.2.

Is there a fix for CVE-2026-6111?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-6111 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-6111?

Check whether you run metagpt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-6111: FoundationAgents MetaGPT SSRF in decode_image

CVE-2026-6111 · Severity: medium · CVSS 6.3 · Published 2026-04-12

MetaGPT, a multi-agent framework for software development, is vulnerable to a security flaw that allows attackers to force the server to make unauthorized network requests. By providing a malicious URL instead of an image, an attacker could potentially access internal company services, scan private networks, or steal cloud service credentials. This could lead to the exposure of sensitive internal data or unauthorized access to cloud infrastructure.

Technologies: metagpt (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-6111 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6111 being exploited in the wild.
How severe is CVE-2026-6111?: Medium severity, with a CVSS score of 6.3, published 12 April 2026.
Which products and versions are affected?: metagpt (PyPI) ECOSYSTEM:introduced=0,last_affected=0.8.2.
Is there a fix for CVE-2026-6111?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-6111 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-6111?: Check whether you run metagpt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in MetaGPT versions up to and including 0.8.2. The vulnerability is located in the `decode_image` function within `metagpt/utils/common.py`, specifically due to insufficient validation of the `img_url_or_b64` argument. When a URL starting with 'http' is provided, the application uses the `requests.get()` method without verifying the destination. A remote attacker with low privileges can exploit this to perform non-blind SSRF, allowing them to access internal network resources (localhost, private IP ranges), fetch cloud metadata (AWS/Azure/GCP), or perform internal port scanning. While a pull request (#1941) has been proposed to implement URL validation and IP filtering, it has not been officially merged into a released version as of the advisory date.

Affected products

FoundationAgents MetaGPT <= 0.8.2

Identifiers

CVE-2026-6111
GHSA-r5v8-c28h-f8r8
PYSEC-2026-2642

Timeline

2026-02-11: other: Pull request with fix submitted by community member
2026-04-12: advisory: GitHub Advisory and NVD entry published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.