PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-6111 FoundationAgents CVE debrief

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.

Vendor
FoundationAgents
Product
MetaGPT
CVSS
LOW 2.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-12
Original CVE updated
2026-10-26
Advisory published
2026-04-12
Advisory updated
2026-10-26

Who should care

Defenders responsible for FoundationAgents MetaGPT deployments should assess exposure to remote attacks and verify the presence of vulnerable versions. They should also monitor for potential exploitation attempts and review compensating controls for exposed systems. Security teams and vulnerability management teams should prioritize verifying the presence of vulnerable MetaGPT versions and assessing exposure to remote server-side request forgery attacks.

Why it matters

Defenders should prioritize verifying the presence of vulnerable MetaGPT versions and assessing exposure to remote server-side request forgery attacks.

  • Verify the presence of vulnerable MetaGPT versions
  • Assess exposure to remote server-side request forgery attacks
  • Monitor for potential exploitation attempts

Technical summary

The vulnerability is located in the decode_image function of the metagpt/utils/common.py file in FoundationAgents MetaGPT up to version 0.8.1. The manipulation of the img_url_or_b64 argument leads to server-side request forgery, allowing for remote attacks. This could potentially allow attackers to access unauthorized resources or perform actions on behalf of the server. 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.

Defensive priority

Defenders should prioritize verifying the presence of vulnerable MetaGPT versions and assessing exposure to remote attacks.

Recommended defensive actions

  • Verify the presence of vulnerable MetaGPT versions in your environment
  • Assess exposure to remote attacks
  • Monitor for potential exploitation attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. Defenders should verify the presence of vulnerable MetaGPT versions and assess exposure to remote server-side request forgery attacks. The project was informed of the problem early through an issue report but has not responded yet with a patch or fix. Limited evidence is available on exploitation attempts or specific impacted systems.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-6111 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-6111

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-6111 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-6111

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.