Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
loom-logs-owner — A Loom user who can read sessions in an agent's group can read another user's prompts and answers from logs, traces, and evaluation exchange. Opening the session itself is still forbidden. v1.9.0 and v1.10.3. Medium 6.5. | Kitploit
Tools/GitHubGitHub/abraxas/loom-logs-owner
Authentication & AuthorizationVulnerability AnalysisExploitationWeb SecurityPenetration Testing
GitHubabraxas/loom-logs-owner

loom-logs-owner

A Loom user who can read sessions in an agent's group can read another user's prompts and answers from logs, traces, and evaluation exchange. Opening the session itself is still forbidden. v1.9.0 and v1.10.3. Medium 6.5.

View Repository
2 days agoNot yet reviewed
Share

Abraxas Labs - loom-logs-owner

loom-logs-owner

A person in the same group as an agent, with permission to read sessions, can open another person's prompts and answers in the logs, the traces, and the evaluation exchange. Asking for the session itself is still forbidden.

Another group's agent stays forbidden. This is not a cross-group read.

Class: Missing per-session owner check on conversation text Reach: Remote. session:read and agent:read in the agent's loom:group. The lab caller is a normal user in that group, not an admin of the tenant.

Loom v1.9.0 a3050669 and v1.10.3 cc10ab0

IDno CVE yet
ClassSame-group session-owner bypass on logs, traces, and eval exchange
ReachRemote, in-group t-user
CWECWE-639
CVSSMedium: 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Productawslabs/loom
Affectedv1.9.0 a3050669f5b4c83210a44ed4346f17e01641e82f and v1.10.3 cc10ab08573087fa12154f7c8181ffcd985fea88
Authg-users-* matching the agent tag
LicenseGNU Affero GPL v3.0
Labloopback Docker on v1.9.0. v1.10.3 was a source check.

What an attacker can do

PrivilegeMethod / sinkImpactLab-proven or inferred
Read their own sessionGET /api/agents/{id}/sessions/{sid} as the ownerRecon of their own rowLab-proven. Alice 200.
Be refused the other person's sessionthe same GET as a different userClosedLab-proven. Bob 403.
Read that person's prompt and answer in runtime logsGET .../sessions/{sid}/logsConfidentialityLab-proven. Bob logs 200, witness in the body.
Read span input and outputGET .../traces/{tid}ConfidentialityLab-proven. Traces 200, witness present.
Read prompt and answer from an evaluationGET /api/agents/{id}/evaluations/traces/{tid}/exchangeConfidentialityLab-proven. Exchange 200. Same missing owner check, not a second bug. agent:read on the shipped group map already comes with session:read.

Stays closed

AxisMethod / sinkWhy it is closed
ConfidentialityAnother group's agentCharlie's log read was 403
ConfidentialityA caller-picked log group nameVended log groups stay on the allowlist
ConfidentialitySession body for a non-ownerassert_session_readable
ConfidentialityAn in-group admin reading transcriptsIntended. t-admin for that tag may read.

How I found it

Session GET grew an owner check. The CloudWatch readers that return the same conversation call get_agent_or_404 and then fetch the log stream. _resolve_agent_and_log_group never calls assert_session_readable. The evaluation exchange was already on agent:read in v1.9.0 and still is.

I ran the container on v1.9.0. On v1.10.3 the resolver is the same shape.

Lab

python3 loom-logs-owner-Abraxas-Labs.py
SUCCESS LOOM-190-LOGS-OWNER alice-session=200 bob-session=403 logs=200 logs-has-witness=yes charlie-logs=403 exchange=200 exchange-has-witness=yes traces=200 traces-has-witness=yes LOOM-190-LOGS-OWNER-WITNESS

The fix

Call assert_session_readable from the log, trace, and evaluation-exchange handlers before the body is read. Group membership is the wrong grain for another person's prompt.

References

  • awslabs/loom v1.10.3 cc10ab08573087fa12154f7c8181ffcd985fea88
  • logs.py _resolve_agent_and_log_group
  • CWE-639
  • CVSS 3.1 calculator

License

GNU Affero GPL v3.0. See LICENSE. Loopback lab only. No warranty.

Abraxas Labs [email protected]

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    927
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    555
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    360
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    357
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    324
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    289

Explore all tools

Browse our collection of tools

View all tools →