Reporting Vulnerabilities
Sigen defines a vulnerability as a security issue in a product that can be exploited by an attacker, resulting in a breach of the product's integrity, availability, or confidentiality. A vulnerability is not the same as a quality defect. A quality defect is triggered under certain conditions without requiring an attacker's exploitation, whereas a vulnerability must be exploited by an attacker.
If you discover a suspected vulnerability in Sigen products, you can submit it to Sigenergy regarding the relevant product via psirt@sigenergy.com. You will typically receive an email confirmation from Sigenergy PSIRT within 24 hours and will be kept informed of the progress of the issue as appropriate.
You may submit a report even if you cannot provide all the information initially. Sigenergy PSIRT will contact you and help identify any additional information needed.
Recommended Information
-
Affected product or component
Provide the product name, model, hardware version, and software or firmware version. If you cannot confirm all version information, provide what is currently known. -
Brief description and potential impact
Briefly describe the type of issue and the potential impact if an attacker successfully exploits it. -
Technical details or reproduction information
Provide reproduction steps, test conditions, or other evidence that may help us understand the issue. If complete reproduction steps are unavailable, describe the behavior you observed. -
Contact information
Provide an email address for follow-up communication. You may use your real name or an alias.
Additional Information (Optional)
Where applicable, you may also provide:
- Logs, redacted screenshots, packet captures, crash files, or proof-of-concept code (PoC);
- Required privileges, network position, user interaction, and other prerequisites for exploitation;
- The date the vulnerability was discovered;
- Whether it has been reported to another supplier, coordination body, or CVE Numbering Authority;
- Whether it has already been disclosed or a disclosure date is planned;
- Known affected or unaffected versions;
- Suggested temporary mitigations or remediation; and
- Whether you consent to public acknowledgment in a security advisory.
This information is not required to submit a vulnerability report. Sigenergy PSIRT will accept and begin an initial assessment of an incomplete report.
Sensitive Information and Attachments
Do not send passwords, private keys, recovery codes, customer data, or other sensitive information unrelated to vulnerability validation. Before submitting device serial numbers, certificate information, logs, screenshots, or network information, redact personal and customer information that is not relevant to the vulnerability analysis.
To protect undisclosed vulnerability information, we recommend encrypting sensitive vulnerability material sent to psirt@sigenergy.com with an OpenPGP-compatible tool, such as GnuPG. OpenPGP encryption is optional and is not required to submit a vulnerability report. Reports without OpenPGP encryption may still be submitted by regular email.
- PGP Key ID:
0xA962CE4630742DA0 - Full PGP fingerprint:
E3A4 914C 309F 294A 0DC6 DC57 A962 CE46 3074 2DA0 - Key identity:
Sigenergy PSIRT <psirt@sigenergy.com> - Created: 2026-11-10
- Expires: 2029-11-10
After downloading and importing the public key, confirm that its full fingerprint exactly matches the fingerprint shown on this page. You may then use the public key to encrypt the report body or attachments and send the resulting .ascor .gpgfile to psirt@sigenergy.com. If the fingerprint does not match, the key has expired, or the key cannot be downloaded, do not continue using it. Contact us by regular email for confirmation.
If an attachment exceeds the email size limit, contact us through the PSIRT email address first, and we will provide an appropriate secure transfer method.
Coordinated Disclosure
Do not disclose technical details of an unremediated vulnerability before a fix or appropriate mitigation is available. Sigenergy PSIRT will coordinate validation, remediation, and an appropriate disclosure date with the reporter.
When submitting a report, you may indicate whether you consent to the publication of your name, alias, or other acknowledgment in a security advisory. Sigenergy will not disclose your identity in a public acknowledgment without your consent.