Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Mitigations for profound privacy and security issues seem to be missing?

Abierto
  • ¿Algo no está bien?
#313 8 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
html
Área
security

Línea de trabajo

Start by reading the issue thread and the WebMCP specification, then review the Privacy Working Group discussion mentioned in the report. The issue describes broad privacy and security threats but does not identify specific files or a bounded change; done would require agreed mitigations for attacks by malicious site authors.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Agenda+ beyond-scope: agents-on-the-web privacy-needs-resolution

These are among the largest and most diverse set of security and privacy threats introduced by a single spec -- a malicious website can very likely access huge amounts of personal information from the user, including from other origins (all of their emails, say), other browsing history, or other sensitive sources, without any user involvement or awareness, and even take consequential actions that cost the user money, spread the harms to other people, hurt reputations, etc.

But there mostly don't seem to be any mitigations? Hopefully the implementers will share notes in real time about all the prompt injection attacks that they encounter? A few of these mitigations are aimed at site authors, but the largest threats are when the site author is the attacker.

The Privacy Working Group discussed this briefly, but the reaction was mostly that the threats are severe and that the protections seem to just be missing. I recognize that many implementers are shipping various agentic browsing tools that already suffer from many of these threats, but, this seems to provide a well-suited surface for large-scale open-ended attacks.

Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Security

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.