CVE-2026-14679: Stack-based Buffer Overflow in PostgreSQL
CVE-2026-14679 is a stack-based buffer overflow vulnerability in PostgreSQL affecting versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24. The flaw occurs during argument name matching for OUT parameters, allowing an object creator to write limited bytes (0x0 and 0x1) to the stack. This vulnerability has a high severity score of 8.2 and can lead to denial of service or other impacts on availability. No known exploits are reported in the wild. A fix is implied by the version boundaries but no explicit patch links or vendor advisory content are provided.
AI Analysis
Technical Summary
This vulnerability is a stack buffer overflow in PostgreSQL's argument name matching mechanism for OUT parameters. It allows an attacker with object creation privileges to write limited bytes (0x0 and 0x1) to the stack, potentially causing denial of service or other availability impacts. The vulnerability affects PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24. The CVSS 3.1 base score is 8.2, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to integrity and availability. No known exploits in the wild have been reported. Patch status is not explicitly confirmed in the provided data, but the affected version ranges suggest that fixed versions start at 18.6, 17.11, 16.15, 15.19, and 14.24 respectively.
Potential Impact
The vulnerability allows an attacker who can create objects in PostgreSQL to cause a stack buffer overflow by manipulating OUT parameter counts. This can lead to limited arbitrary writes (0x0 and 0x1 bytes) on the stack, potentially resulting in denial of service or other impacts on availability. There is no reported impact on confidentiality or system integrity beyond limited integrity impact. No active exploitation is known.
Mitigation Recommendations
Since the vulnerability affects versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24, upgrading PostgreSQL to these or later versions is recommended to remediate the issue. No explicit vendor advisory or patch links are provided, so users should consult official PostgreSQL release notes or security advisories for confirmation and apply the official fixes accordingly. No other mitigation guidance is available from the provided data.
CVE-2026-14679: Stack-based Buffer Overflow in PostgreSQL
Description
CVE-2026-14679 is a stack-based buffer overflow vulnerability in PostgreSQL affecting versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24. The flaw occurs during argument name matching for OUT parameters, allowing an object creator to write limited bytes (0x0 and 0x1) to the stack. This vulnerability has a high severity score of 8.2 and can lead to denial of service or other impacts on availability. No known exploits are reported in the wild. A fix is implied by the version boundaries but no explicit patch links or vendor advisory content are provided.
CVSS v3.1
Score 8.2high
Affected software
PostgreSQL
pkg:deb/postgresql/postgresqlRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability is a stack buffer overflow in PostgreSQL's argument name matching mechanism for OUT parameters. It allows an attacker with object creation privileges to write limited bytes (0x0 and 0x1) to the stack, potentially causing denial of service or other availability impacts. The vulnerability affects PostgreSQL versions before 18.6, 17.11, 16.15, 15.19, and 14.24. The CVSS 3.1 base score is 8.2, indicating high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to integrity and availability. No known exploits in the wild have been reported. Patch status is not explicitly confirmed in the provided data, but the affected version ranges suggest that fixed versions start at 18.6, 17.11, 16.15, 15.19, and 14.24 respectively.
Potential Impact
The vulnerability allows an attacker who can create objects in PostgreSQL to cause a stack buffer overflow by manipulating OUT parameter counts. This can lead to limited arbitrary writes (0x0 and 0x1 bytes) on the stack, potentially resulting in denial of service or other impacts on availability. There is no reported impact on confidentiality or system integrity beyond limited integrity impact. No active exploitation is known.
Mitigation Recommendations
Since the vulnerability affects versions prior to 18.6, 17.11, 16.15, 15.19, and 14.24, upgrading PostgreSQL to these or later versions is recommended to remediate the issue. No explicit vendor advisory or patch links are provided, so users should consult official PostgreSQL release notes or security advisories for confirmation and apply the official fixes accordingly. No other mitigation guidance is available from the provided data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-07-03T20:28:17.880Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7dc617bf8831d5393e53aa
Added to database: 08/13/2026, 13:26:47 UTC
Last enriched: 09/12/2026, 04:46:44 UTC
Last updated: 09/29/2026, 01:47:40 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.