CVE-2018-3827

HIGHNVD 8.18.1—

8.1

A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged.

CVSS v3: 8.1
EG Score: 8.1(medium)
EPSS: 53.1%
KEV: Not listed

Published

September 19, 2018

Last Modified

November 21, 2024

References (4)

security@elastichttps://discuss.elastic.co/t/elastic-stack-6-3-0-and-5-6-10-security-update/135777
security@elastichttps://www.elastic.co/community/security
af854a3a-2127-422b-91ae-364da2661108https://discuss.elastic.co/t/elastic-stack-6-3-0-and-5-6-10-security-update/135777
af854a3a-2127-422b-91ae-364da2661108https://www.elastic.co/community/security

Weakness Classification(1)

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

CWE-532Insertion of Sensitive Information into Log File

Data Freshness Timeline

(refreshed 10× in last 7d / 18× 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-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 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:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:38 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:37 UTCEG score recompute
2026-05-23 02:37 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2018-3827?

CVE-2018-3827 is a high vulnerability published on September 19, 2018. A sensitive data disclosure flaw was found in the Elasticsearch repository-azure (formerly elasticsearch-cloud-azure) plugin. When the repository-azure plugin is set to log at TRACE level Azure credentials can be inadvertently logged.

When was CVE-2018-3827 disclosed?

CVE-2018-3827 was first published in the National Vulnerability Database on September 19, 2018, 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-3827 actively exploited?

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

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

CVE-2018-3827 has a CVSS v3 base score of 8.1 (NVD).

How do I remediate CVE-2018-3827?

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

Explore →

Is Your Infrastructure Affected by CVE-2018-3827?

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

Start Free Scan →Browse All CVEs

CVE-2018-3827

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-3827?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)