Finding and attribution
Integer wraparound in several PostgreSQL server features could undersize allocations and cause out-of-bounds writes, with potential code execution under the database OS account.
Product: PostgreSQL. AI system: AISLE autonomous analyzer (specific model/version not disclosed). Team / organization: AISLE.
CVE identifiers: CVE-2026-6473.
AI and human contribution (source account): This finding was one of the eight CVEs AISLE says its autonomous analyzer detected across MySQL, MariaDB, and PostgreSQL. The report states that the findings were discovered by Pavel Kohout using AISLE; the specific model/version and division of human/model work are not disclosed.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The individual public CVE disclosure date and the July 7, 2026 public campaign attribution are recorded separately. Fix evidence is linked; no in-the-wild exploitation claim is made. PostgreSQL credits multiple reporters for this CVE; AISLE’s own campaign attributes its itemized finding to Pavel Kohout using AISLE. This supports AI involvement but does not establish discovery priority or sole authorship.
Remediation status: fix documented. The PostgreSQL security page documents affected/fixed versions and the integer-wraparound memory-safety issue. Its credits include Pavel Kohout and AISLE among multiple reporters. AISLE’s July 7 campaign explicitly attributes this itemized database finding to Pavel Kohout using AISLE.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 14 May 2026. AI attribution dated 7 Jul 2026. Sources checked 15 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: code execution, denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-6473: CVSS 3.1 · 8.8 (High) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. PostgreSQL (CNA; CVE Program record) · checked 16 Nov 2026. - CVE-2026-6473: CVSS 3.1 · 8.8 (High) ·
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. redhat-SADP (ADP; CVE Program record) · checked 16 Nov 2026.
CVE-2026-6473: code execution, denial of service.
Prerequisites / affected scope: An unprivileged database user can trigger undersized allocations/out-of-bounds writes that may execute code as the database OS user; gigabyte-scale application inputs can cause segmentation fault..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: The PostgreSQL security page documents affected/fixed versions and the integer-wraparound memory-safety issue. Its credits include Pavel Kohout and AISLE among multiple reporters. AISLE’s July 7 campaign explicitly attributes this itemized database finding to Pavel Kohout using AISLE.