United States Patent and Trademark Office
Vulnerability disclosure program on security.txt uspto.gov
- 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]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- 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.
- Pays cash
-
No
By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against the U.S. Government related to your submission.
- Response
-
Within 3 days
Within 3 business days, we will acknowledge that your report has been received.
- Safe harbor
-
Full
If you as a security researcher, make a good faith effort to comply with this policy during the security research, we will consider your research to be authorized, will work with you to understand and resolve the issue, and USPTO will not recommend or pursue legal action related to your research.
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, 2 excluded.
Domains 1
- uspto.gov
Wildcard domains 1
- *.uspto.gov
Out of scope (2)
- Any service not expressly listed above, such as any connected services
- vulnerabilities found in systems from our vendors
Rules
What the policy asks of you, and the bug types it won't reward, quoted from United States Patent and Trademark Office's policy. "We" in these lines means the program, not this site.
While testing
-
Notify us as soon as possible after you discover a real or potential security issue or encounter any sensitive data.
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Provide us 90 calendar days to resolve the issue before you disclose it publicly.
-
If you decide to publicly disclose a vulnerability, after the 90 calendar days, provide us 7 business day notice prior to public disclosure
-
Do not submit a high volume of low-quality reports (reports with insufficient information to take action).
Not accepted
-
Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
-
Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing
-
Remote Code Execution (RCE), in which ANY code is run remotely on a target machine.
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.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.