- Top reward
- $10,000
- Top severity paid
- Not published
- Assets in scope
- 3
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays up to $10,000
- top reward, from $10.
- Report by email
- [email protected]
- Replies within 1 day
- 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.
The policy page has no reward table. Here is what it says, in its own words.
- Pays cash
-
Yes
If the relevant product is within the scope of the ZTE bug-bounty program, the corresponding reward will be provided.
- Response
-
Within 1 days
an email of confirmation within 1 working day from submission;
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
3 assets you may test, 1 excluded.
Domains 2
- www.ztedevices.com/en/products/mobile-internet.html
- zte.com.cn
Products and areas 1
- Products within the scope of ZTE service (excluding End of Service & Support products )
Out of scope (1)
- End of Service & Support products
Rules
What the policy asks of you, and the bug types it won't reward, quoted from ZTE's policy. "We" in these lines means the program, not this site.
While testing
-
As security vulnerabilities are sensitive information, we strongly suggest you use our PGP public key (key ID: FF095577) to encrypt the information you submit.
-
Use the Email subject format as: [Product Name-Vulnerability Overview]
-
Ensure that your submission does not involve intellectual property issues, and does not contain the contents prohibited by law or profanities.
-
Vulnerability reports generated by AI-assisted or automated mining must undergo manual verification before submission.
-
Provide a complete and compilable POC or Exploit.
-
we assume that you agree to keep the information confidential before ZTE discloses the information.
Not accepted
-
For non-security vulnerabilities, please consult Global Technical Support 。
-
Reports that are too simple or contain no proof of impact whatsoever will be directly rejected.
-
reports that are directly generated by AI, have not been manually reproduced, or lack valid verification materials
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 12 Nov 2026. Last checked 5 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.