Vulnerability Disclosure Policy

Page revised 17 November 2026 (version 2).

In force since: 23 May 2025

Last updated: 17 November 2026

1. Introduction

Shelly Europe Ltd. (the „Company“, „We“ or „Shelly“) is committed to ensuring an appropriate level of cybersecurity, based on the risks, across its ecosystem of smart products for home automation with brand names „Shelly“, „Shelly Loqed“ and „Cury by Shelly“ and digital services for remote control.

As a manufacturer of smart devices and a provider of digital services, We understand the importance of cybersecurity and coordinated vulnerability disclosure. This policy establishes the principles and the procedure for the coordinated reporting of potential vulnerabilities, ensuring cyber protection and the integrity of our digital ecosystem. The Company, through its IT Team, encourages the disclosure of any identified vulnerabilities through our designated reporting channels.

This policy is adopted in accordance with Regulation (EU) 2024/2847 (Cyber Resilience Act), applies to all SHELLY Devices and SHELLY Services, and is publicly available on the Company’s website.

2. Definitions and classification

Vulnerability. For the purposes of this policy, „vulnerability“ means any weakness, susceptibility or flaw of a product with digital elements or digital service, such as SHELLY Devices and SHELLY Services, including their software, components and remote data processing solutions, that can be exploited by a cyber threat, including via any tool or code for unauthorized access, manipulation or disruption of their functionality.

Severity. Vulnerabilities are assessed on a risk basis, taking into account their exploitability, the likelihood of exploitation and the potential impact on the confidentiality, integrity and availability of the product, its functions and the data it processes. A vulnerability is classified as „critical“ in particular where:

Functional defects. A reported issue is treated as a vulnerability only if it has a security consequence, such as unauthorized access, information disclosure, persistent disruption of the device or bypass of security controls. Issues without such a consequence, for example temporary crashes caused by invalid input from which the device recovers automatically, or actions by authorized users within their existing rights, may be classified as functional defects and handled through the normal development process. A home or local network is not considered a trusted environment for this assessment. Reports may be reassessed if new evidence demonstrates a security impact.

3. Scope

3.1. Products and services in scope

This policy applies to all products with digital elements, digital services, platforms and applications that are designed, developed, manufactured, placed on the market, provided, or fully maintained and supported by the Company, including their software, firmware and integrated third-party and open-source components, in particular:

Any other product, platform or application falling within this Section shall be treated as a SHELLY Device or a SHELLY Service, as applicable.

3.2. Out of scope

Products and services that are not developed, manufactured, provided or supported by the Company are excluded from the scope of this policy. This includes third-party products, services and IoT ecosystems, as well as the applications and systems of third-party integrators using SHELLY API. Vulnerabilities in them should be reported directly to the respective provider in accordance with its disclosure policy (if any). However, vulnerabilities in third-party or open-source components integrated into SHELLY Devices or SHELLY Services fall within the scope of this policy.

The following issues are not handled under this policy and should be addressed to our Support Team at https://support.shelly.cloud:

The Company reserves the right not to consider such reports under this policy, unless they reveal a potential security risk to SHELLY Devices or SHELLY Services.

Vulnerabilities related to the Company’s website and online store at www.shelly.com, including its subdomains used for the website and online store, are not covered by this policy and should be reported to e-commerce@shelly.com in accordance with the separate procedure applicable to them. Vulnerabilities related to the Company’s security platform at security.shelly.com should be reported to security@shelly.com.

If you are unsure whether a product or service is included in the scope of this policy, contact us at security@shelly.com before you proceed with your research.

4. How to report a vulnerability

4.1. Reporting channels

If you believe that you have discovered a vulnerability in a SHELLY Device, SHELLY X Module or SHELLY Service, or would like to report a security incident, please complete the reporting form available at https://security.shelly.com/report/. Security vulnerabilities or incidents may also be reported directly by email to security@shelly.com. Reports should be submitted in English or German.

The form allows the reporter to submit the report anonymously. In such case, the Company reserves the right not to provide updates on the status of the report or disclose any information regarding the progress or outcome of the investigation and remediation of the anonymously reported vulnerability.

4.2. What to include

To be processed effectively, each report sent by email to security@shelly.com shall contain the following information:

To facilitate the processing of reports, we recommend using the following format in the email subject: „Vulnerability report – [affected SHELLY Device or SHELLY Service] – [affected software version, if applicable] – [brief description of the issue]“.

4.3. Encryption and files

Reporters who wish to submit an encrypted report may use the Company’s PGP public key to encrypt communications sent to security@shelly.com. The key fingerprint is: E51B 04C8 4025 B4BB 21AB B5D1 DCD2 7410 0534 24C6. Encrypted reports are subject to the same requirements as other reports under this Section.

To ensure the security of communication, attachments are not accepted with the initial vulnerability report, except files encrypted with the Company’s PGP public key. Where additional materials (for example proof of concept (PoC), logs, screenshots or video) are necessary, they should be sent by email, encrypted with the Company’s PGP public key, unless another secure channel is agreed with the Company.

