CVE-2025-53602VulnerabilityPublished 4 Jul 2025Updated 8 Jul 2025

CVE-2025-53602: Zipkin · Insecure Default

Affects ZipkinSource CVE Database V5

Mentioned vulnerabilities

CVE-2025-48927

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.5.2 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.5.2

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade openzipkin/zipkin to 3.5.2.

Affected software

Product	Affected	Fixed in
GitHubopenzipkin/zipkin`pkg:github/openzipkin/zipkin`Other threats	Affected <3.5.2	Fixed in 3.5.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations using Zipkin should immediately audit their Spring Boot Actuator configurations to ensure that sensitive endpoints like /heapdump are not exposed publicly or are secured behind strong authentication and network access controls. Specifically, disable the /heapdump endpoint if not required, or restrict its access to trusted internal networks only. Implement network-level protections such as firewalls and API gateways to block unauthorized access to actuator endpoints. Monitor logs and network traffic for any unusual access patterns to these endpoints. Additionally, conduct regular security reviews of all diagnostic and management endpoints in microservices environments to prevent similar exposures. Employ secrets management best practices to minimize sensitive data stored in memory and consider runtime application self-protection (RASP) tools to detect anomalous access attempts.

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.

Impact

For European organizations, the exposure of heap dumps via the /heapdump endpoint in Zipkin can lead to unauthorized disclosure of sensitive runtime information. This can include environment variables, credentials, tokens, or other secrets stored in memory, which attackers could use to escalate privileges or move laterally within networks. Organizations relying on Zipkin for distributed tracing in microservices architectures may inadvertently expose internal application details, increasing the risk of targeted attacks. The impact is particularly significant for sectors with stringent data protection requirements such as finance, healthcare, and critical infrastructure, where leakage of sensitive information can lead to regulatory penalties under GDPR and damage to reputation. Although the vulnerability does not directly allow code execution or denial of service, the confidentiality breach can be a stepping stone for more severe attacks. Given the remote and unauthenticated nature of the exploit, attackers can scan for exposed endpoints and retrieve heap dumps without needing credentials or user interaction, increasing the risk of automated exploitation attempts.

CWE-1188Initialization of a Resource with an Insecure Default (opens in a new tab)
Base weakness
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2025, 21:25 UTC

WeaknessesCWE-1188

Technical details

References

Community reviews

Related threats