A ContextForge tool or resource request could carry gateway user identity to an upstream MCP server even when its specific identity-propagation setting was disabled. The reported issue combines two boundaries: signed identity-claim material remained replayable without sufficient freshness and selected paths ignored the server-specific propagation opt-out.…
Inspect the ClaimsCase · DiggingBeagle record
ContextForge identity propagation could reveal identity data despite a disabled per-server setting
A ContextForge tool or resource request could carry gateway user identity to an upstream MCP server even when its specific identity-propagation setting was disabled.
Public disclosure: Nov 13, 2026
An authenticated agent gateway forwards tool/resource calls to an upstream server whose identity-propagation setting is off.
At a glance
A per-server privacy flag is not authoritative if the lower-level forwarding code still attaches replayable identity material.
Read the implicationsThis is not the same issue as credential override CVE-2026-110279. Claim replay and disclosure contrary to configuration require different tests from authorization to issue an upstream call.
Limits and uncertaintyFull account
A ContextForge tool or resource request could carry gateway user identity to an upstream MCP server even when its specific identity-propagation setting was disabled.
The reported issue combines two boundaries: signed identity-claim material remained replayable without sufficient freshness and selected paths ignored the server-specific propagation opt-out. That exposes user identifiers, email addresses, group or team context to an unintended recipient under affected configurations.
The advisory identifies CVE-2026-110278 and a 1.1.1 fix. A leak is conditional on the upstream path and configuration; no independently confirmed replay or third-party extraction was established by the cited report.
This is not the same issue as credential override CVE-2026-110279. Claim replay and disclosure contrary to configuration require different tests from authorization to issue an upstream call.
Mechanism and trust boundary
- 01
Starting condition
An authenticated agent gateway forwards tool/resource calls to an upstream server whose identity-propagation setting is off.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
The reported issue combines two boundaries: signed identity-claim material remained replayable without sufficient freshness and selected paths ignored the server-specific propagation opt-out. That exposes user identifiers, email addresses, group or team context to an unintended recipient under affected configurations.
Boundary: mechanism
- 03
Observed consequence
A per-server privacy flag is not authoritative if the lower-level forwarding code still attaches replayable identity material.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-CF110278-MECHA ContextForge tool or resource request could carry gateway user identity to an upstream MCP server even when its specific identity-propagation setting was disabled. The reported issue combines two boundaries: signed identity-claim material remained replayable without sufficient freshness and selected paths ignored the server-specific propagation opt-out. That exposes user identifiers, email addresses, group or team context to an unintended recipient under affected configurations.supported
Basis: reported finding
- supportsContextForge replayable identity propagation, CVE-2026-110278primary disclosure
GitHub Advisory GHSA-774m-v6g3-r639, Description and mitigation
CLM-NOV15-CF110278-SCOPEThe advisory identifies CVE-2026-110278 and a 1.1.1 fix. A leak is conditional on the upstream path and configuration; no independently confirmed replay or third-party extraction was established by the cited report. This is not the same issue as credential override CVE-2026-110279. Claim replay and disclosure contrary to configuration require different tests from authorization to issue an upstream call.supported
Basis: reported finding
- supportsContextForge replayable identity propagation, CVE-2026-110278primary disclosure
Primary disclosure: results, scope and limitations
Implications
A per-server privacy flag is not authoritative if the lower-level forwarding code still attaches replayable identity material.
Controls and mitigations
- Upgrade ContextForge and test identity propagation at each tool/resource route with a synthetic account.
- Bind delegated identity claims to an intended upstream audience and short freshness window; inspect actual outbound headers, not only configuration state.
Unknowns and contradictions
- This is not the same issue as credential override CVE-2026-110279. Claim replay and disclosure contrary to configuration require different tests from authorization to issue an upstream call.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250