CVE-2025-8738VulnerabilityPublished 8 Aug 2025

CVE-2025-8738: zlt2000 microservices-platform · Information Disclosure

Affects zlt2000 microservices-platformSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Aug 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-25.

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

Affected software

Product	Affected	Fixed in
zlt2000 microservices-platform	Affected =6.0	Fixed in–

AI-suggested

To mitigate CVE-2025-8738 effectively, European organizations should implement the following specific measures: 1) Restrict access to the /actuator endpoint by enforcing network-level controls such as IP whitelisting or VPN-only access, ensuring that only trusted internal users or systems can reach this interface. 2) Implement strong authentication and authorization mechanisms on the actuator endpoints, such as OAuth2 or mutual TLS, to prevent unauthenticated access. 3) Disable or limit the exposure of sensitive actuator endpoints in production environments, enabling only necessary health checks or metrics with minimal information disclosure. 4) Monitor and log all access attempts to the /actuator endpoint to detect and respond to suspicious activity promptly. 5) Conduct thorough code and configuration reviews to ensure that no sensitive data is unnecessarily exposed via actuator endpoints. 6) Stay updated with vendor advisories and apply patches or updates as soon as they become available. 7) Employ Web Application Firewalls (WAFs) with rules tailored to detect and block suspicious requests targeting actuator endpoints. 8) Perform penetration testing focusing on microservices management interfaces to identify and remediate similar exposure risks proactively.

Description

A vulnerability has been found in zlt2000 microservices-platform up to 6.0.0 and classified as problematic. This vulnerability affects unknown code of the file /actuator of the component Spring Actuator Interface. The manipulation leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, the impact of CVE-2025-8738 can be significant depending on the sensitivity of the disclosed information. Unauthorized access to actuator endpoints can reveal internal configuration, environment variables, or system health data, which attackers can leverage to map the internal architecture, identify further vulnerabilities, or craft targeted attacks such as privilege escalation or lateral movement. Organizations relying on the zlt2000 microservices-platform for critical business applications may face increased risk of subsequent breaches or data leaks. Given the microservices architecture's prevalence in modern cloud-native deployments, this vulnerability could affect service availability indirectly if attackers use the disclosed information to disrupt operations. Additionally, disclosure of sensitive operational data may violate GDPR requirements if personal data or security controls are exposed, leading to regulatory and reputational consequences. The fact that exploitation requires no authentication or user interaction increases the threat surface, especially for externally facing services. European organizations with internet-exposed microservices using zlt2000 are particularly at risk, necessitating urgent attention to mitigate potential information leakage and comply with data protection regulations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Aug 2025, 20:32 UTC

Technical details

References

Community reviews

Related threats