dbcve.org
CWE-693Weakness · CWE-693

CVE-2026-61437

HIGH · 7.8 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges 6 weeks old

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 · unedited
PraisonAI (pip package praisonaiagents) before 1.6.78 contains an unsafe dynamic module loading vulnerability in AgentFlow._resolve_pydantic_class (src/praisonai-agents/praisonaiagents/workflows/workflows.py). When a workflow step uses a string output_pydantic reference, the framework locates and imports a sibling tools.py from the workflow file's directory via importlib exec_module without sandboxing, ignoring the PRAISONAI_ALLOW_*_TOOLS environment variables. An attacker who controls a workflow file and its sibling tools.py can execute arbitrary Python code with the workflow runner's privileges when the workflow is executed via WorkflowManager or after load_yaml.

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 confidence

PraisonAI before 1.6.78 has an unsafe dynamic module loading vulnerability in AgentFlow._resolve_pydantic_class. The method imports a sibling tools.py from the workflow file's directory using importlib.exec_module without sandboxing when resolving string output_pydantic references, ignoring security environment variables. An attacker who controls both a workflow file and its sibling tools.py can achieve arbitrary code execution.

MitigationUpgrade praisonaiagents to version 1.6.78 or later. Until then, ensure workflow files and their directories are not writable by untrusted users.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI version
    Run: pip show praisonaiagents or pip show praisonai | grep Version
    Affected if Version is before 1.6.78 (e.g., 1.6.77, 1.6.0, etc.)
  2. Locate AgentFlow._resolve_pydantic_class method
    Search for the method in the installed package: find $(python -c 'import praisonaiagents; print(praisonaiagents.__path__[0])') -name '*.py' -exec grep -l '_resolve_pydantic_class' {} \;
    Affected if The method exists and uses importlib.exec_module without sandboxing on workflow file directories
  3. Identify workflow file usage
    Check if your application loads workflow YAML/JSON files that reference pydantic models via AgentFlow (search for workflow file loading or agent execution patterns)
    Affected if Your application loads workflow files that trigger the _resolve_pydantic_class method for string output_pydantic references
  4. Assess directory write access
    Review file permissions on directories containing workflow files and any sibling tools.py files: ls -la /path/to/workflow/directory/
    Affected if Untrusted users can write to directories containing workflow files that also contain or could contain a tools.py

You are affected if praisonaiagents version is below 1.6.78 AND your environment loads workflow files that trigger the vulnerable _resolve_pydantic_class method, especially if workflow directories are writable by untrusted users who could supply a malicious tools.py.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade praisonaiagents to version 1.6.78 or later. Until then, ensure workflow files and their directories are not writable by untrusted users.

Recommended fix High confidence

praisonaiagents version 1.6.78 or later

  1. Check current installed version: pip show praisonaiagents
  2. Upgrade to version 1.6.78 or later: pip install --upgrade praisonaiagents>=1.6.78
  3. Verify the installed version: pip show praisonaiagents
  4. If using in code, ensure WorkflowManager or load_yaml is called only on trusted workflow files

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61437 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61437 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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