CVE-2025-64168
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAgno is a multi-agent framework, runtime and control plane. From 2.0.0 to before 2.2.2, under high concurrency, when session_state is passed to Agent or Team during run or arun calls, a race condition can occur, causing a session_state to be assigned and persisted to the incorrect session. This may result in user data from one session being exposed to another user. This has been patched in version 2.2.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition in the Agno multi-agent framework (versions 2.0.0 to 2.2.1) causes session_state to be incorrectly assigned across sessions during concurrent Agent or Team run/arun calls. Under high concurrency, session data from one user can be exposed to another user due to improper session state management.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Agno versionRun `pip show agno` or `pip list | grep -i agno` to identify the installed version numberAffected if Version is 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, or 2.2.1
-
Identify concurrent Agent.run or Team.run usageSearch your codebase for patterns where agent.run(), agent.arun(), team.run(), or team.arun() are called concurrently (within async functions, ThreadPoolExecutor, multiprocessing, or loop structures)Affected if Multiple Agent or Team run/arun calls execute simultaneously and share session_state
-
Inspect session_state for sensitive dataReview code where session_state is populated or accessed; check if it contains user credentials, tokens, PII, or other sensitive information that should not cross sessionsAffected if session_state holds user-specific sensitive data and is used in concurrent contexts
-
Check for multi-user or high-concurrency deploymentExamine your deployment to determine if multiple users or high request volumes trigger concurrent agent executions (check web server logs, load balancer configs, or application metrics for concurrent request patterns)Affected if Your application serves multiple users or handles high-concurrency requests using Agno agents
You are likely affected if running Agno 2.0.0-2.2.1 with concurrent Agent/Team run/arun calls where session_state contains user-specific data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Agno version 2.2.2 or later to patch the race condition. Until upgraded, avoid high-concurrency scenarios or implement application-level session isolation as a temporary workaround.
2.2.2 or later
- Check current installed version of agno (pip show agno or pip list | grep agno)
- Upgrade to version 2.2.2 or later using: pip install --upgrade agno>=2.2.2
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-64168 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data