# CVE-2024-11994: APM Server Insertion of Sensitive Information into Log File

> Attackers can read sensitive document body data from APM Server error logs generated during failed bulk index requests.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2025
- **Updated:** 1 May 2025
- **Also known as:** GHSA-p93v-94fp-qv28

## What is CVE-2024-11994?

CVE-2024-11994 is a medium-severity vulnerability in Elastic APM Server, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

APM server logs could contain parts of the document body from a partially failed bulk index request. Depending on the nature of the document, this could disclose sensitive information in APM Server error logs.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-11994?


## How do I fix CVE-2024-11994?

No fix has been published for CVE-2024-11994 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11994 being exploited?

There is no known exploitation of CVE-2024-11994 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11994 and fix it if it is affected.

What it is: CVE-2024-11994 is a medium-severity vulnerability in Elastic APM Server, published on 1 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11994 in the wild and no public exploit code.

Affected product: Elastic APM Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11994/ (Markdown: https://insights.sbomify.com/CVE-2024-11994/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11994
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11994
- OSV: https://osv.dev/vulnerability/CVE-2024-11994

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11994/
Summaries are generated and may contain mistakes; the official description above is the record.