Threats Tagged 'cve-2026-14681'
View all threats tagged with 'cve-2026-14681'. 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-14681'
Click on any threat for detailed analysis and mitigation recommendations
0 This security update for PostgreSQL 18 addresses multiple vulnerabilities affecting various components such as psql, logical decoding, pgcrypto, regexp, and others. The issues include heap buffer overflows that can lead to arbitrary code execution, type confusion, integer wraparound causing undersize allocations, privilege enforcement failures, and SQL injection risks. The update fixes these vulnerabilities to improve the security and stability of PostgreSQL 18 and related versions. Join the discussion | GCVE Database | 08/30/2026, 15:29:24 UTC Added: 08/13/2026, 17:48:23 UTC |
0 PostgreSQL versions 17 and 18 prior to 17.11 and 18.6 respectively have an issue where GSSAPI message integrity enforcement is improperly handled when used with SSL. This allows a connection to negotiate GSSAPI authentication contrary to pg_hba.conf rules by initially using a direct TLS connection. If TLS settings are more permissive than GSSAPI settings, the connection may proceed with weaker protection than intended. Versions before 17 are not affected. A patch is available to address this issue. Join the discussion | GCVE Database | 08/19/2026, 08:52:46 UTC Added: 08/13/2026, 17:48:22 UTC |
0 CVE-2026-14681 is a vulnerability in PostgreSQL's GSSAPI support where message integrity enforcement during transmission is improper. This allows a user to negotiate GSSAPI authentication contrary to the pg_hba.conf configuration via an initial direct TLS connection. If TLS settings are more permissive than GSSAPI settings, the connection may proceed with weaker protection. The issue affects PostgreSQL major versions 17 and 18, specifically versions before 17.11 and 18.6. Versions before 17 are not affected. Join the discussion | CVE Database V5 | 08/13/2026, 13:00:10 UTC Added: 08/13/2026, 13:26:47 UTC |
Showing 1 to 3 of 3 results