Elastic Agent
Approved changes feed: RSS · Atom
cpe:2.3:a:elastic:elastic_agent:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Elastic (1d0b8d2a-fd47-5b20-b005-34326f9bd037) |
|---|---|
| Product | Elastic Agent (0e38d000-7e8f-59f6-a99d-6eba20538ec7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/elastic/elastic-agent |
purl2cpe | 2026-06-01 10:15:14.343288 |
pkg:golang/github.com/elastic/elastic-agent |
purl2cpe | 2026-06-01 10:15:14.343289 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-52976 |
vulnerable | 2026-06-03 14:57:31.062630 |
Elastic Agent Inclusion of Functionality from Untrusted Control Sphere
MEDIUM (4.4)
Inclusion of functionality from an untrusted control sphere in Elastic Agent subprocess, osqueryd, allows local attackers to execute arbitrary code via parameter injection.
An attacker requires local access and the ability to modify osqueryd configurations.
Published: 2025-05-01T13:03:58.672Z
Updated: 2025-05-01T15:33:01.380Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-37283 |
vulnerable | 2026-06-03 14:56:06.241071 |
Elastic Agent Insertion of Sensitive Information into Log File
An issue was discovered whereby Elastic Agent will leak secrets from the agent policy elastic-agent.yml only when the log level is configured to debug. By default the log level is set to info, where no leak occurs.
Published: 2024-08-08T23:34:22.070Z
Updated: 2024-08-09T15:34:02.839Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6687 |
vulnerable | 2026-06-03 14:53:58.672980 |
Elastic Agent Insertion of Sensitive Information into Log File
MEDIUM (6.8)
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.
Published: 2023-12-12T18:28:06.423Z
Updated: 2024-08-02T08:35:14.993Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-46669 |
vulnerable | 2026-06-03 14:53:10.320463 |
Elastic Agent / Elastic Endpoint Security local API key disclosure
MEDIUM (6.2)
Exposure of sensitive information to local unauthorized actors in Elastic Agent and Elastic Security Endpoint can lead to loss of confidentiality and impersonation of Endpoint to the Elastic Stack. This issue was identified by Elastic engineers and Elastic has no indication that it is known or has been exploited by malicious actors.
Published: 2025-05-01T12:59:49.101Z
Updated: 2025-05-01T15:33:08.751Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-31421 |
vulnerable | 2026-06-03 14:51:55.726300 |
Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue
MEDIUM (5.9)
It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.
Published: 2023-10-26T03:10:52.684Z
Updated: 2024-08-02T14:53:30.714Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.