Last Updated: 2022-11-02
This policy covers ALL Jackson projects/repos: some repos may have their own copy of this policy document.
Current status of open branches, with new releases, can be found from Jackson Releases wiki page
The recommended mechanism for reporting possible security vulnerabilities follows so-called "Coordinated Disclosure Plan" (see definition of DCP for general idea). The first step is to file a Tidelift security contact: Tidelift will route all reports via their system to maintainers of relevant package(s), and start the process that will evaluate concern and issue possible fixes, send update notices and so on. Note that you do not need to be a Tidelift subscriber to file a security contact.
Alternatively you may also report possible vulnerabilities to info at fasterxml dot com
mailing address. Note that filing an issue to go with report is fine, but if you do that please
DO NOT include details of security problem in the issue but only in email contact.
This is important to give us time to provide a patch, if necessary, for the problem.
(for more in-depth explanation, see Apache Release Signing document)
To verify that any given Jackson artifact has been signed with a valid key, have a look at KEYS file of the main Jackson repo:
https://github.com/FasterXML/jackson/blob/master/KEYS
which lists all known valid keys in use.
There is a published security audit about 2 main Jackson components (jackson-core, jackson-databind):
which documents a thorough investigation into Jackson design, implementation, as well as some security design suggestions for developers using Jackson libraries.