Skip to content

docs: update security reporting #351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
crandmck wants to merge 6 commits into
base: main
Choose a base branch
from
+5 −14
Open

docs: update security reporting #351

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
498b5a1
docs: update security reporting
crandmck Oct 26, 2026
1221afb
docs: Clarify specification vulnerability reporting
crandmck Oct 26, 2026
7b9b132
Sentence case heading
crandmck Oct 26, 2026
dbad323
Remove SLAs
crandmck Oct 29, 2026
9c05ef9
Add xref link
crandmck Oct 29, 2026
aeb2abf
Merge branch 'main' into docs/update-security-reporting
crandmck Oct 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 5 additions & 14 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,22 +1,13 @@
# Security

This C2PA open-source library is maintained in partnership with Adobe. At this time, Adobe is taking point on accepting security reports through its HackerOne portal and public bug bounty program.
This C2PA open-source library is maintained in partnership with Adobe. Adobe accepts security reports through its public [Intigriti program](https://app.intigriti.com/programs/adobe/adobepublic/detail). C2PA is listed in the program for vulnerability disclosure, but is not currently eligible for bounty rewards. Adobe continues to accept reports for assets that are not bounty-eligible, including critical findings it considers important.

## Reporting a vulnerability

Please do not create a public GitHub issue for any suspected security vulnerabilities. Instead, please file an issue through [Adobe's HackerOne page](https://hackerone.com/adobe?type=team). If for some reason this is not possible, reach out to cai-security@adobe.com.
Please do not create a public GitHub issue for any suspected security vulnerabilities. Details on how to report security vulnerabilities are available on [Adobe's bug bounty program page](https://www.adobe.com/trust/security/bug-bounty.html).

For more information on reporting security vulnerabilities in the SDK, see [SECURITY.md in c2pa-rs](https://github.com/contentauth/c2pa-rs/blob/main/SECURITY.md).

## Vulnerability SLAs
## C2PA vulnerabilities

Once we receive an actionable vulnerability (meaning there is an available patch, or a code fix is required), we will acknowledge the vulnerability within 24 hours. Our target SLAs for resolution are:

1. 72 hours for vulnerabilities with a CVSS score of 9.0-10.0
2. 2 weeks for vulnerabilities with a CVSS score of 7.0-8.9

Any vulnerability with a score below 6.9 will be resolved when possible.


## C2PA Vulnerabilities

This library is not meant to address any potential vulnerabilities within the C2PA specification itself. It is only an implementation of the spec as written. Any suspected vulnerabilities within the spec can be reported [here](https://github.com/c2pa-org/specifications/issues).
This library is not meant to address any potential vulnerabilities within the C2PA specification itself. It is only an implementation of the spec as written. Report suspected vulnerabilities within the spec in the [C2PA specification repository](https://github.com/c2pa-org/specifications/issues).
Loading