GHSA-XV4X-G8MX-CH56
Provider-native MCP credentials and URL-derived MCP identifiers could reach traces
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-XV4X-G8MX-CH56 divulgada · CVSS 6.5 (GitHub) | |
| Remediación | Parche 1.107.8 | pydantic-ai · 0 d desde divulgación | |
| Remediación | Parche 2.58.0 | pydantic-ai · 0 d desde divulgación | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
Provider-native MCP credentials and URL-derived MCP identifiers could reach request telemetry.
Details
With request instrumentation enabled, provider-native MCP tools (`MCPServerTool`, including `MCP(native=True)`) could export server URLs, authorization tokens, and custom header values in OpenTelemetry request traces, even with `include_content=False`. Separately, a URL-based `MCP` capability running locally could expose an identifier derived from the URL's hostname and final path segment. A credential in that path segment could therefore appear in a trace. Anyone with access to affected traces could read the exposed values.
On v1, `MCP(url=...)` uses provider-native MCP by default when the model supports it; on v2, local MCP is the default. A plain `MCPToolset` passed directly through `toolsets=` with a caller-chosen identifier is not affected by these paths.
On v2, Temporal durable execution also names its MCP activities after the URL-derived identifier. With Temporal tracing enabled, including through `LogfirePlugin`, that identifier appears in activity span names. Patched versions keep these activity names, because renaming them would break in-flight workflows.
Mitigation
Upgrade `pydantic-ai` and `pydantic-ai-slim` to patched versions on the maintained v2 or v1 line. Restrict access to historical traces and rotate credentials those traces exposed.
If you run a URL-based `MCP` capability under Temporal with tracing enabled, also pass an explicit `id=` to `MCP`. Make this change once in-flight workflows complete, because it renames the MCP activities.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
pypipydantic-ai |
Corregida | 1.107.8, 2.58.0 | 0 d · 0 d | 2.68.0 no afectada |
pypipydantic-ai-slim |
Corregida | 1.107.8, 2.58.0 | 0 d · 0 d | 2.71.0 no afectada |
1.107.82.58.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/pydantic/pydantic-ai/security/advisories/GHSA-xv4x-g8mx-ch56Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
