Skip to main content
VulnerabilityPublished

CVE-2026-123272: mark3labs mcp-go · Origin Validation Error

Affects mark3labs mcp-goSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to v1.2.1 when convenient.

Data as of 5 Nov 2026, 19:05 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.1
CNA (VulnCheck)CVSS 3.18.0
Patch
Available – fixed in v1.2.1, 1.2.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade mcp-go to v1.2.1; mcp-go to 1.2.1.

Affected software

ProductAffectedFixed in
mark3labsmcp-goAffected
  • >=0.48.0 <1.2.1
Fixed in
  • v1.2.1
Gomcp-gopkg:golang/mcp-goOther threatsAffected
  • >=0.48.0 <1.2.1
Fixed in
  • 1.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade mark3labs mcp-go to version 1.2.1 or later, where this origin validation vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

Mark3labs mcp-go versions before 1.2.1 have an origin validation vulnerability in the OAuthHandler.fetchServerMetadata function. This flaw allows malicious MCP servers to declare arbitrary resources in well-known metadata, causing the authorization server to issue tokens for unintended resources. Attackers can exploit this by declaring a different MCP server as the RFC 8707 resource indicator and replaying the obtained tokens against that resource. The issue is fixed in version 1.2.1.

References

Community reviews

Loading reviews…