An issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at…
Historical advisory recorded 24 Oct 2026 23:17:11 UTC. Read the latest advisory.
nvd · CVE-2023-49922
PublishedAn issue was discovered by Elastic whereby Beats and Elastic Agent would log a raw event in its own logs at the WARN or ERROR level if ingesting that event to Elasticsearch failed with any 4xx HTTP status code except 409 or 429. Depending on the nature of the event that Beats or Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the Beats or Elastic Agent logs. Elastic has released 8.11.3 and 7.17.16 that prevents this issue by limiting these types of logs to DEBUG level logging, which is disabled by default.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2023-49922
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Modified
Weakness classifications: CWE-532
Original publisher date fields
published: 2023-12-12T19:15:08.307
lastModified: 2026-06-17T06:36:42.480
1 source CPE criteria · context only
- cpe:2.3:a:elastic:elastic_beats:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON