CVE-2018-6331

CRITICALNVD 9.89.8—

9.8

Buck parser-cache command loads/saves state using Java serialized object. If the state information is maliciously crafted, deserializing it could lead to code execution. This issue affects Buck versions prior to v2018.06.25.01.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 75.9%
KEV: Not listed

Published

December 31, 2018

Last Modified

May 6, 2025

Advisory Details (1)

Auto-updated May 25, 2026

Patch available. Sources: github_commit.

github_commit Patch Available

commit 8c5500981812 (facebook/buck)

Patch available: facebook/buck v2018.06.25.01 (contains commit 8c5500981812)

https://github.com/facebook/buck/commit/8c5500981812564877bd122c0f8fab48d3528ddf

Weakness Classification(1)

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

CWE-502Deserialization of Untrusted Data

Data Freshness Timeline

(refreshed 9× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-23 02:44 UTCEG score recompute
2026-05-23 02:44 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2018-6331?

CVE-2018-6331 is a critical vulnerability published on December 31, 2018. Buck parser-cache command loads/saves state using Java serialized object. If the state information is maliciously crafted, deserializing it could lead to code execution. This issue affects Buck versions prior to v2018.06.25.01.

When was CVE-2018-6331 disclosed?

CVE-2018-6331 was first published in the National Vulnerability Database on December 31, 2018, with the most recent update on May 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-6331 actively exploited?

CVE-2018-6331 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 75.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-6331?

CVE-2018-6331 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2018-6331?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6331, 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-6331

Explore →

Is Your Infrastructure Affected by CVE-2018-6331?

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

Start Free Scan →Browse All CVEs

CVE-2018-6331

📅 Published

🔄 Last Modified

📋 Advisory Details (1)

commit 8c5500981812 (facebook/buck)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-6331?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

Advisory Details (1)

Frequently asked(5)

Related CVEs(same CWE)