Summary
PraisonAI's Jobs API exposes run-management endpoints without requiring authentication, allowing reachable callers to interact with jobs and their results. Depending on deployment exposure and operator permissions, an unauthenticated caller may submit, read, cancel, or delete jobs.
Affected context
The issue occurs in PraisonAI deployments where the Jobs API create_app function mounts the /api/v1/runs endpoints without authentication middleware. It becomes risky when the API is reachable by untrusted or insufficiently trusted network clients and the service can perform operations using operator-level credentials.
Exploit preconditions
- Attack surface: Network-accessible PraisonAI Jobs API endpoints
- Required access: Network reachability; no valid API credential may be required
- Trigger point: Requests to endpoints for creating, viewing, canceling, or deleting jobs
- Why exploitation is possible: The API accepts job-management requests without verifying caller identity before applying operator-authorized actions
Why this happens
The underlying bug is an authentication control omission: sensitive API routes are mounted without middleware that verifies a caller's identity or presents a valid credential. This maps to CWE-306, Missing Authentication for Critical Function, because job-management operations are exposed while the service relies on its own operator privileges rather than enforcing authentication at the request boundary.
Potential impact
- An unauthorized caller may submit jobs for execution
- An attacker could read job outputs or other run results
- Active runs may be canceled or jobs may be deleted
- Compute resources could be consumed or abused
- Confidential data exposed through job results could be disclosed
- Workflows and operational processes could be disrupted
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization
consistently for every job-management route.
Common defensive patterns include:
- Require a strong API credential through Authorization or X-API-Key before routing requests
- Apply authentication middleware by default to all sensitive API endpoints
- Enforce operation-level authorization rather than relying only on service credentials
- Reduce the privileges available to the Jobs API service identity
- Keep the API on a restricted network boundary and avoid unauthenticated exposure
- Use short-lived, rotatable credentials and protect them from logs and client-side disclosure
How teams detect issues like this
Organizations can identify this class of issue through:
- Static analysis and route audits that flag sensitive handlers without authentication middleware
- Code review checks confirming every create, read, cancel, and delete operation has an authorization path
- Integration tests that verify unauthenticated requests receive an authentication failure
- API gateway or service-mesh policies requiring credentials for job-management paths
- Monitoring for job submissions, result reads, cancellations, and deletions without an authenticated principal
- Automated security review tools that map exposed routes to missing authentication controls

