CVE-2018-1115

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.8%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
3.8%
EPSS %ILE
90th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 10, 2018

Last Modified

October 8, 2026

Advisory Details (5)

Auto-updated Jul 19, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:2565
Web page

PostgreSQL: Multiple vulnerabilities (GLSA 201810-08) — Gentoo security

https://security.gentoo.org/glsa/201810-08
Red HatMentions a patch (unverified)

1573276 – (CVE-2018-1115) CVE-2018-1115 postgresql: Too-permissive access control list on function pg_logfile_rotate()

Affected: Red Hat Enterprise Linux 7

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1115
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:2566

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrh-postgresql96-postgresql-0:9.6.10-1.el72018-08-27redhat
redhatrh-postgresql10-postgresql-0:10.5-1.el72018-08-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(19 across 17 ecosystems)
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
postgresql15—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
postgresql15—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.4(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 9.5.13-r0: fixed in 9.5.13-r0
—
Alpine:v3.5(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 9.6.9-r0: fixed in 9.6.9-r0
—
Alpine:v3.6(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 9.6.9-r0: fixed in 9.6.9-r0
—
Alpine:v3.7(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 10.0 up to 10.4-r0: fixed in 10.4-r0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 217 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:27 UTCEPSS rescoreEPSS 3.8% · 90th percentile
  2. 2026-10-22 22:52 UTCEG score recompute
  3. 2026-10-22 22:52 UTCVendor advisory
  4. 2026-10-22 22:52 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-22 16:28 UTCEPSS rescoreEPSS 3.8% · 90th percentile
  6. 2026-10-22 00:49 UTCEG score recompute
  7. 2026-10-22 00:49 UTCVendor advisory
  8. 2026-10-22 00:49 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-21 16:27 UTCEPSS rescoreEPSS 3.8% · 90th percentile
  10. 2026-10-21 02:43 UTCEG score recompute
  11. 2026-10-21 02:43 UTCVendor advisory
  12. 2026-10-21 02:43 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-20 16:27 UTCEPSS rescoreEPSS 3.8% · 89th percentile
  14. 2026-10-20 04:42 UTCEG score recompute
  15. 2026-10-20 04:42 UTCVendor advisory
  16. 2026-10-20 04:42 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-19 16:27 UTCEPSS rescoreEPSS 3.8% · 89th percentile
  18. 2026-10-19 05:35 UTCEG score recompute
  19. 2026-10-19 05:35 UTCVendor advisory
  20. 2026-10-19 05:35 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-18 16:27 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  22. 2026-10-18 07:31 UTCEG score recompute
  23. 2026-10-18 07:31 UTCVendor advisory
  24. 2026-10-18 07:31 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-17 16:27 UTCEPSS rescoreEPSS 3.9% · 90th percentile
Show 74 more
  1. 2026-10-17 09:21 UTCEG score recompute
  2. 2026-10-17 09:21 UTCVendor advisory
  3. 2026-10-17 09:21 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-16 16:30 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  5. 2026-10-16 11:19 UTCEG score recompute
  6. 2026-10-16 11:19 UTCVendor advisory
  7. 2026-10-16 11:19 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-15 16:27 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  9. 2026-10-15 11:48 UTCEG score recompute
  10. 2026-10-15 11:48 UTCVendor advisory
  11. 2026-10-15 11:47 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-14 16:27 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  13. 2026-10-14 07:17 UTCEG score recompute
  14. 2026-10-14 07:17 UTCVendor advisory
  15. 2026-10-14 07:17 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-13 16:27 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  17. 2026-10-13 02:33 UTCVendor advisory
  18. 2026-10-13 02:33 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-12 20:21 UTCEG score recompute
  20. 2026-10-12 16:28 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  21. 2026-10-12 00:44 UTCEG score recompute
  22. 2026-10-11 13:41 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  23. 2026-10-10 19:55 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  24. 2026-10-09 20:02 UTCEPSS rescoreEPSS 3.9% · 90th percentile
  25. 2026-10-08 22:31 UTCVendor advisory
  26. 2026-10-08 22:31 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-08 21:35 UTCEG score recompute
  28. 2026-10-08 21:35 UTCVendor advisory
  29. 2026-10-08 21:35 UTCGHSA enrichmentGHSA-54w7-jv4g-qhqg · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-08 16:36 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  31. 2026-10-07 23:42 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  32. 2026-10-06 15:12 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  33. 2026-10-05 17:39 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  34. 2026-10-03 14:21 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  35. 2026-10-01 19:44 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  36. 2026-09-30 14:59 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  37. 2026-09-30 09:51 UTCEG score recompute
  38. 2026-09-29 05:02 UTCOSV refresh
  39. 2026-09-28 13:45 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  40. 2026-09-27 13:40 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  41. 2026-09-26 15:53 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  42. 2026-09-24 13:59 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  43. 2026-09-20 20:10 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  44. 2026-09-19 15:36 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  45. 2026-09-18 19:22 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  46. 2026-09-17 19:22 UTCEPSS rescoreEPSS 3.9% · 89th percentile
  47. 2026-09-16 05:06 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  48. 2026-09-15 03:05 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  49. 2026-09-13 16:42 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  50. 2026-09-12 14:56 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  51. 2026-09-11 14:47 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  52. 2026-09-11 09:32 UTCEPSS rescoreEPSS 4.0% · 90th percentile
  53. 2026-09-09 09:23 UTCOSV refresh
  54. 2026-09-07 15:57 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  55. 2026-09-06 13:43 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  56. 2026-09-05 15:24 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  57. 2026-09-04 13:56 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  58. 2026-09-04 05:02 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  59. 2026-09-02 14:07 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  60. 2026-09-01 13:49 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  61. 2026-09-01 03:32 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  62. 2026-08-28 21:36 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  63. 2026-08-27 14:21 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  64. 2026-08-26 14:42 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  65. 2026-08-25 13:44 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  66. 2026-08-22 17:37 UTCOSV refresh
  67. 2026-08-21 23:45 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  68. 2026-08-20 22:51 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  69. 2026-08-19 17:00 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  70. 2026-08-18 13:44 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  71. 2026-08-17 13:43 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  72. 2026-08-16 14:51 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  73. 2026-08-16 02:10 UTCEPSS rescoreEPSS 4.0% · 89th percentile
  74. 2026-08-15 01:26 UTCEPSS rescoreEPSS 4.0% · 89th percentile

Frequently asked(5)

What is CVE-2018-1115?
CVE-2018-1115 is a critical-severity vulnerability; its CVE record was published on May 10, 2018. postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pgcatalog.pglogfilerotate() function doesn't follow the same ACLs than pgrorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.
When was CVE-2018-1115 made public?
CVE-2018-1115 was made public on April 30, 2018: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on May 10, 2018. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2018-1115 actively exploited?
CVE-2018-1115 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.8% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-1115?
CVE-2018-1115 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2018-1115?
A fix for CVE-2018-1115 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-1115 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-1115

Explore →

Is Your Infrastructure Affected by CVE-2018-1115?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.