CVE-2018-16858

HIGHNVD 7.89.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
7.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
CISA-KEV: Not listedEPSS: 67%CVSS: 7.8Exploit: NoneExposed: 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(high)
EPSS
99.2%
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.

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 8× in last 7d / 26× 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-07-22 14:04 UTCEPSS rescore
  2. 2026-07-21 15:21 UTCEPSS rescore
  3. 2026-07-20 20:02 UTCOSV refresh
  4. 2026-07-20 17:04 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 14:28 UTCEPSS rescore
  7. 2026-07-16 16:59 UTCEPSS rescore
  8. 2026-07-16 16:59 UTCEPSS rescore
  9. 2026-07-15 16:55 UTCEPSS rescore
  10. 2026-07-13 22:26 UTCEPSS rescore
  11. 2026-07-13 06:10 UTCEPSS rescore
  12. 2026-07-11 08:24 UTCEPSS rescore
  13. 2026-07-09 19:06 UTCEPSS rescore
  14. 2026-07-08 15:11 UTCEPSS rescore
  15. 2026-07-05 02:27 UTCEPSS rescore
  16. 2026-07-03 15:26 UTCOSV refresh
  17. 2026-07-02 16:54 UTCEPSS rescore
  18. 2026-07-01 15:03 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-24 14:02 UTCEPSS rescore
  25. 2026-06-24 14:02 UTCEPSS rescore
Show 26 more
  1. 2026-06-23 21:30 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-19 19:23 UTCEPSS rescore
  4. 2026-06-18 17:50 UTCEPSS rescore
  5. 2026-06-18 17:50 UTCEPSS rescore
  6. 2026-06-17 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-16 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:45 UTCEPSS rescore
  11. 2026-06-15 04:43 UTCOSV refresh
  12. 2026-06-12 23:09 UTCEPSS rescore
  13. 2026-06-10 22:16 UTCEPSS rescore
  14. 2026-06-01 13:49 UTCEPSS rescore
  15. 2026-05-31 22:29 UTCEPSS rescore
  16. 2026-05-31 22:28 UTCEPSS rescore
  17. 2026-05-31 00:14 UTCEPSS rescore
  18. 2026-05-31 00:14 UTCEPSS rescore
  19. 2026-05-29 13:41 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-27 21:28 UTCEG score recompute
  23. 2026-05-27 21:28 UTCVendor advisory
  24. 2026-05-27 21:28 UTCGHSA enrichment
  25. 2026-05-26 07:17 UTCEPSS rescore
  26. 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 high 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 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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