Exposure of Sensitive Information in Elastic APM .NET AgentGHSA-hx93-gc73-5rpr
LOWFix: elastic/apm-agent-dotnet#1286GHSA-hx93-gc73-5rpr is a low-severity (CVSS 2.1) Information Exposure vulnerability in Elastic.Apm. A fix is available for Elastic.Apm — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hx93-gc73-5rpr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
Elastic.ApmReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
The Elastic APM .NET Agent can leak sensitive HTTP header information when logging the details during an application error. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application error it is possible the headers will not be sanitized before being sent.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Elastic.Apm | all versions | 1.10.0dotnet add package Elastic.Apm --version 1.10.0 |
Affected Products
apm .net agentelasticDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Elastic.Apm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Elastic.Apm to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hx93-gc73-5rpr is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-hx93-gc73-5rpr in your dependencies?
Find it across NuGet, including transitive dependencies.