4.4. Quality of reports

Reports prepared in whole or in part with the use of artificial intelligence tools are accepted, provided that the reporter discloses such use, has personally verified the vulnerability, and the report contains accurate and reproducible steps. However, the Company reserves the right not to consider reports that appear to be automatically generated and have not been verified by the reporter. Each report should concern a single finding.

Where a report does not contain sufficient information to identify the vulnerability, the Company may request additional information from the reporter. Reports that remain insufficient may not be processed, unless they reveal a potential security risk to SHELLY Devices or SHELLY Services. Speculative findings, unverified output of automated scanners and repeated or bulk submissions of the same issue may be closed as unverified.

Reporting vulnerabilities in no way creates contractual relationships or representations between the Company and the reporting person, nor does it constitute a commitment to financial compensation or any payment of remuneration or rewards.

5. Research guidelines

5.1. Permitted research

Research on SHELLY Devices owned by the researcher and on the researcher’s own SHELLY Service accounts, including analysis of firmware, software, communications, and hardware analysis (e.g. debug ports, UART), is permitted, provided that it is conducted in good faith, does not affect other users or the Company’s production systems, and the findings are reported to the Company and disclosed in accordance with this policy. The publication or distribution of extracted firmware, source code, cryptographic keys or other proprietary information of the Company is prohibited.

5.2. Prohibited methods and activities

Data protection and the stability of our ecosystem are paramount. Therefore, the following methods and activities are strictly prohibited under this policy:

If you have any concerns about the permitted research methods, please contact the Company before taking any action.

Any person, whether a user, independent researcher or other party, who violates the terms of this policy and/or uses any of the prohibited methods and activities may be subject to legal or technical action by the Company.

6. Safe harbour

Research conducted in good faith and in compliance with this policy will be considered authorised, and the Company will not take legal action against the researcher in connection with it.

7. What to expect

The Company is committed to providing timely feedback to reporters on the status of their report and the actions taken, provided that a contact email address has been provided:

Step

Commitment

Acknowledgement

Within 3 (three) business days of receipt, the Company confirms that the report is under review.

Response

Within 30 days of receipt, the Company informs the reporter whether the vulnerability is confirmed. If it is confirmed, the Company also provides the planned remediation and its estimated timeframe. If it is not, the Company explains why: the issue is not a vulnerability, falls outside the scope of this policy, or is adequately mitigated by other measures.

Remediation

The Company aims to remediate confirmed vulnerabilities as quickly as possible, and within 90 days of the report. Security updates are provided free of charge and disseminated without delay, together with advice to users on any actions to be taken.

Publication

Once a security update is available, the Company publishes a security advisory in accordance with Section 9.

Critical vulnerabilities. Vulnerabilities classified as „critical“ are handled with priority and within significantly shorter timeframes.

Products outside the support period. For products whose support period has expired, the Company will assess the report and, where possible, publish mitigation advice, but may not release a security update.

Regulatory notifications. Actively exploited vulnerabilities and severe incidents affecting SHELLY Devices or SHELLY Services are notified through the ENISA single reporting platform, and affected users are informed, in accordance with the Cyber Resilience Act, irrespective of the timelines set out above.

Personal data breaches. If a reported vulnerability leads to an incident or a personal data breach, the Company will involve its Data Protection Officer and will take appropriate action in accordance with the GDPR and applicable law.

Extension of timelines. The Company may extend the timelines set out above in the event of complex vulnerabilities, system interdependencies, unforeseen technical challenges or other unexpected circumstances, without amending this policy. In such cases, the reporter shall be informed of the extension and its reasons, where contact details have been provided. Any extension shall be without prejudice to the time limits under the Cyber Resilience Act.

8. Coordinated disclosure

Premature public disclosure may increase the risk to users and compromise the security of SHELLY Devices, SHELLY X Modules and SHELLY Services.

All reporters shall follow the principles of coordinated vulnerability disclosure and shall not publicly release information about identified vulnerabilities, proof-of-concept (PoC) exploits, or any related technical or non-technical information before the earlier of the remediation and disclosure of the vulnerability by the Company, or the expiry of 90 days from the date of the report, unless otherwise agreed with the Company.

The Company treats all vulnerability reports as confidential information until the vulnerability is remediated and the necessary guidance and updates are publicly provided, except where disclosure is required by law, including under the Cyber Resilience Act, or is necessary for the remediation of the vulnerability. The Company does not publicly disclose or discuss vulnerabilities until their investigation is complete and any necessary updates are publicly available, unless earlier information to users is necessary to mitigate an actively exploited vulnerability.

In the event of disclosure in breach of this policy, the Company reserves the right to take appropriate measures in accordance with applicable law.

9. Security advisories

In the interest of transparency and security, the Company publishes information about confirmed vulnerabilities and the corresponding remediation in security advisories available at https://security.shelly.com/advisories/, within the timelines set out in Section 7. Users can subscribe to new security advisories via the subscription options available on the security platform.

