CVE-2025-13805VulnerabilityPublished 1 Dec 2025Updated 24 Feb 2026

CVE-2025-13805: nutzam NutzBoot · Deserialization

Affects nutzam NutzBootSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.3Medium

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

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

CVSS:4.0/AV:N/AC:H/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: High
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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 1 Dec 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
Mavenorg.nutz/nutzboot`pkg:maven/org.nutz/nutzboot`Other threats	Affected =2.6.0-SNAPSHOT	Fixed in–

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

AI-suggested

1. Monitor for and apply official patches or updates from the Nutzam project as soon as they become available to address this vulnerability. 2. Restrict network access to the vulnerable LiteRpc-Serializer endpoints by implementing firewall rules or network segmentation to limit exposure to trusted internal networks only. 3. Implement strict input validation and deserialization controls, such as using allowlists for acceptable classes during deserialization or employing safer serialization frameworks that do not allow arbitrary object deserialization. 4. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious serialized payloads targeting the vulnerable endpoint. 5. Conduct code reviews and security testing focused on deserialization logic within the application to identify and remediate similar issues proactively. 6. Monitor security advisories and threat intelligence feeds for exploitation attempts related to CVE-2025-13805 to respond promptly to emerging threats.

Description

A weakness has been identified in nutzam NutzBoot up to 2.6.0-SNAPSHOT. This affects the function getInputStream of the file nutzcloud/nutzcloud-literpc/src/main/java/org/nutz/boot/starter/literpc/impl/endpoint/http/HttpServletRpcEndpoint.java of the component LiteRpc-Serializer. Executing a manipulation can lead to deserialization. The attack may be launched remotely. This attack is characterized by high complexity. The exploitability is reported as difficult. The exploit has been made available to the public and could be used for attacks.

Impact

The vulnerability could allow remote attackers to perform deserialization attacks, potentially leading to unauthorized access to sensitive data or limited information disclosure, given the low confidentiality impact rating. However, there is no direct impact on data integrity or system availability. The high complexity and difficulty of exploitation reduce the likelihood of widespread attacks, but the availability of a public exploit increases risk over time. Organizations using NutzBoot in exposed environments may face targeted attacks aiming to exploit this flaw for reconnaissance or lateral movement. The impact is primarily on confidentiality, with a limited scope due to the specific affected component and version. The lack of authentication requirements means attackers can attempt exploitation without credentials, increasing exposure if the vulnerable service is internet-facing.

Summary

CVE-2025-13805 identifies a deserialization vulnerability in the NutzBoot framework up to version 2.6.0-SNAPSHOT, specifically within the LiteRpc-Serializer component's getInputStream method located in the HttpServletRpcEndpoint.java file. Deserialization vulnerabilities occur when untrusted data is processed by the application’s deserialization routines, potentially allowing attackers to execute arbitrary code or cause denial of service. In this case, the vulnerability arises from insufficient validation or sanitization of serialized input data received remotely, enabling an attacker to craft malicious serialized objects that the system will deserialize. The attack vector is remote network access without requiring authentication or user interaction, but the exploit complexity is high, making exploitation difficult. The CVSS 4.0 base score is 6.3 (medium), reflecting the limited confidentiality impact and no integrity or availability impact. No known active exploits in the wild have been reported, but a public exploit exists, increasing the risk of future attacks. The vulnerability affects Java-based web applications using NutzBoot’s LiteRpc-Serializer, which is used for remote procedure calls over HTTP. This flaw could be leveraged in targeted attacks against organizations using this framework, especially those exposing vulnerable endpoints to untrusted networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:12 UTC

Technical details

References

Community reviews

Related threats