CVE-2026-6111

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-04-12. NVD baseline CVSS 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 12, 2026

Last Modified

April 30, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Fix referenced — no release confirmed yet. Sources: github_pr.
GitHub pull request

Security Fix: Prevent SSRF vulnerability in decode_image() function - Fixes #1934

Upstream fix in progress (PR #1941 · FoundationAgents/MetaGPT, state=open)

https://github.com/FoundationAgents/MetaGPT/pull/1941
Web page

Non-Blind SSRF with File Write in download_model() · Issue #1934 · FoundationAgents/MetaGPT · GitHub

https://github.com/FoundationAgents/MetaGPT/issues/1934
Web page

GitHub - FoundationAgents/MetaGPT: 🌟 The Multi-Agent Framework: First AI Software Company, Towards Natural Language Programming · GitHub

https://github.com/FoundationAgents/MetaGPT/

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmetagpt—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
metagpt0.1 ... 0.8.2 (30 versions)
  • every version through 0.8.2: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 198 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-10-12 15:51 UTCEG score recompute
  7. 2026-10-11 19:35 UTCEG score recompute
  8. 2026-10-11 16:50 UTCEG score recompute
  9. 2026-10-11 14:12 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-10-10 20:33 UTCOSV refresh
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 70 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-09-21 07:49 UTCOSV refresh
  4. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-09-02 05:36 UTCOSV refresh
  17. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  18. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  23. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  27. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  28. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  30. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  31. 2026-08-16 06:59 UTCEG score recompute
  32. 2026-08-16 06:59 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  33. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  35. 2026-08-14 04:59 UTCEG score recompute
  36. 2026-08-14 04:59 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  37. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-08-12 19:13 UTCEG score recompute
  39. 2026-08-12 19:13 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  40. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  41. 2026-08-11 06:35 UTCEG score recompute
  42. 2026-08-11 06:35 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  43. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  44. 2026-08-10 05:29 UTCEG score recompute
  45. 2026-08-10 05:29 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  46. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  47. 2026-08-09 04:24 UTCEG score recompute
  48. 2026-08-09 04:24 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  49. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-08-07 14:10 UTCEG score recompute
  51. 2026-08-07 14:10 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  52. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  53. 2026-08-05 23:37 UTCEG score recompute
  54. 2026-08-05 23:37 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  55. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  56. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  57. 2026-08-04 10:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-08-03 21:52 UTCEG score recompute
  59. 2026-08-03 21:52 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  60. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  61. 2026-08-02 13:38 UTCEG score recompute
  62. 2026-08-02 13:38 UTCGHSA enrichmentGHSA-r5v8-c28h-f8r8 · GitHub severity LOW · GitHub CVSS 6.3
  63. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  64. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  65. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  67. 2026-07-28 15:37 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  68. 2026-07-27 14:14 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  69. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  70. 2026-07-25 14:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-6111?
CVE-2026-6111 is a medium-severity vulnerability; its CVE record was published on April 12, 2026. A security flaw has been discovered in FoundationAgents MetaGPT up to 0.8.1. This impacts the function decodeimage of the file metagpt/utils/common.py. The manipulation of the argument imgurlorb64 results in server-side request forgery. It is possible to launch the attack remotely. The exploit has…
When was the CVE record for CVE-2026-6111 published?
The CVE record for CVE-2026-6111 was published on April 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 30, 2026; the record at its source may have been updated since.
Is CVE-2026-6111 actively exploited?
CVE-2026-6111 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6111?
CVE-2026-6111 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-6111?
A fix for CVE-2026-6111 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6111

Explore →

Is Your Infrastructure Affected by CVE-2026-6111?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs