How severe is GHSA-m4w4-3r8h-jw98?

GHSA-m4w4-3r8h-jw98 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-m4w4-3r8h-jw98?

GHSA-m4w4-3r8h-jw98 affects the following packages: agno (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-m4w4-3r8h-jw98?

Update agno to 2.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4w4-3r8h-jw98 is resolved across your whole dependency graph.

How do I detect GHSA-m4w4-3r8h-jw98 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for agno, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m4w4-3r8h-jw98 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-m4w4-3r8h-jw98 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4w4-3r8h-jw98 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m4w4-3r8h-jw98?

GHSA-m4w4-3r8h-jw98 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m4w4-3r8h-jw98?

GHSA-m4w4-3r8h-jw98 is classified as CWE-95 (CWE-95). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m4w4-3r8h-jw98 published, and has it been updated?

GHSA-m4w4-3r8h-jw98 was published on October 27, 2026 and was last updated on October 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

Agno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`GHSA-m4w4-3r8h-jw98

CRITICALFix: agno-agi/agno@cbf6755

GHSA-m4w4-3r8h-jw98 is a critical-severity (CVSS 9.8) CWE-95 vulnerability in agno. A fix is available for agno — see the affected versions and patch details below.

Also known asCVE-2026-35002 GHSA-77rh-m34w-rv36PYSEC-2026-256

Published

Oct 27, 2026

Updated

Oct 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m4w4-3r8h-jw98.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍agno

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Agno versions prior to 2.3.24 contain an arbitrary code execution vulnerability in the model execution component. The field_type parameter on a FunctionCall input field was passed to Python's built-in eval(), allowing an attacker who could influence that value to execute arbitrary Python code in the Agno process.

This is a code injection flaw (CWE-95) with full impact to confidentiality, integrity, and availability. CVSS 3.1 score: 9.3 (Critical).

Any deployment that exposes Agno to user-influenced FunctionCall inputs (for example via an API, web UI, or untrusted tool/model output) is affected.

Patches

Fixed in Agno 2.3.24.

The unsafe eval() call was replaced with a fixed type_mapping dictionary lookup, and field_type is now validated as either a known string key or an already-resolved type object before use. See commit cbf67552 (PR #5912).

All users should upgrade to 2.3.24 or later. The current release line (2.6.x) includes the fix.

Workarounds

There is no safe workaround. Users who cannot upgrade should ensure no untrusted input can reach the field_type parameter of FunctionCall input fields, but upgrading is strongly preferred.

References

Patch commit: https://github.com/agno-agi/agno/commit/cbf675521d4d2281925a051784a3b94172e56416
Patch PR: https://github.com/agno-agi/agno/pull/5912
CWE-95: https://cwe.mitre.org/data/definitions/95.html

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`agno`	all versions	2.3.24`pip install --upgrade 'agno==2.3.24'`

Affected Products

1 product · 1 configurations

Application

agnoagno

< 2.3.24

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for agno, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update agno to 2.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4w4-3r8h-jw98 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Agno versions prior to 2.3.24 contain an arbitrary code execution vulnerability in the model execution component. The `field_type` parameter on a `FunctionCall` input field was passed to Python's built-in `eval()`, allowing an attacker who could influence that value to execute arbitrary Python code in the Agno process. This is a code injection flaw (CWE-95) with full impact to confidentiality, integrity, and availability. CVSS 3.1 score: 9.3 (Critical). Any deployment that exposes Agno to user-influenced FunctionCall inputs (for example via an API, web UI, or untrusted tool/model