CVE-2026-16019
SQL injection in FAYDAM Datalogger <2.8.0 enables DB compromise and unauthorized actions
Is CVE-2026-16019 being exploited?
Not confirmed. CVE-2026-16019 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-16019?
CVE-2026-16019 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16019?
Yes. A fix has been recorded for CVE-2026-16019. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16019 affect?
CVE-2026-16019 affects FAYDAM Datalogger (versions >=2.7.1 and <2.8.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16019?
Upgrade to FAYDAM Datalogger 2.8.0 and restrict network access to affected devices
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote SQL injection allows attackers to read/modify device DB, tamper logs, execute unauthorized commands and pivot to networks.
Immediate action required
- affected>= 2.7.1 and < 2.8.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.