Skip to content

Create SECURITY.md #3005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
janiversen merged 2 commits into from
Aug 25, 2026
+18 −0
Merged

Create SECURITY.md #3005

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
20fd4e6
Create SECURITY.md
janiversen Aug 25, 2026
52d09aa
Update SECURITY.md
janiversen Aug 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Security Policy

## Supported Versions

Only the latest version are supported.

## Reporting a Vulnerability

Please be aware that ModbusTcpServer, ModbusUdpServer, ModbusSimulatorServer as well as AsyncModbusTcpClient,
ModbusTcpClient, AsyncModbusUdpClient, ModbusUdpClient are not safe to be used on non-private networks. This is pr
modbus standard. Security reports telling they are not safe, are not accepted because it is a non-valid usage.

For non-private networks please use ModbusTlsServer, AsyncModbusTlsClient or ;odbusTlsClient. Using the correct
certificate is an app issue and considered out of scope for pymodbus. The App can choose to e.g. use a
self-signed certificates which are considered insecure.

Most vulnerabilities like e.g. a buffer overrun should just be reported as a normal issue, since it really is a bug,
allowing all users to be aware of the problem.