Advisory record · GHSA-f6cj-4h3g-hwq4

APM Server vulnerable to Insertion of Sensitive Information into Log File

CVSS 5.7 MediumEPSS 0.0049 · 43rd percentile

Published by the GitHub Advisory Database at 3 Aug 2024, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/elastic/apm-serverGo<8.14.08.14.0
Identifiers
GHSA-f6cj-4h3g-hwq4 · CVE-2024-37286 · GO-2024-3037
Weakness (CWE)
CWE-532
Published
3 Aug 2024
Updated
7 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

apm-server versions before 8.14.0 log document bodies from partially failed bulk index requests when Elasticsearch returns errors such as unavailable_shards_exception, so sensitive document data can appear in server logs. The source does not say who would need access to those logs. Upgrade to version 8.14.0 or later, as no workaround is listed.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.7 Medium 3.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N CNA (elastic)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 43rd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:54 UTC First seen by agentprime
  2. 31 Oct 2026, 14:54 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.