Skip to content
bugbounty.fyi
Get paid to secure open source 475 paid open-source programs on Sorona, up to $1M Perk Low bugs: $100 or 1 mo Claude Max

Also on Patchstack. All 476 paid open-source programs

Try

Highest paying Newly launched Paid without KYC Full safe harbor
All results

About this site

Django Software Foundation

Vulnerability disclosure program on security.txt djangoproject.com

Accepting reports security.txt
Go to program Website
Top reward
No cash rewards
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

No cash rewards
A disclosure program: you report for credit, not money.
Report by email
[email protected]
Replies within 3 days
As the policy promises.
Publish after a fix
Coordinate the timing with the company.

Rewards

What the company's own policy page says it pays.

This program does not pay cash rewards.

Response
Within 3 days you should receive an acknowledgment from a member of the security team within 3 working days.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test.

Domains 1

  • djangoproject.com

Source code 1

  • Django

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Django Software Foundation's policy.

While testing

  • please report security issues by emailing [email protected] .
  • please send a description of the issue via email to [email protected] .
  • Your initial report should give the security team enough to make a triage decision, no more.
  • A single vulnerability, as opposed to multiple separate issues.
  • A minimal, working proof of concept (code snippet or reproduction steps).
  • The versions of Django and Python you tested against.
  • Please do not attach screenshots of code.
  • Please do not include severity scores (CVSS or otherwise), lengthy background sections, multiple headers, or a determination of whether the issue constitutes a vulnerability.
  • If you have identified multiple potential issues, please wait for a triage result on your initial report before submitting further ones.
  • Do not include multiple reports in a single submission.

Not accepted

  • Reports based on a failure to sanitize user input are not valid security vulnerabilities.
  • vulnerabilities that only occur when Django is run on a version of Python that is no longer receiving security updates (“end-of-life”) are not considered valid
  • the Django security team will not consider reports that rely on request headers or URLs exceeding 8K bytes
  • a proof of concept must not exceed 2.5 MB in the request body to be considered valid.
  • Proof of concepts which use over 100 KB of data to be processed by the DTL will be considered invalid.
  • If a vulnerability depends on directly calling these internal functions in an unsafe way, it will not be considered a valid security issue.
  • Exploits that only affect local development, for example when using runserver .
  • Exploits which fail to follow security best practices, such as failure to sanitize user input.
  • Exploits in AI generated code that do not adhere to security best practices.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 2 hours ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.