Oracle values the independent security research community and believes that responsible disclosure of security vulnerabilities helps us ensure the security and privacy of all our users.
Please do NOT raise a GitHub Issue to report a security vulnerability. If you believe you have found a security vulnerability, please submit a report to mailto:[email protected] preferably with a proof of concept. Please review some additional information on how to report security vulnerabilities to Oracle. We encourage people who contact Oracle Security to use email encryption using our encryption key.
We ask that you do not use other channels or contact the project maintainers directly.
Non-vulnerability related security issues including ideas for new or improved security features are welcome on GitHub Issues.
Security updates will be released on a regular cadence. Many of our projects will typically release security fixes in conjunction with the Oracle Critical Patch Update program. Security updates are released on the Tuesday closest to the 17th day of January, April, July and October. A prerelease announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our security alerts page.
We will provide security related information such as a threat model, considerations for secure use, or any known security issues in our documentation. Please note that labs and sample code are intended to demonstrate a concept and may not be sufficiently hardened for production use.