cve.bz

CVE-2025-64168 agno-agi agno: Race Condition

7.1 highEPSS 0.2%Fix available

High (7.1) in agno-agi agno. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in agno 2.2.2.

On this page
Agno 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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-31. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • agno (PyPI): fixed in 2.2.2

Ask an AI about this CVE

Show the promptExplain CVE-2025-64168 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-64168?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-64168?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-64168 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
agno-agi agno>= 2.0.0, < 2.2.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vw84-hprm-cxmmPyPIagno>=2.0.0 <2.2.22.2.2
PYSEC-2026-1077PyPIagno>=2.0.0 <2.2.22.2.2

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON