T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:132- Finding
Overbroad Access to Persistent Agent Memory and User Context
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This daily briefing skill is purpose-aligned, but it can surface sensitive tasks, meetings, calendar items, and agent memory from broad everyday trigger phrases without clear per-source consent.
Install only if you are comfortable with the skill reading and summarizing your task list, recent meeting notes, calendar data, and optional memory/profile files into chat output. Use explicit briefing commands, avoid invoking it while screen sharing unless the audience should see that context, and consider disabling or removing access to MEMORY.md, USER.md, or calendar sources unless you intentionally want them included.
SKILL.md:132Overbroad Access to Persistent Agent Memory and User Context
README.md:7Unpinned Remote Sources in Installation Instructions
The skill is designed to read potentially sensitive sources including todo.md, meeting-notes/, MEMORY.md, session memory files, and calendar data, but the user-facing description says "No setup. Just say 'briefing'" without warning that personal and organizational data will be accessed. This weakens informed consent and increases the chance users invoke the skill casually, not realizing it may aggregate private tasks, meeting decisions, deadlines, and memory content into a response.
The trigger phrases include broad, natural-language requests such as "what do I need to know?", "start my day", and "give me the rundown," which can plausibly appear in unrelated conversations. In a skill-routing environment, this can cause the skill to activate unexpectedly and read from local task lists, meeting notes, memory files, or calendar sources, exposing sensitive personal or workplace context without sufficiently explicit user intent.
Using the single word trigger "briefing" is overly generic and can easily appear in normal conversation, making accidental invocation plausible. In a skill that aggregates tasks, calendars, and meeting-note context, unintended activation could expose sensitive productivity data or cause the assistant to act in the wrong context.
The phrase "what's today look like?" is common conversational language and not clearly bound to this skill. Because this skill surfaces personal schedule and work context, broad matching raises the risk of accidental invocation and unintentional disclosure of calendar items, priorities, or recent meeting content.
The trigger "what's overdue?" is short, generic, and likely to occur in unrelated conversations about tasks or deadlines. In this skill's context, an unintended match could reveal overdue items and associated business context to the wrong user or at the wrong time.
The example activation phrases include very common conversational language such as "what's on my plate?" and "start my day," which can overlap with ordinary user speech and unintentionally trigger the skill. In a briefing skill that surfaces calendar items, overdue tasks, and meeting-derived context, accidental activation can expose sensitive personal or work information at the wrong time or in front of unintended viewers.
The quick-start text promotes automatic surfacing of to-do items, calendar meetings, conflicts, and contextual background without warning users that potentially sensitive data will be aggregated and displayed. This lack of disclosure increases the risk of inadvertent privacy exposure, especially in shared screens, public spaces, or when users do not realize linked systems are being queried automatically.
"Weekly preview" is less common than the other phrases but is still generic enough to be triggered unintentionally in routine planning discussions. The resulting disclosure risk is somewhat lower, but the skill still exposes potentially sensitive schedule and task summaries when invoked without strong boundaries.
No suspicious patterns detected.