Threats Tagged 'cve-2026-15741'
View all threats tagged with 'cve-2026-15741'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-15741'
Click on any threat for detailed analysis and mitigation recommendations
SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. (CVE-2026-15741)CVE-2026-15741 0 A SQL injection vulnerability exists in the PostgreSQL EXTRACT() function deparse process that allows an object owner to execute arbitrary SQL commands with superuser privileges via a malicious object definition. This affects tools and commands that consume expression deparse output, including pg_dump and psql commands like \sf. Versions prior to PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are impacted. Join the discussion | GCVE Database | 08/13/2026, 15:34:36 UTC Added: 08/13/2026, 17:48:22 UTC |
CVE-2026-15741: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in PostgreSQLCVE-2026-15741 0 SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a superuser via a hostile object definition. Attacks affect expression deparse consumers broadly, including pg_dump, psql commands like \sf, and any similar usage in non-core tools. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. Join the discussion | CVE Database V5 | 08/13/2026, 13:00:11 UTC Added: 08/13/2026, 13:26:47 UTC |
Showing 1 to 2 of 2 results