Skip to content
Noroxi
CVE-2026-6479· NVD / CVE Program· CNA PostgreSQL

PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.59% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: n/a PostgreSQL 14.23, 15.18, 16.14; azl3 postgresql 16.12-1 on Azure Linux 3.0 16.14-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to n/a PostgreSQL 14.23, 15.18, 16.14; azl3 postgresql 16.12-1 on Azure Linux 3.0 16.14-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
May 14, 2026
Updated
Jun 17, 2026
EPSS
0.5% · 47th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · PostgreSQL
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-6479

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
postgresqlpostgresql

Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)

Watch new CVEs for postgresql

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is PostgreSQL on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • postgresql postgresqlbefore 14.23
  • postgresql postgresql15.0 and later · before 15.18
  • postgresql postgresql16.0 and later · before 16.14
  • postgresql postgresql17.0 and later · before 17.10
  • postgresql postgresql18.0 and later · before 18.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a PostgreSQL

    • 18 and later · before 18.4affected · rpm
    • 17 and later · before 17.10affected · rpm
    • 16 and later · before 16.14affected · rpm
    • 15 and later · before 15.18affected · rpm
    • before 14.23affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8pg_repackbefore 1.4.6-3.module_el8.9.0+3704+f1f917ce1.4.6-3.module_el8.9.0+3704+f1f917ce
AlmaLinux:8pgauditbefore 1.4.0-7.module_el8.10.0+3889+48cb11fb.alma.11.4.0-7.module_el8.10.0+3889+48cb11fb.alma.1
AlmaLinux:8pgauditbefore 1.4.0-7.module_el8.9.0+3740+0e74851f.alma.11.4.0-7.module_el8.9.0+3740+0e74851f.alma.1
AlmaLinux:8postgres-decoderbufsbefore 0.10.0-2.module_el8.9.0+3704+f1f917ce0.10.0-2.module_el8.9.0+3704+f1f917ce
AlmaLinux:8postgresqlbefore 12.22-9.module_el8.10.0+4249+5ffd6db712.22-9.module_el8.10.0+4249+5ffd6db7
AlmaLinux:8postgresql-contribbefore 12.22-9.module_el8.10.0+4249+5ffd6db712.22-9.module_el8.10.0+4249+5ffd6db7
AlmaLinux:8postgresql-upgradebefore 12.22-9.module_el8.10.0+4249+5ffd6db712.22-9.module_el8.10.0+4249+5ffd6db7
AlmaLinux:8postgresql-upgrade-develbefore 12.22-9.module_el8.10.0+4249+5ffd6db712.22-9.module_el8.10.0+4249+5ffd6db7
AlmaLinux:9postgresqlbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-contribbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-docsbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-plperlbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-plpython3before 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-pltclbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-private-develbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-private-libsbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-serverbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-server-develbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-staticbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-testbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-test-rpm-macrosbefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-upgradebefore 13.23-5.el9_813.23-5.el9_8
AlmaLinux:9postgresql-upgrade-develbefore 13.23-5.el9_813.23-5.el9_8
Alpine:v3.20postgresql15before 15.18-r015.18-r0

+96

Other highest-scoring records for the same primary product.

  • CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers
    57Plan
  • CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to
    55Plan
  • CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.
    49Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-6477May 14, 2026 · PostgreSQL libpq lo_* functions let server superuser overwrite client stack memory
    35Monitor
  • ← EarlierCVE-2026-6478May 14, 2026 · PostgreSQL discloses MD5-hashed passwords via covert timing channel
    26Monitor
  • Later →CVE-2026-6575May 14, 2026 · PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
n/a PostgreSQL14.23Vendor (CNA)
n/a PostgreSQL15.18Vendor (CNA)
n/a PostgreSQL16.14Vendor (CNA)
n/a PostgreSQL17.10Vendor (CNA)
n/a PostgreSQL18.4Vendor (CNA)
azl3 postgresql 16.12-1 on Azure Linux 3.016.14-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:postgresql13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-contrib13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-docs13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-plperl13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-plpython313.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-pltcl13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-private-devel13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-private-libs13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-server13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-server-devel13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-static13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:postgresql-test13.23-5.el9_8 · AlmaLinux:9Package registry (OSV)
alpine:postgresql1515.18-r0 · Alpine:v3.20Package registry (OSV)
alpine:postgresql1616.14-r0 · Alpine:v3.20Package registry (OSV)
alpine:postgresql1717.10-r0 · Alpine:v3.21Package registry (OSV)
alpine:postgresql1818.4-r0 · Alpine:v3.23Package registry (OSV)
debian:postgresql-1515.18-0+deb12u1 · Debian:12Package registry (OSV)
debian:postgresql-1717.10-0+deb13u1 · Debian:13Package registry (OSV)
debian:postgresql-1818.4-1 · Debian:14Package registry (OSV)
opensuse:postgresql1414.23-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1515.18-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1616.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1717.10-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:postgresql1818.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)

+32

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records