ENPLDEPT
Flash
All docs
Security

Found a hole? Tell us privately.

We fix security problems first and credit the people who find them. Please report privately, not in a public issue or on Discord.

How to report

  • Preferred: open a private report on GitHub in the repository the problem is in, under Security → Report a vulnerability (for example sensmos-firmware). Only the maintainers can see it.
  • Not sure which repository? Use sensmos-firmware for anything about nodes and the servers.
  • Machine-readable contact: /.well-known/security.txt.

Please include what is affected (component and version), how to reproduce it, and what an attacker could do. English or Polish is fine.

What happens next

StepWhen
We confirm we received the reportwithin 3 working days
First assessment and severitywithin 7 days
Fix for a critical problem on the tester channelas fast as possible, usually within 14 days
Fix rolled out to the fleet in waves, then public advisoryafter the fix is confirmed

If a vulnerability is being actively exploited, we notify the national CSIRT and ENISA within 24 hours, as the EU Cyber Resilience Act requires, and tell users what to do.

What is in scope

Firmware (nodes, communicator), the Android app and web panel, Sensmos Hub, the Home Assistant and ESPHome integrations, Store clients, the GALU contract and the sensmos.com servers. Please do not run denial-of-service tests, do not access other people's data or nodes beyond what is needed to show the problem, and give us a reasonable time to fix it before publishing.

How fixes reach you

Nodes update over the air. New firmware goes to testers first, must pass a round trip of over-the-air updates, and then reaches the fleet in waves. The app updates itself from GitHub releases; the Hub and Home Assistant integration through their usual update channels.

Last updated: 2026-11-16