Reporting a vulnerability
If you think you have found a security vulnerability in Zero Defect Pro, its installer, its update service or its licence service, e-mail it@learnexconsulting.com with the subject Security: short title. Please include:
- the version (About → Version) and the operating system;
- what an attacker can do, and the steps to reproduce it;
- any proof-of-concept files, logs or screenshots. Please do not send real FMEA data or passwords.
Please do not report it publicly, or test it against other customers' systems, until we have fixed it.
What we commit to
- Acknowledge the report within 2 business days.
- First assessment and severity (CVSS 3.1) within 5 business days.
- Fix a critical or high issue within 30 days, released as a patch version.
- Fix a medium or low issue in the next planned release.
We tell the reporter when the fix ships and, if they wish, credit them in the release notes. Customers learn about a fixed security issue in the What's new notes of that release; for a critical issue, their administrators are also e-mailed.
Supported versions
Security fixes go to the latest minor version and, for 6 months, to the minor version before it. Older versions must update to receive fixes.
In scope
- The Zero Defect Pro desktop application and its installer
- The in-app updater and the LearnEX delivery service it uses
- Licence activation, online and with offline licence files
Out of scope: third-party AI services a customer chooses to connect, the customer's own network, file servers and AI servers, and social engineering of LearnEX staff.
How the software is built
- Type checking, linting and automated tests on every change, including a security regression suite for access control and application hardening, plus a release checklist before each release. An internal code security review was carried out in October 2026 and its findings fixed.
- Hardened desktop shell: sandboxed interface, context isolation, a strict content security policy, and the Node.js run mode, debugger port and code loading from outside the application archive all switched off.
- Dependencies pinned in a lock file and audited before each release. Every release ships a software bill of materials (CycloneDX) and the open-source notices.
- Releases are built by CI from a tagged commit; the updater checks each download's size and SHA-256 before installing it.
For IT teams, the IT & Security Pack and our answers to the usual security questionnaire are available on request from it@learnexconsulting.com.
Last updated 17 November 2026.