The OWTF leadership team takes security issues seriously. We value coordinated disclosure and will work with reporters to understand, remediate, and disclose vulnerabilities responsibly. Response and remediation times depend on maintainer availability, severity, and the complexity of the fix; we will agree on a disclosure timeline after triage.
Do not open a public issue or discussion containing vulnerability details.
Email the current OWTF project leaders at
viyat.bhalodia@owasp.org and
abraham.aranguren@owasp.org with the subject [OWTF SECURITY]. Include:
- Your name and affiliation (if any)
- A clear description of the vulnerability
- Steps to reproduce the issue, including sample payloads or proof-of-concept code if applicable
- Any related CVE, advisory, or public references
- Your preferred disclosure timeline
If you need an encrypted channel, send an initial message without sensitive technical details and ask the maintainers to arrange one.
The security policy applies to:
- The OWTF core framework and official plugins hosted in this repository
- Infrastructure maintained by the OWTF project that directly supports users (for example, official Docker images)
Third-party tools invoked by OWTF plugins fall outside of our direct control. We will coordinate with upstream projects when feasible but cannot guarantee fixes for external dependencies.
| Version | Supported |
|---|---|
develop |
Yes |
2.7.x |
Yes |
2.6.0 and older tagged releases |
No |
Security fixes are developed on develop and released as 2.7.x patch updates when required. Older tagged releases do not
receive security fixes.
With the reporter's consent, we credit responsible disclosures in the corresponding published GitHub security advisory.