Skip to main content

Responsible Vulnerability Disclosure Policy

Promptfoo values the security and privacy of our users, customers, and the broader community. We welcome responsible disclosure of vulnerabilities.

Scope​

This policy covers vulnerabilities in:

  • Promptfoo Open Source Software (CLI, libraries)
  • Promptfoo Cloud Services
  • Promptfoo On-premises Components

For technical details on our security model, trust boundaries, and hardening recommendations, see SECURITY.md on GitHub.

Open Source (CLI)​

The OSS CLI runs in your environment with your user permissions. It is permissive by default and executes user-configured code (custom assertions, custom or script-based providers, transforms, hooks, plugins, and templates in fields that execute code) without sandboxing.

Treat Promptfoo configuration files and everything they reference or evaluate against as trusted code and data. This includes referenced scripts, prompt packs, test fixtures or datasets, configured providers, models, remote content, and model-output feedback loops. Run untrusted configs, scripts, prompt packs, fixtures, datasets, providers, models, remote content, model-output feedback loops, or pull requests only when the run is isolated and secrets are scoped for that run.

Promptfoo OSS is a local eval runner, not a sandbox for adversarial eval content. Adversarial data flowing through the configured template engine and eval pipeline (e.g., model output in grading prompts, variable values rendered through Nunjucks) is normal operation. However, if a code path outside the configured template engine or user-configured code-executing fields promotes runtime data to code, that is a vulnerability.

In scope for OSS: runtime data promoted to code by a code path outside the configured template engine and user-configured code-executing fields; bypasses of supported isolation boundaries or hardening controls; data or secret leakage to destinations not configured to receive that data or secret.

Out of scope for OSS: adversarial eval content flowing through the configured template engine and eval pipeline; code execution from explicitly configured custom code or templates in fields that execute code; direct local API or browser access to the OSS local server (promptfoo view); and issues requiring users to run untrusted configs, scripts, prompt packs, fixtures, datasets, providers, models, remote content, or model-output feedback loops with local privileges.

Cloud Services​

Promptfoo Cloud operates with higher isolation expectations. The following are in scope and treated as critical:

  • Cross-tenant data access or isolation failures
  • Sandbox escapes or privilege escalation
  • Access to Promptfoo internal systems or credentials
  • Unauthorized data exposure between accounts

Reporting Vulnerabilities​

Do not open a public GitHub issue for security reports.

Report privately via:

Include:

  • Description and steps to reproduce
  • Affected version or environment
  • Security impact assessment
  • Whether remotely exploitable or requires local access
  • Your contact info for follow-up (optional)

To speed triage, also include:

  • Whether you reproduced on the latest supported release (or main)
  • The affected file/function/code path, if known
  • A real browser-based PoC for browser-origin claims; spoofed Origin or Sec-Fetch-Site headers from curl or other non-browser clients are not sufficient
  • Why the issue exceeds the OSS trust model described in SECURITY.md

Response Time​

We will acknowledge your report within 1 business day and keep you informed throughout remediation.

Responsible Disclosure Guidelines​

When researching or disclosing vulnerabilities:

  • Do not exploit beyond minimal testing needed to demonstrate the issue
  • Do not disclose publicly or to third parties before resolution
  • Allow reasonable time for investigation and remediation

Coordinated Disclosure​

We ask that you keep details private until:

  • A fix is released, or
  • We agree on a disclosure date

We will work with you to establish a reasonable timeline.

Our Commitment​

Upon receiving your disclosure, we commit to:

  • Acknowledge within 1 business day
  • Keep you informed throughout remediation
  • Resolve vulnerabilities in a timely manner
  • Credit you (with consent) in security acknowledgments or changelogs

Safe Harbor​

If you act in good faith and follow this policy, we will not pursue legal action against you for security research that:

  • Avoids privacy violations and data destruction
  • Avoids service disruption
  • Is limited to what is necessary to demonstrate the vulnerability
  • Does not involve accessing data that is not your own

Out-of-Scope​

The following are out-of-scope:

  • Code execution from explicitly configured custom code or templates in fields that execute code in OSS (expected behavior)
  • Direct local API access or browser access to the OSS local server (promptfoo view)
  • Adversarial eval content flowing through the configured template engine and eval pipeline (e.g., model output in grading prompts or reports)
  • Issues requiring users to run untrusted configs, scripts, prompt packs, fixtures, datasets, providers, models, remote content, or model-output feedback loops with local privileges
  • Reports based only on spoofed Origin or Sec-Fetch-Site headers from non-browser clients
  • Social engineering, phishing, or physical attacks
  • Volumetric denial of service
  • Vulnerabilities in unsupported versions
  • Non-security bugs or feature requests

If unsure whether something is in scope, report it anyway.

Thank you for helping protect Promptfoo users.