Each security advisory includes:

Where appropriate, the Company may request or assign CVE identifiers and publish the corresponding vulnerability records in accordance with the rules of the CVE Program.

Acknowledgement of reporters. The Company does not publicly acknowledge reporters, unless the reporter requests it and gives their consent.

All information provided in the security advisories and in linked documents is provided „as is“ as of the time of publication. The Company may update advisories as new information becomes available, and the date of the latest update shall be indicated in the advisory.

In duly justified cases, where the security risks of publication outweigh its benefits, the Company may delay or limit the disclosure of a vulnerability and any related information until users have had the opportunity to apply the security update.

10. Limitation of liability and intellectual property

To the extent permitted by applicable law, the Company shall not be liable for:

By submitting a vulnerability report, the reporter grants the Company a free of charge, non-exclusive, perpetual, irrevocable and worldwide licence to use, reproduce, modify and publish the information provided, for the purposes of analysing and remediating the vulnerability, improving the security of SHELLY Devices, SHELLY X Modules and SHELLY Services, and complying with the Company’s legal obligations. The reporter confirms that they are entitled to grant this licence. No compensation or remuneration is due to the reporter, except as provided in Section 12.

Submitting a vulnerability report shall not entitle the reporter to any intellectual property rights in the solutions developed to remedy the vulnerability or in subsequent updates to the Company’s products and services.

11. Privacy notice

For the purposes of this policy, Shelly Europe Ltd., as controller, collects and processes personal data of natural persons („reporters“) who report potential vulnerabilities in SHELLY Devices, SHELLY X Modules and/or SHELLY Services, on the legal bases set out below. The processing of personal data based on the legitimate interests of the Company is balanced against the fundamental rights of the reporters. This legitimate interest is grounded in the Company’s responsibility to maintain the security and integrity of its smart products and digital services, to prevent and mitigate cyber threats, and to ensure the continuous and reliable operation of its systems.

Data processed. The data processed in connection with vulnerability reports may include:

Providing personal data is voluntary. However, without a valid contact email address the Company cannot provide feedback on the report.

Reports submitted through the reporting form are encrypted in the reporter’s browser before they are sent. The encrypted report is held on the server of the security platform only until it is forwarded to security@shelly.com, which normally takes a few minutes, and is then deleted from the server. The name and email address, if provided, are contained only in the encrypted report. To prevent abuse, IP addresses are processed temporarily in memory and are recorded in the server logs only where a request is blocked or fails. The security platform does not use analytics, tracking or third-party services that could identify visitors.

Purposes and legal bases. The Company uses the data provided by the reporter to:

The Company has implemented technical, organisational and contractual measures to protect reporters’ personal data against unauthorized access, use or alteration.

Recipients. The data may be accessed by authorised employees of the Company and may be shared with:

Where personal data is transferred outside the European Economic Area, appropriate safeguards are applied, such as standard contractual clauses.

Retention. Personal data is retained for no longer than 1 (one) year after the completion of the vulnerability handling process. After that period, vulnerability records may be kept in anonymised form. Data needed for legal claims may be retained until the applicable limitation period expires. Where the reporter has consented to be acknowledged, their name and the record of their consent are kept for as long as the acknowledgement is published. Server logs are retained for 12 months. The full IP address is kept for 14 days and then shortened.

Rights. Reporters have the right to access, rectification, erasure, restriction of processing and objection to processing based on legitimate interest. Where processing is based on consent, they also have the right to data portability and the right to withdraw consent. Requests may be sent to dpo@shelly.com. Where a reporter withdraws their consent to be acknowledged, the Company removes their name from the security advisory and requests the update of the related CVE record. Copies already published by third parties may not be fully removable. Reporters may also lodge a complaint with the competent supervisory authority, in Bulgaria the Commission for Personal Data Protection.

12. Final provisions

Rewards. The Company does not have a bug bounty programme, but reserves the right, at its discretion, to establish, amend or terminate such programmes. Participation in such programmes shall be governed by specific terms and conditions, which shall be published on the Company’s official website https://www.shelly.com/. The Company does not provide monetary rewards (such as cash), even upon confirmation of vulnerabilities, but reserves the right, at its sole discretion, to reward reporters with discount vouchers or other non-cash rewards.

Amendments. The Company reserves the right to modify or amend this policy at any time, without prior written notice, when necessary to protect its interests, the security of users, or to comply with regulatory requirements. The date of the latest update is indicated at the beginning of this policy.

Governing law. This policy shall be governed by the laws of the Republic of Bulgaria, without prejudice to the mandatory provisions of applicable law.

Languages. The official languages for communication under this policy are English and German. In the event of any discrepancy between the English version of this policy and any translation thereof, the English version shall prevail.

Contact. Shelly Europe Ltd., security@shelly.com, tel. +359 2 988 6954 (business days, 9:00–18:00 EET/EEST). Vulnerability reports may be submitted at any time through the channels set out in Section 4.

All rights reserved. Shelly Europe Ltd.