CVE-2026-41167
Authenticated SQLi in Jellystat enables full DB read and potential PostgreSQL RCE.
Is CVE-2026-41167 being exploited?
Not confirmed. CVE-2026-41167 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-41167?
CVE-2026-41167 is rated Critical with a CVSS score of 9.1. 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-41167?
Yes. A fix has been recorded for CVE-2026-41167. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41167 affect?
CVE-2026-41167 affects Jellystat (<1.1.10). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41167?
Upgrade Jellystat to 1.1.10+; rotate credentials; monitor activity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth user can read any table (incl. app_config) and may trigger RCE via stacked queries (COPY TO PROGRAM) on PostgreSQL.
Patch when possible
- affected< 1.1.10
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.