No technology is perfect, and curl believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you believe you've found a security issue in our products, we encourage you to notify us. We welcome working with you to resolve the issue promptly.

Disclosure Policy

• Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
• Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
• Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service.

No monetary rewards

The curl project explicitly will not pay any monetary rewards for security reports submitted through this program - even if the report ends up being a confirmed vulnerability. Everyone participating in this program should do so with the knowledge that proper credits is the only "payment" we offer.

Exclusions

While researching, we'd like to ask you to refrain from:

• Denial of service
• Spamming
• Social engineering (including phishing) of curl developers

AI

If you have used AI in the creation of the vulnerability report, you must disclose this fact in the report and you should do so clearly. We will of course doubt all "facts" and claims in reports where an AI has been involved. You should check and double-check all facts and claims any AI told you before you pass on such reports to us. You are normally much better off avoiding AI.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

Valid issues

Security problems present in the latest released curl/libcurl version that haven't already been reported/fixed and haven't otherwise been made public, in full or in part, may be subject for a bounty. Responsible disclosure must be followed for a vulnerability to be subject for a bounty.

Reports are made public

All security reports that are submitted to the curl project are subject for disclosure once they have been dealt with and they are deemed "insensitive". We are an Open Source project for which transparency is important, which then includes showing the world all our security reports as well.

Exclusions from the vulnerability reporting program

Experiments

Vulnerabilities in features which are off by default and documented as experimental, are not considered valid. We treat them as plain bugs.

Issues with our infrastructure

Any infrastructure issues that you may find are out of the policy unless they affect source packaging/distribution. This includes but is not limited to DNS config for our domains, our email setup details and website configurations or hosting details. Not in scope!

The wiki is world editable

It is on purpose. It is a wiki. If you change or add non-curl related contents to prove a point, we consider that abuse.

Thank you for helping keep curl and our users safe!