Answer in brief
CVE-2026-14679 records a Unknown severity vulnerability in PostgreSQL stack buffer overflow in argument match writes 0x0 and 0x1 to server memory. The current sources do not mark it as known exploited. The current feed maps n/a/PostgreSQL (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps n/a/PostgreSQL (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| n/a/PostgreSQLgeneric | >=18 <18.5 || >=17 <17.11 || >=16 <16.15 || >=15 <15.19 || >=0 <14.24 | 18.5, 17.11, 16.15, 15.19, 14.24 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-14679 records a Unknown severity vulnerability in PostgreSQL stack buffer overflow in argument match writes 0x0 and 0x1 to server memory. The current sources do not mark it as known exploited. The current feed maps n/a/PostgreSQL (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps n/a/PostgreSQL (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| n/a/PostgreSQLgeneric | >=18 <18.5 || >=17 <17.11 || >=16 <16.15 || >=15 <15.19 || >=0 <14.24 | 18.5, 17.11, 16.15, 15.19, 14.24 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 13, 2026
Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown impacts via OUT parameter count. The attack can write only 0x0 and 0x1 bytes. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
Quoted source text, attributed separately from HOL analysis.