CVE-2026-56078
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 · uneditedPraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
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 confidencePraisonAI before 1.5.115 has a path traversal vulnerability in the MultiAgentMonitor component. The application fails to sanitize agent IDs before using them in file path construction, allowing attackers to inject '../' sequences to escape the intended directory and access or modify arbitrary files on the system.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed PraisonAI versionRun 'pip show praisonai' or 'pip list | grep praisonai' to find the installed version numberAffected if Version is lower than 1.5.115
-
Identify if MultiAgentMonitor component is in useSearch your codebase or application logs for imports or usage of 'MultiAgentMonitor' class or moduleAffected if MultiAgentMonitor is imported or instantiated in your application code
-
Locate agent ID handling in MultiAgentMonitorInspect the MultiAgentMonitor source file (typically in the agents or monitoring directory) and locate where agent IDs are used in file path operations (os.path.join, open(), or similar)Affected if The code uses agent IDs directly in file path construction without sanitization
-
Test for path traversal vulnerability in agent ID inputIf you have access to the agent ID input field or API parameter, observe whether input containing '../' sequences is accepted or filtered (for example, provide an agent ID like '../../etc/passwd' and check the resulting file access path)Affected if The application accepts and processes path traversal sequences in agent IDs without rejecting them
-
Review application logs for suspicious path accessCheck application logs for any file access attempts that escape the intended agent data directory (look for '../' patterns or access to files outside the designated agent directory)Affected if Logs show file access attempts with '../' sequences or access to unexpected directories triggered by agent IDs
You are affected if you are running PraisonAI version before 1.5.115 and the MultiAgentMonitor component processes agent IDs without path traversal sanitization.
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 PraisonAI version 1.5.115 or later. As a temporary measure, implement strict input validation on agent IDs to reject any path traversal sequences before the fix is applied.
1.5.115
- 1. Identify the current installed version of PraisonAI by running `pip show praisonai` or checking your dependency files
- 2. If the current version is below 1.5.115, upgrade to version 1.5.115 or later using `pip install --upgrade praisonai`
- 3. Verify the upgrade was successful by running `pip show praisonai` and confirming the version number
- 4. Test that the MultiAgentMonitor functionality works correctly after the upgrade
- 5. If using a requirements.txt or poetry.lock file, update the version constraint to specify `praisonai>=1.5.115` and run `pip install -r requirements.txt` or `poetry update` to lock the fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56078 — 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-2026-56078 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