# CVE-2026-6479: PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion > An attacker with socket access can cause sustained denial of service in PostgreSQL via uncontrolled recursion during SSL or GSS negotiation. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 May 2026 - **Updated:** 14 May 2026 - **Also known as:** ALPINE-CVE-2026-6479, ALSA-2026:52395, ALSA-2026:52396, AZL-86843, BELL-CVE-2026-6479, BIT-postgresql-2026-6479, DEBIAN-CVE-2026-6479, ECHO-c17a-46ab-75a9, GHSA-hwfh-mh4f-m67f, JLSEC-2026-606, MINI-3q4p-xr3c-g323, MINI-662c-pjrh-mw5c, MINI-884q-vq7p-mwmp, MINI-8vjf-c7vw-fw2m, MINI-9xrf-4g6p-4fcj, MINI-fp6p-q6gg-m3xc, RHSA-2026:52395, RHSA-2026:52396, RHSA-2026:57633, RHSA-2026:60265, RHSA-2026:61254, RHSA-2026:61255, RHSA-2026:62116, RHSA-2026:62117, RLSA-2026:52395, RLSA-2026:52396, UBUNTU-CVE-2026-6479 ## What is CVE-2026-6479? CVE-2026-6479 is a high-severity denial of service vulnerability in Postgresql Postgresql, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected. Weakness: CWE-674 (Uncontrolled Recursion) ## Which versions are affected by CVE-2026-6479? 1 open source package ship an affected version, including postgresql. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `postgresql` | Bitnami | All versions | 14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0 | | `pg_repack` | AlmaLinux:8 | All versions | 1.4.6-3.module_el8.9.0+3704+f1f917ce | | `pgaudit` | AlmaLinux:8 | All versions | 1.4.0-7.module_el8.10.0+3889+48cb11fb.alma.1 | | `pgaudit` | AlmaLinux:8 | All versions | 1.4.0-7.module_el8.9.0+3740+0e74851f.alma.1 | | `postgres-decoderbufs` | AlmaLinux:8 | All versions | 0.10.0-2.module_el8.9.0+3704+f1f917ce | | `postgresql` | AlmaLinux:8 | All versions | 12.22-9.module_el8.10.0+4249+5ffd6db7 | | `postgresql-contrib` | AlmaLinux:8 | All versions | 12.22-9.module_el8.10.0+4249+5ffd6db7 | | `postgresql-upgrade` | AlmaLinux:8 | All versions | 12.22-9.module_el8.10.0+4249+5ffd6db7 | | `postgresql-upgrade-devel` | AlmaLinux:8 | All versions | 12.22-9.module_el8.10.0+4249+5ffd6db7 | | `postgresql` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-contrib` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-docs` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-plperl` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-plpython3` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-pltcl` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-private-devel` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-private-libs` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-server` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-server-devel` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-static` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-test` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-test-rpm-macros` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-upgrade` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `postgresql-upgrade-devel` | AlmaLinux:9 | All versions | 13.23-5.el9_8 | | `pg_repack` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.6-3.module+el8.9.0+19330+c97ddbdf | | `pg_repack-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.6-3.module+el8.9.0+19330+c97ddbdf | | `pg_repack-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.6-3.module+el8.9.0+19330+c97ddbdf | | `pgaudit` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.0-7.module+el8.10.0+22214+9beb89d6 | | `pgaudit-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.0-7.module+el8.10.0+22214+9beb89d6 | | `pgaudit-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.4.0-7.module+el8.10.0+22214+9beb89d6 | | `postgres-decoderbufs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.10.0-2.module+el8.9.0+19330+c97ddbdf | | `postgres-decoderbufs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.10.0-2.module+el8.9.0+19330+c97ddbdf | | `postgres-decoderbufs-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:0.10.0-2.module+el8.9.0+19330+c97ddbdf | | `postgresql` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-contrib` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-contrib-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-docs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | | `postgresql-docs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:12.22-9.module+el8.10.0+24635+941a3cac | Products: Postgresql Postgresql. ## How do I fix CVE-2026-6479? Upgrade postgresql to a fixed version for your release line: 14.23.0, 15.18.0, 16.14.0 or 17.10.0. ## Is CVE-2026-6479 being exploited? There is no known exploitation of CVE-2026-6479 in the wild and no public exploit code. ## Other vulnerabilities in Postgresql Postgresql - [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0) - [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0) - [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0) - [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0) - [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-6479 and fix it if it is affected. What it is: CVE-2026-6479 is a high-severity denial of service vulnerability in Postgresql Postgresql, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-6479 in the wild and no public exploit code. Affected packages and fixed versions: - postgresql (Bitnami): affected all versions; fixed in 14.23.0, 15.18.0, 16.14.0, 17.10.0, 18.4.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-6479/ (Markdown: https://insights.sbomify.com/CVE-2026-6479/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6479 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6479 - OSV: https://osv.dev/vulnerability/CVE-2026-6479 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-6479/ Summaries are generated and may contain mistakes; the official description above is the record.