dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-60087

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges 5 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 before 1.6.78 caches tool approval decisions by tool name only, allowing attackers to reuse initial approvals for subsequent calls with arbitrary arguments. Attackers can exploit this by obtaining approval for a benign operation and then executing dangerous file write operations with unreviewed parameters in the same session.

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 · moderate confidence

PraizonAI before 1.6.78 has a flawed approval caching mechanism that stores tool approval decisions using only the tool name as the cache key, ignoring the actual arguments passed to the tool. This allows an attacker who obtains approval for a benign operation to later invoke the same tool with malicious parameters (such as dangerous file write operations) without re-verification, as the system incorrectly trusts the cached approval from the initial benign call.

MitigationImplement approval caching that includes both tool name AND the full argument set/context as the cache key, or require re-approval for operations involving file system modifications regardless of prior approvals for the same tool name.

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
None
Integrity
High
Availability
Low

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

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. Identify PraizonAI installation and version
    Locate the PraizonAI installation directory and check the version file or binary version. Common paths include /opt/praizonai, /usr/local/praizonai, or the application root directory. Look for a version manifest, package.json, or version.txt file.
    Affected if The installed version is before 1.6.78 (e.g., 1.6.77, 1.6.5, etc.)
  2. Verify approval caching is enabled
    Examine the PraizonAI configuration files for approval caching settings. Look in config/approvals.conf, config/cache.json, or similar configuration directories for settings like 'cache_approvals', 'approval_cache_enabled', or 'use_cached_approvals'. Check for boolean flags set to true.
    Affected if Approval caching is enabled in the configuration (any setting that permits reusing prior approval decisions without re-verification)
  3. Identify tools with file system access
    Review the tool definitions or plugin directory to identify tools capable of file write, file modify, or file download operations. Look for tools named file_write, write_file, save_file, download, or similar. Cross-reference with the approved tools list if one exists.
    Affected if Tools with file write or modification capabilities are registered and available for use
  4. Examine approval cache storage
    Locate the approval cache storage mechanism. Check for cache files in data/cache/, data/approvals/, or runtime/cache/ directories. Look for JSON, SQLite, or other database files that store approval decisions. Inspect the cache key structure by examining a cached entry.
    Affected if Cache entries use only the tool name as the key (e.g., 'file_write': true) without including arguments or context in the key
  5. Review approval logs for cached decisions
    Check application logs for entries containing 'cache', 'cached approval', or 're-using approval'. Look for log patterns showing a tool was approved without re-evaluation on subsequent calls with different arguments.
    Affected if Logs show approvals being reused for repeated tool calls without argument validation on each invocation

If PraizonAI version is below 1.6.78 AND approval caching is enabled for tools with file operations, the environment is vulnerable to argument-agnostic approval reuse attacks.

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

Implement approval caching that includes both tool name AND the full argument set/context as the cache key, or require re-approval for operations involving file system modifications regardless of prior approvals for the same tool name.

Recommended fix High confidence

1.6.78 or later

  1. 1. Identify the currently installed PraisonAI version using pip show praisonai or pip list
  2. 2. If the installed version is before 1.6.78, upgrade to version 1.6.78 or later using: pip install --upgrade praisonai
  3. 3. Verify the upgrade was successful by checking the installed version: pip show praisonai
  4. 4. Confirm the version meets the minimum secure version requirement of 1.6.78

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-60087 — 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-60087 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