CVE
PostgreSQL SQL injection in pg_dump not-null constraint names
Affects PostgreSQL 18 minor versions before 18.7 when an inherited column has a child-local not-null constraint whose name requires quoting. Fixed in 18.7.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 18.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. PostgreSQL major version 18 with minor versions before 18.7 An inherited column has a child-local not-null constraint whose name requires quoting Attacker has permission to create non-temporary objects in at least one schema
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.43% · 37th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 35/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
PostgreSQL's pg_dump tool has an SQL injection flaw that lets an object creator run arbitrary SQL as the user who restores the dump. An attacker can exploit it over the network with low-privilege login and no user action, by creating an inherited column with a child-local not-null constraint whose name requires quoting.
Read the original description
SQL injection in PostgreSQL pg_dump allows an object creator to execute arbitrary SQL as the user restoring the dump, via an inherited column having a child-local not-null constraint whose name requires quoting. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.
Who should check
Teams running PostgreSQL 18.x below 18.7 where users can create non-temporary objects in a schema and who restore pg_dump output.
Read the source excerpt
“Within major version 18, minor versions before PostgreSQL 18.7 are affected.”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach17/20Affects PostgreSQL (a widely deployed server, runtime, framework or database)
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 42 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
PostgreSQL major version 18 with minor versions before 18.7 An inherited column has a child-local not-null constraint whose name requires quoting Attacker has permission to create non-temporary objects in at least one schemaUpgrade to a fixed version: 18.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116318 (PostgreSQL pg_dump not-null constraint name allows SQL injection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-116318 (entry last updated 2026-11-13):
Affected:
- n/a PostgreSQL: from 18, fixed in 18.7
Fixed versions: 18.7.
Conditions (all must be true for the bug to be hit):
- PostgreSQL major version 18 with minor versions before 18.7 (source: https://www.postgresql.org/support/security/CVE-2026-116318/)
- An inherited column has a child-local not-null constraint whose name requires quoting (source: https://www.postgresql.org/support/security/CVE-2026-116318/)
- Attacker has permission to create non-temporary objects in at least one schema (source: https://www.cve.org/CVERecord?id=CVE-2026-116318)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-116318 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116318 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.postgresql.org/support/security/CVE-2026-116318/
- https://www.cve.org/CVERecord?id=CVE-2026-116318
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-116318
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-116318"}.Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- Record last updated
Affected versions
- n/a PostgreSQL
From 18 · fixed in 18.7
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116318
Is CVE-2026-116318 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
When pg_dump writes a not-null constraint whose name needs quoting on an inherited column, the dump can contain injected SQL. Restoring that dump runs the injected SQL as the user doing the restore.Source: postgresql.org, cve.org
Which versions are affected by CVE-2026-116318?
PostgreSQL: from 18 before 18.7.Source: cve.now feed data
Am I affected, and how do I check?
PostgreSQL 18 minor versions before 18.7 are affected. To check a version, run SELECT version(); in psql or postgres --version on the server. The bug needs an inherited column with a child-local not-null constraint whose name requires quoting, and an attacker who can create non-temporary objects in at least one schema.Source: postgresql.org, cve.org
How do I fix CVE-2026-116318?
Upgrade to a fixed version: 18.7. The vendor's advisory also recommends PostgreSQL 18.7 or later.Source: cve.now feed data, postgresql.org