Philips
By Royal Philips Vulnerability disclosure program on Self-hosted philips.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- 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]
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 2 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.
- Response
-
Within 2 days
Philips will acknowledge receiving your report within two business days.
- Safe harbor
-
Partial
Philips supports coordinated vulnerability disclosure, and encourages vulnerability testing by security researchers and by customers, with responsible reporting to Philips.
- Hall of fame
-
Yes
Visit our Hall of Honors ›
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- philips.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Philips's policy. "We" in these lines means the program, not this site.
While testing
-
Do not perform any vulnerability or similar testing on products that are actively in use.
-
For Healthcare products, never perform any vulnerability or similar testing on products that are actively in use in patient care, patient diagnosis or patient monitoring.
-
For web based products, please use demo/test environments to perform vulnerability testing.
-
Do not take advantage of the vulnerability or problem you have discovered; for example, by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying any data.
-
After vulnerability testing, each device should be retested to ensure no damage has been inflicted and the device is suitable for use.
-
Please inform us of your disclosure plans, if any, prior to public disclosure.
-
Using social engineering to gain access to the system.
-
Building his or her own backdoor in an information system with the intention of then using it to demonstrate the vulnerability, as doing so can cause additional damage and create unnecessary security risks.
-
Utilizing a vulnerability further than necessary to establish its existence.
-
Copying, modifying or deleting data on the system.
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 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.