Skip to content

fix: resolve multi-user session hijacking in LinkedIn agent#132

Open
SunkariManwithaGopal wants to merge 1 commit into
fetchai:mainfrom
SunkariManwithaGopal:fix/linkedin-agent-session-hijacking
Open

fix: resolve multi-user session hijacking in LinkedIn agent#132
SunkariManwithaGopal wants to merge 1 commit into
fetchai:mainfrom
SunkariManwithaGopal:fix/linkedin-agent-session-hijacking

Conversation

@SunkariManwithaGopal
Copy link
Copy Markdown

@SunkariManwithaGopal SunkariManwithaGopal commented May 25, 2026

Closes #130

Replace global LinkedInAgent singleton with per-sender session management. Each incoming sender now gets an isolated LinkedInAgent instance via a user_sessions dictionary, preventing cross-user state corruption of auth flows (connection_request, connected_account, user_id). Fixes BOLA / session hijacking vulnerability where concurrent users could overwrite each other's LinkedIn credentials and execute actions on another user's account.

Summary

Describe what this PR changes.

Type of Change

  • New agent example
  • Bug fix
  • Documentation update
  • Refactor / cleanup
  • Other

Checklist

  • I have starred this repository.
  • New community agents are under contributors/<agent-name>/ (not repo root).
  • I ran ruff check ..
  • I ran ruff format ..
  • I added/updated README.md for changed example(s).
  • I added .env.example if environment variables are required.
  • I added demo image/GIF (if applicable).
  • I added agent profile link (if applicable).
  • I updated contributors/CHANGELOG.md for community agent changes, or root CHANGELOG.md for other non-doc changes.
  • I added my agent to the Community Contributors table in root README.md (if new agent).
  • I verified paths/commands used in docs.
  • I understand this PR requires maintainer review before merge (review-required CI).

Related Issue

Link issue number(s), if any:

Notes for Reviewers

Anything reviewers should focus on.

Replace global LinkedInAgent singleton with per-sender session management. Each incoming sender now gets an isolated LinkedInAgent instance via a user_sessions dictionary, preventing cross-user state corruption of auth flows (connection_request, connected_account, user_id). Fixes BOLA / session hijacking vulnerability where concurrent users could overwrite each other's LinkedIn credentials and execute actions on another user's account.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Multi-User Session Hijacking & Global State Collision in LinkedIn Agent

1 participant