Beats Insertion of Sensitive Information into Log File
Description
An 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.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
github.com/elastic/beats/v7Go | >= 7.0.0, < 7.17.16 | 7.17.16 |
github.com/elastic/beatsGo | >= 8.0.0, < 8.11.3 | 8.11.3 |
github.com/elastic/beatsGo | >= 7.0.0, < 7.17.16 | 7.17.16 |
Affected products
1Patches
19bd7de84ab9cRemove event fields from error log. (#37330) (#37348)
1 file changed · +0 −1
libbeat/processors/script/javascript/session.go+0 −1 modified@@ -210,7 +210,6 @@ func (s *session) runProcessFunc(b *beat.Event) (out *beat.Event, err error) { if r := recover(); r != nil { s.log.Errorw("The javascript processor caused an unexpected panic "+ "while processing an event. Recovering, but please report this.", - "event", mapstr.M{"original": b.Fields.String()}, "panic", r, zap.Stack("stack")) if !s.evt.IsCancelled() {
Vulnerability mechanics
Generated by null/stub on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4News mentions
0No linked articles in our index yet.