CVE-2018-16858

CRITICALNVD 7.89.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 7.8; sources differ by 2.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 67%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

It was found that libreoffice before versions 6.0.7 and 6.1.3 was vulnerable to a directory traversal attack which could be used to execute arbitrary macros bundled with a document. An attacker could craft a document, which when opened by LibreOffice, would execute a Python method from a script in any arbitrary file system location, specified relative to the LibreOffice install location.

CVSS v3
7.8
EG Score
9.8(medium)
EG Risk
76(Track*)
EG Risk 76/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation67% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
67%
EPSS %ILE
99%
KEV
Not listed

Published

March 25, 2019

Last Modified

November 21, 2024

References (16)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuure (5.1.6~rc2-0ubuntu1~xenial6) @ xenial2026-05-27ubuntu
redhatlibreoffice-1:5.3.6.1-21.el72019-08-08redhat

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

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libreoffice—1:6.1.3-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libreoffice—1:6.1.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libreoffice—1:6.1.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libreoffice—1:6.1.3-1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
libreoffice1:4.3.3-2 ... 1:4.3.3-2+deb8u9 (16 versions)1:4.3.3-2+deb8u12—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
libreoffice1:5.2.7-1 ... 1:5.2.7-1+deb9u4~bpo8+1 (7 versions)1:5.2.7-1+deb9u5—

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:22 UTCEPSS rescore
  2. 2026-09-17 19:22 UTCEPSS rescore
  3. 2026-09-16 14:03 UTCEPSS rescore
  4. 2026-09-16 05:06 UTCEPSS rescore
  5. 2026-09-15 03:05 UTCEPSS rescore
  6. 2026-09-12 14:56 UTCEPSS rescore
  7. 2026-09-11 14:47 UTCEPSS rescore
  8. 2026-09-10 09:27 UTCEPSS rescore
  9. 2026-09-08 15:34 UTCOSV refresh
  10. 2026-09-06 13:43 UTCEPSS rescore
  11. 2026-09-05 15:24 UTCEPSS rescore
  12. 2026-09-04 13:56 UTCEPSS rescore
  13. 2026-09-04 05:02 UTCEPSS rescore
  14. 2026-09-02 14:07 UTCEPSS rescore
  15. 2026-09-02 14:07 UTCEPSS rescore
  16. 2026-09-01 13:49 UTCEPSS rescore
  17. 2026-08-30 19:13 UTCEPSS rescore
  18. 2026-08-28 21:36 UTCEPSS rescore
  19. 2026-08-27 14:21 UTCEPSS rescore
  20. 2026-08-26 14:41 UTCEPSS rescore
  21. 2026-08-23 00:14 UTCEPSS rescore
  22. 2026-08-22 01:11 UTCOSV refresh
  23. 2026-08-21 23:44 UTCEPSS rescore
  24. 2026-08-20 22:51 UTCEPSS rescore
  25. 2026-08-19 17:00 UTCEPSS rescore
