InfrastructureHigh 8.8Patch available
CVE-2026-6460
PostgreSQL type-confusion RCE allowing DB object creators to run OS code.
How scary is it?
updated 14 Nov 2026- No
Works without logging in1
Needs a login: a basic user account (CVSS PR:L).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
2 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- None known
Attacks seen in the wild1
None reported that we know of. CISA's SSVC assessment says exploitation: none.
- No
On CISA's exploited list3
Not in the catalog as of our last sync.
Scare-o-meter
Act this week
Serious and within reach of attackers. Schedule the fix this week.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 8.8.1 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run PostgreSQL in an affected version>= 18 and < 18.7 / >= 17 and < 17.12 / >= 16 and < 16.16 (+2 more)
>= 18 and < 18.7 >= 17 and < 17.12 >= 16 and < 16.16 >= 15 and < 15.20 < 14.25
The CVE record states no fixed release.
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
The attacker has a user account
CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
Recommendation, AI-writtenUpgrade to fixed versions (18.7,17.12,16.16,15.20,14.25) and restrict DB owner privileges until patched.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. PostgreSQL is widely deployed; this flaw enables OS-level code execution on DB hosts, risking broad data/host compromise across enterprises.
- CVSS
- 8.8Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
- EPSS
- 0.64%chance of exploitation in the next 30 daystop 49% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 12 Nov 2026analysed here 14 Nov 2026
Summary
Impact
Object creators can execute arbitrary code as the DB server OS user via DDL (e.g., ALTER ... SET DATA TYPE), enabling host compromise and data access.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| PostgreSQL | >= 18 and < 18.7>= 17 and < 17.12>= 16 and < 16.16>= 15 and < 15.20< 14.25Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- PostgreSQL < 18.7
- PostgreSQL < 17.12
- PostgreSQL < 16.16
- PostgreSQL < 15.20
- PostgreSQL < 14.25
- PostgreSQL server (object creators / DDL paths)
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? No. The vulnerability requires database object creators to exploit it, meaning the attacker must have local or authenticated access to the database server. It is not triggered via HTTP requests, so a web application firewall cannot detect or block it.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
- CISA SSVC
- exploitation none, automatable no, technical impact totalAssessed by CISA 12 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 12 Nov 2026CISA SSVC assessment: exploitation none
- 12 Nov 2026Published1 day later
- 13 Nov 2026First proof-of-concept repository on GitHub (unvetted)same day later
- 13 Nov 2026CVE record last updatedsame day later
- 14 Nov 2026Analysed by vulneraibility.com1 day later
Common questions
Is CVE-2026-6460 being exploited?
Not confirmed. CVE-2026-6460 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.64% probability of exploitation in the next 30 days.
How severe is CVE-2026-6460?
CVE-2026-6460 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-6460?
Yes. A fix has been recorded for CVE-2026-6460. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-6460 affect?
CVE-2026-6460 affects PostgreSQL < 18.7, PostgreSQL < 17.12, PostgreSQL < 16.16, PostgreSQL < 15.20, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-6460?
Upgrade to fixed versions (18.7,17.12,16.16,15.20,14.25) and restrict DB owner privileges until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
1 reference in the CVE record, grouped by the tags the record gives them.
Other links (1)
- postgresql.org /support/security/CVE-2026-6460/
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.