# CVE-2025-57564: Other in n/a

> Unauthenticated attackers can inject arbitrary log entries into CubeAPM, causing log poisoning, alert obfuscation, and potential performance degradation.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-g6hp-qhwq-p766

## What is CVE-2025-57564?

CVE-2025-57564 is a high-severity vulnerability in n/a, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CubeAPM nightly-2025-08-01-1 allow unauthenticated attackers to inject arbitrary log entries into production systems via the /api/logs/insert/elasticsearch/_bulk endpoint. This endpoint accepts bulk log data without requiring authentication or input validation, allowing remote attackers to perform unauthorized log injection. Exploitation may lead to false log entries, log poisoning, alert obfuscation, and potential performance degradation of the observability pipeline. The issue is present in the core CubeAPM platform and is not limited to specific deployment configurations.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2025-57564?


## How do I fix CVE-2025-57564?

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

## Is CVE-2025-57564 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57564 and fix it if it is affected.

What it is: CVE-2025-57564 is a high-severity vulnerability in n/a, published on 7 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-57564 in the wild and no public exploit code.

Affected product: n/a. 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-2025-57564/ (Markdown: https://insights.sbomify.com/CVE-2025-57564/index.md)
```

## Sources

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

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