What is CVE-2018-1058?

CVE-2018-1058 is A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. The supplied enrichment data classifies it as Input Validation mapped to CWE-20 Improper Input Validation.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2018-1058 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

140 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2018-1058 using CVSS 8.8, EPSS 13%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highInput Validationpublic exploit

CVE-2018-1058

CVE-2018-1058 — A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users

A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database. Versions 9.3 through 10 are affected.

Published Mar 2, 2018Updated Jun 17, 2026Sources: NVD, The PostgreSQL Global Development Group (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX)

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

13%

chance of exploitation in 30 days

Affects

The PostgreSQL Global Development Group

postgresql

CVSS base

8.8

high · 3 sources

Remediation

The vendor's own words where we have them.

Upgrade postgresql to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2018-1058

fixed427affected51not affected41

vendor_fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is run…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
The PostgreSQL Global Development Group	postgresql	9.3 - 10	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	high	2.8	5.9	NVD
6.5	CVSS 2.0	medium	8	6.4	NVD
8.8	CVSS 3.1	high	—	—	GHSA, Red Hat (VEX)

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

Weakness & attack patterns

CWE-20Improper Input Validation

Inferred from the weakness class — not observed against this CVE.

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

140

1 of the 5 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable postgresql.
Monitor for scanner or exploit-pattern traffic after 140 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.8 (AV:N)
Jun 17, 2026 · NVD
2022
Added · GHSA-wj3f-f94q-2r98 published (high)
May 13, 2022 · GitHub Security Advisory
2018
Initial · CVE published
Mar 2, 2018 · NVD

References

11 on the record

www.securityfocus.com/bid/103221
Third Party Advisory, VDB Entry
access.redhat.com/errata/RHSA-2018:2511
Third Party Advisory
access.redhat.com/errata/RHSA-2018:2566
Third Party Advisory
access.redhat.com/errata/RHSA-2018:3816
Third Party Advisory
bugzilla.redhat.com/show_bug.cgi?id=1547044
Issue Tracking, Third Party Advisory
usn.ubuntu.com/3589-1/
Third Party Advisory
www.postgresql.org/about/news/1834/
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2018-1058
NVD

Elsewhere on this site

The PostgreSQL Global Development Groupevery CVE for this vendor
Input Validationsame class
CWE-20other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2018-1058 is A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users, a high vulnerability affecting postgresql from The PostgreSQL Global Development Group. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 140 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 13% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.