Skip to content

High 7.2Patch available

CVE-2019-9193

In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to execute arbitrary code in the context of the database's operating system user. This functionality is enabled by default and can be abused to run arbitrary operating system commands on Windows, Linux, and macOS. NOTE: Third parties claim/state this is not an issue because PostgreSQL functionality for ‘COPY TO/FROM PROGRAM’ is acting as intended. References state that in PostgreSQL, a superuser can execute commands as the server user without using the ‘COPY FROM PROGRAM’.

How scary is it?

updated 22 Nov 2026
  • No

    Works without logging in1

    Needs a login: an administrator-level account (CVSS PR:H).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Public exploit code is out2345

    3 on Exploit-DB · 1 Metasploit module · 10 GitHub proofs of concept · 1 Nuclei template.

  • None known

    Attacks seen in the wild6

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list7

    Not in the catalog as of our last sync.

Scare-o-meter

Drop everything

A working exploit is public. Patch now.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: A working exploit is public (Exploit-DB, Metasploit or Nuclei).23 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. Product names from our AI analysisYou run postgresql:postgresql

    We hold no version range from the vendor for this CVE. These product names were written by a language model from the CVE record: check them against the sources.

    See the products named

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. The attacker has an administrator-level account

    CVSS privileges required: High (PR:H). The attacker needs admin-level 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

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

CVSS
7.2High
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
91.7%chance of exploitation in the next 30 daystop 0.2% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
1 Apr 2019analysed here 22 Nov 2026

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

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

Products named in our analysis

  • postgresql:postgresql

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.

Also consider: shlex/execve-style APIs

Based on the weakness type only; no CVE-specific evidence 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
Yes: 3 on Exploit-DB · 1 Metasploit module · 10 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 24 Apr 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

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

  1. 1 Apr 2019Published
  2. 8 May 2019First public exploit or proof of concept36 days later
  3. 24 Apr 2024CISA SSVC assessment: exploitation none1,814 days (about 5 years) later
  4. 15 Nov 2024CVE record last updated205 days (about 7 months) later
  5. 22 Nov 2026Analysed by vulneraibility.com736 days (about 2 years) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredHighThe attacker needs admin-level privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2019-9193 being exploited?

Not confirmed. CVE-2019-9193 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 92% probability of exploitation in the next 30 days.

How severe is CVE-2019-9193?

CVE-2019-9193 is rated High with a CVSS score of 7.2. 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-2019-9193?

Yes. A fix has been recorded for CVE-2019-9193. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-9193 affect?

CVE-2019-9193 affects postgresql:postgresql. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

8 references in the CVE record, grouped by the tags the record gives them.

Other links (8)

  • paquier.xyz /postgresql-2/postgres-9-3-feature-highlight-copy-tofrom-program/
  • medium.com /greenwolf-security/authenticated-arbitrary-command-execution-on-postgresql-9-3-
  • blog.hagander.net /when-a-vulnerability-is-not-a-vulnerability-244/
  • trustwave.com /en-us/resources/blogs/spiderlabs-blog/authenticated-arbitrary-command-execution
  • security.netapp.com /advisory/ntap-20190502-0003/
  • packetstormsecurity.com /files/152757/PostgreSQL-COPY-FROM-PROGRAM-Command-Execution.html
Show 2 more

Where the data on this page comes from

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.