Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

FEAT: Cross-principal memory leakage scenario for agents with shared long-term memory

オープン
  • 何か問題がありますか？
#3,272 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
security

調査の方向性

The payload names the existing Leakage scenario and the substring/regex scorers as reference points, but no file paths. Start by reading how Leakage and those scorers are built, and ask the maintainers how multi-principal targets should be modelled before writing code. Done means a two-phase scenario that seeds canaries as one identity, probes as another, and reports leak rate per probe strategy.

索引モデルが issue の本文から書いたものです。

説明

feature-request
Is your feature request related to a problem? Please describe.

The Leakage scenario tests whether a model discloses training data, PII or confidential
information. It doesn't cover a growing agent-specific path: data that one user was entitled
to see is written into a shared long-term memory (e.g. a workspace-level store), and later
retrieved for a different user who is not entitled to it.

In this pattern, each individual check passes. The source query is authorized for user A,
the memory read is authorized by namespace or workspace membership for user B, and keyword
input/output filters pass because the second user's questions don't use restricted terms.
The leak exists only across sessions and principals, so single-conversation probing doesn't
surface it.

Two public descriptions of the pattern are in the OWASP GenAI Data Security Initiative's
trace dataset (memory_read_write category): an unintentional variant
(GenAI-Security-Project/GenAI-Data-Security-Initiative#102) and an adversarial variant where
a member deliberately words queries to extract restricted derived items (#104). Related
published work on query-only extraction from agent memory: Wang et al., "Unveiling Privacy
Risks in LLM Agent Memory" (arXiv:2502.13172).

Describe the solution you'd like

A scenario that runs in two phases against an agent target that supports per-user identity:

  1. Seed: as principal A, send prompts that cause the agent to read restricted data and
    persist something derived from it. Restricted values are unique canary tokens, so leakage
    can be detected deterministically.
  2. Probe: as principal B, who lacks the entitlement, send benign and adversarial
    (paraphrased, keyword-free, verbatim-recall) prompts drawn from a seed dataset.
  3. Score: a true/false scorer that flags any of A's canaries in B's responses. This could
    build on the existing substring/regex scorers, with no LLM judge needed.

Output: leak rate per probe strategy, which shows whether keyword filtering vs.
entitlement-aware memory reads actually stops the path.

Describe alternatives you've considered, if relevant
  • Extending Leakage directly. It's model-focused and single-principal, so a separate
    scenario (or a clearly separate technique set) seems cleaner, but I'm happy to follow your
    preference.
  • Shipping it as an external example notebook rather than a built-in scenario.
Additional context

I'd like to implement this if it fits PyRIT's direction, starting with the seed dataset and
the canary scorer, then the scenario. Guidance on how you'd want multi-principal targets
modelled would be very helpful before I start.

Disclosure: I contributed the two OWASP traces referenced above and have published on
lineage-aware access control for agent memory.

主要言語
Python
スター
4.6k
フォーク
962
平均マージ
2日 16時間
マージ済み PR（30日）
354

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

microsoft/PyRIT のほかの issue

microsoft/PyRIT の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。