PraisonAI recipe registry publish path traversal allows out-of-root file write

An attacker exploiting this vulnerability could leverage strategically crafted manifest files within recipe bundles to write arbitrary files to the PraisonAI Recipe Registry server's filesystem. This could lead to a range of impacts, including overwriting critical system files, injecting malicious code, or gaining persistent access to the system. The ability to write files outside the designated registry root significantly expands the potential attack surface and blast radius. While the initial request is rejected with an HTTP 400 error, the damage is already done as the file creation occurs prior to the rejection.

Organizations utilizing PraisonAI Recipe Registry in production environments, particularly those with automated deployment pipelines or allowing external recipe bundle uploads, are at risk. Shared hosting environments where multiple users can upload recipe bundles are also particularly vulnerable.

• nodejs / server:

  grep -r '../' /var/log/nginx/access.log

• nodejs / server:

  journalctl -u praisonai-registry -g 'manifest.json'

• generic web:

  curl -I http://your-praisonai-registry/api/v1/recipes/upload | grep 'Server:'

1. 2026-04-07Disclosure

   disclosure

1. Reserviert2026-04-06
2. Veröffentlicht2026-04-07
3. Geändert2026-04-09
4. EPSS aktualisiert2026-04-15

The primary mitigation for CVE-2026-39308 is to upgrade PraisonAI Recipe Registry to version 1.5.113 or later, which includes the necessary fix. If upgrading immediately is not feasible, consider implementing stricter input validation on the recipe bundle manifest files to prevent the inclusion of traversal sequences (e.g., ../). Web application firewalls (WAFs) configured to detect and block requests containing such sequences can also provide a temporary layer of protection. Monitor registry server logs for suspicious file creation activity, particularly in unexpected directories.