Show 69 more
  1. 2026-08-17 13:42 UTCEPSS rescore
  2. 2026-08-16 02:10 UTCEPSS rescore
  3. 2026-08-15 01:26 UTCEPSS rescore
  4. 2026-08-13 21:56 UTCEPSS rescore
  5. 2026-08-12 13:46 UTCEPSS rescore
  6. 2026-08-11 13:36 UTCEPSS rescore
  7. 2026-08-07 16:22 UTCEPSS rescore
  8. 2026-08-06 05:54 UTCOSV refresh
  9. 2026-07-30 16:24 UTCEPSS rescore
  10. 2026-07-30 01:27 UTCEPSS rescore
  11. 2026-07-28 15:32 UTCEPSS rescore
  12. 2026-07-26 14:51 UTCEPSS rescore
  13. 2026-07-26 14:51 UTCEPSS rescore
  14. 2026-07-24 14:14 UTCEPSS rescore
  15. 2026-07-23 14:15 UTCEPSS rescore
  16. 2026-07-23 14:15 UTCEPSS rescore
  17. 2026-07-23 01:34 UTCEG score recompute
  18. 2026-07-22 22:14 UTCEG score recompute
  19. 2026-07-22 14:04 UTCEPSS rescore
  20. 2026-07-21 15:21 UTCEPSS rescore
  21. 2026-07-20 20:02 UTCOSV refresh
  22. 2026-07-20 17:04 UTCEPSS rescore
  23. 2026-07-20 17:04 UTCEPSS rescore
  24. 2026-07-19 14:28 UTCEPSS rescore
  25. 2026-07-16 16:59 UTCEPSS rescore
  26. 2026-07-16 16:59 UTCEPSS rescore
  27. 2026-07-15 16:55 UTCEPSS rescore
  28. 2026-07-13 22:26 UTCEPSS rescore
  29. 2026-07-13 06:10 UTCEPSS rescore
  30. 2026-07-11 08:24 UTCEPSS rescore
  31. 2026-07-09 19:06 UTCEPSS rescore
  32. 2026-07-08 15:11 UTCEPSS rescore
  33. 2026-07-05 02:27 UTCEPSS rescore
  34. 2026-07-03 15:26 UTCOSV refresh
  35. 2026-07-02 16:54 UTCEPSS rescore
  36. 2026-07-01 15:03 UTCEPSS rescore
  37. 2026-07-01 15:03 UTCEPSS rescore
  38. 2026-06-28 04:53 UTCEPSS rescore
  39. 2026-06-28 04:53 UTCEPSS rescore
  40. 2026-06-25 13:47 UTCEPSS rescore
  41. 2026-06-25 13:47 UTCEPSS rescore
  42. 2026-06-24 14:02 UTCEPSS rescore
  43. 2026-06-24 14:02 UTCEPSS rescore
  44. 2026-06-23 21:30 UTCEPSS rescore
  45. 2026-06-22 14:23 UTCEPSS rescore
  46. 2026-06-19 19:23 UTCEPSS rescore
  47. 2026-06-18 17:50 UTCEPSS rescore
  48. 2026-06-18 17:50 UTCEPSS rescore
  49. 2026-06-17 17:50 UTCEPSS rescore
  50. 2026-06-17 17:50 UTCEPSS rescore
  51. 2026-06-16 17:50 UTCEPSS rescore
  52. 2026-06-16 17:50 UTCEPSS rescore
  53. 2026-06-15 17:45 UTCEPSS rescore
  54. 2026-06-15 04:43 UTCOSV refresh
  55. 2026-06-12 23:09 UTCEPSS rescore
  56. 2026-06-10 22:16 UTCEPSS rescore
  57. 2026-06-01 13:49 UTCEPSS rescore
  58. 2026-05-31 22:29 UTCEPSS rescore
  59. 2026-05-31 22:28 UTCEPSS rescore
  60. 2026-05-31 00:14 UTCEPSS rescore
  61. 2026-05-31 00:14 UTCEPSS rescore
  62. 2026-05-29 13:41 UTCEPSS rescore
  63. 2026-05-28 13:42 UTCEPSS rescore
  64. 2026-05-28 13:42 UTCEPSS rescore
  65. 2026-05-27 21:28 UTCEG score recompute
  66. 2026-05-27 21:28 UTCVendor advisory
  67. 2026-05-27 21:28 UTCGHSA enrichment
  68. 2026-05-26 07:17 UTCEPSS rescore
  69. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-46727✓ verified
    First seen Apr 18, 2019

    LibreOffice < 6.0.7 / 6.1.3 - Macro Code Execution (Metasploit)

    Open source ↗
  • GitHub PoC4nimanegra/libreofficeExploit1
    First seen Apr 14, 2019

    CVE-2018-16858 exploit implementation

    Open source ↗
  • Metasploitexploit/multi/fileformat/libreoffice_macro_exec✓ verified
    First seen Oct 18, 2018

    LibreOffice Macro Code Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-16858?
CVE-2018-16858 is a critical vulnerability published on March 25, 2019. It was found that libreoffice before versions 6.0.7 and 6.1.3 was vulnerable to a directory traversal attack which could be used to execute arbitrary macros bundled with a document. An attacker could craft a document, which when opened by LibreOffice, would execute a Python method from a script in…
When was CVE-2018-16858 disclosed?
CVE-2018-16858 was first published in the National Vulnerability Database on March 25, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-16858 actively exploited?
CVE-2018-16858 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67% probability of exploitation in the next 30 days, which ranks it in the top 0.7% of all scored CVEs.
What is the CVSS score of CVE-2018-16858?
CVE-2018-16858 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2018-16858?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16858, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2018-16858?

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

Start Free Scan →Browse All CVEs