CVE-2018-16509

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 92% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2018-8320 (ENISA EUVD) · GHSA-98rm-3v6h-p8j6 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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 exploitation likelihood — EPSS 92%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Artifex Ghostscript before 9.24. Incorrect "restoration of privilege" checking during handling of /invalidaccess exceptions could be used by attackers able to supply crafted PostScript to execute code using the "pipe" instruction.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
72
EG Risk 72/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation92% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
92%
EPSS %ILE
99th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.8 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
92% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 5, 2018

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: redhat.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 1504-1] ghostscript security update

https://lists.debian.org/debian-lts-announce/2018/09/msg00015.html
Web page

699654 – /invalidaccess checks stop working after a failed restore

https://bugs.ghostscript.com/show_bug.cgi?id=699654
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2018:3760
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:2918
Web page

oss-sec: More Ghostscript Issues: Should we disable PS coders in policy.xml by default?

http://seclists.org/oss-sec/2018/q3/142

Vendor Advisories for CVE-2018-16509(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibgs9-common (9.18~dfsg~0-0ubuntu2.9) @ xenial2026-11-20ubuntu
redhatghostscript-0:8.70-24.el6_10.22018-12-03redhat
redhatghostscript-0:9.07-29.el7_5.22018-10-16redhat

These rows come from Ubuntu and Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript—
  • every version up to 9.25~dfsg-1: fixed in 9.25~dfsg-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript—
  • every version up to 9.25~dfsg-1: fixed in 9.25~dfsg-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript—
  • every version up to 9.25~dfsg-1: fixed in 9.25~dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript—
  • every version up to 9.25~dfsg-1: fixed in 9.25~dfsg-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript9.06~dfsg-2 ... 9.06~dfsg-2+deb8u7 (8 versions)
  • every version up to 9.06~dfsg-2+deb8u8: fixed in 9.06~dfsg-2+deb8u8
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
ghostscript9.20~dfsg-3.2, 9.20~dfsg-3.2+deb9u1, 9.20~dfsg-3.2+deb9u2, 9.20~dfsg-3.2+deb9u3, 9.20~dfsg-3.2+deb9u4
  • every version up to 9.20~dfsg-3.2+deb9u5: fixed in 9.20~dfsg-3.2+deb9u5
—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 62× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 180 rows 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. None are among the latest 100 rows. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry, 2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-45369✓ verified
    Published Sep 10, 2018

    Ghostscript - Failed Restore Command Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/fileformat/ghostscript_failed_restore✓ verified
    Published Sep 6, 2018

    Ghostscript Failed Restore Command Execution

    Open source ↗
  • GitHub PoCknqyf263/CVE-2018-16509
    Published Nov 17, 2018

    CVE-2018-16509 (Ghostscript contains multiple -dSAFER sandbox bypass vulnerabilities)

    Open source ↗
  • GitHub PoCfarisv/PIL-RCE-Ghostscript-CVE-2018-16509
    Published Oct 15, 2018

    PoC + Docker Environment for Python PIL/Pillow Remote Shell Command Execution via Ghostscript CVE-2018-16509

    Open source ↗

Frequently asked(5)

What is CVE-2018-16509?
CVE-2018-16509 is a critical-severity vulnerability; its CVE record was published on September 5, 2018. An issue was discovered in Artifex Ghostscript before 9.24. Incorrect "restoration of privilege" checking during handling of /invalidaccess exceptions could be used by attackers able to supply crafted PostScript to execute code using the "pipe" instruction.
When was CVE-2018-16509 made public?
CVE-2018-16509 was made public on September 5, 2018: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on September 5, 2018. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2018-16509 actively exploited?
CVE-2018-16509 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-16509?
CVE-2018-16509 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2018-16509?
A fix for CVE-2018-16509 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2018-16509 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-16509

Explore →

Is Your Infrastructure Affected by CVE-2018-16509?

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