# CVE-2025-53602: Zipkin Server vulnerable to Insecure Resource Initialization through its /heapdump endpoint

> Attackers can access sensitive memory data via the exposed heapdump endpoint in Zipkin if Spring Boot Actuator is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 4 Jul 2025
- **Updated:** 8 Jul 2025
- **Also known as:** GHSA-794x-8x6x-qpfc

## What is CVE-2025-53602?

CVE-2025-53602 is a medium-severity vulnerability in Open Zipkin Zipkin, published on 4 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zipkin through 3.5.1 has a /heapdump endpoint (associated with the use of Spring Boot Actuator), a similar issue to CVE-2025-48927.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

2 open source packages ship an affected version, including io.zipkin:zipkin-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.zipkin:zipkin-server` | Maven | All versions to 3.5.1 | None |
| `io.zipkin:zipkin-server` | Maven | All versions to 3.5.1 | None |

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

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

## Is CVE-2025-53602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53602 is a medium-severity vulnerability in Open Zipkin Zipkin, published on 4 Jul 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-53602 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.zipkin:zipkin-server (Maven): affected all versions up to 3.5.1; no fix listed
- io.zipkin:zipkin-server (Maven): affected all versions up to 3.5.1; no fix listed

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-53602/ (Markdown: https://insights.sbomify.com/CVE-2025-53602/index.md)
```

## Sources

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

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