CVE-2023-6687
Elastic Agent vulnerability analysis and mitigation

An issue was discovered by Elastic whereby 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 Elastic Agent attempted to ingest, this could lead to the insertion of sensitive or private information in the 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.


SourceNVD

Related Elastic Agent vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2025-68156HIGH7.5
  • Amazon CloudWatch AgentAmazon CloudWatch Agent
  • rke2-runtime-1.31
NoYesDec 16, 2025
CVE-2025-68383MEDIUM6.5
  • FilebeatFilebeat
  • github.com/elastic/beats/v7
NoYesDec 18, 2025
CVE-2025-10543MEDIUM6.3
  • InfluxDBInfluxDB
  • agentbeat-fips
NoYesDec 02, 2025
CVE-2025-68388MEDIUM5.3
  • NixOSNixOS
  • packetbeat
NoYesDec 18, 2025
CVE-2025-58181MEDIUM5.3
  • cAdvisorcAdvisor
  • grype
NoYesNov 19, 2025

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management