VulnerabilityPublished 16 Feb 2026Updated 23 Feb 2026

CVE-2026-2555: JeecgBoot · Deserialization

Affects JeecgBootSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 4.0 base score

2.3Low

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:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

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

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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Feb 2026
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 26 Oct 2026.

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
JeecgBoot	Affected =3.9.1	Fixed in–

AI-suggested

Organizations should immediately audit their use of JeecgBoot 3.9.1 and identify any deployments of the vulnerable importDocumentFromZip function. Until a vendor patch is available, implement strict input validation and sanitization on all data processed by this function to prevent malicious serialized objects from being deserialized. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious deserialization payloads. Restrict network access to the affected application components, limiting exposure to trusted users and systems only. Monitor logs for unusual deserialization activity or errors indicative of exploitation attempts. Consider upgrading to a later version of JeecgBoot once a fix is released. Additionally, conduct code reviews to identify and remediate other unsafe deserialization patterns in the codebase. Educate developers on secure coding practices related to serialization and deserialization.

Description

A weakness has been identified in JeecgBoot 3.9.1. This vulnerability affects the function importDocumentFromZip of the file org/jeecg/modules/airag/llm/controller/AiragKnowledgeController.java of the component Retrieval-Augmented Generation. Executing a manipulation can lead to deserialization. The attack can be launched remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The project was informed of the problem early through an issue report but has not responded yet.

Impact

If exploited, this vulnerability could allow remote attackers to manipulate the deserialization process, potentially leading to arbitrary code execution or denial of service on affected systems. Although the CVSS score is low due to the high complexity and limited impact, successful exploitation could compromise the confidentiality, integrity, and availability of enterprise applications built on JeecgBoot 3.9.1. Organizations relying on this platform for critical business functions may face operational disruptions or data breaches. The absence of a patch increases the window of exposure. However, the difficulty of exploitation and lack of known active attacks reduce immediate risk. Still, attackers with sufficient skill could leverage this vulnerability in targeted attacks, especially in environments where JeecgBoot is widely deployed.

Summary

CVE-2026-2555 is a security vulnerability in JeecgBoot version 3.9.1, a rapid development platform widely used for enterprise applications. The vulnerability resides in the importDocumentFromZip function within the AiragKnowledgeController.java file, part of the Retrieval-Augmented Generation component. This function improperly handles deserialization of data, allowing an attacker to supply crafted input that triggers unsafe deserialization. Deserialization vulnerabilities can lead to remote code execution, privilege escalation, or denial of service if malicious serialized objects are processed without proper validation. However, this particular vulnerability is noted to be highly complex to exploit, requiring a low privilege level but no user interaction. The CVSS 4.0 vector indicates network attack vector, high attack complexity, no privileges required, no user interaction, and low impact on confidentiality, integrity, and availability. The vendor has been notified but has not yet issued a patch or response. No known exploits have been observed in the wild, suggesting limited current risk but potential future threat if weaponized. The vulnerability highlights the importance of secure deserialization practices and input validation in Java-based web applications.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:21 UTC

Technical details

References

Community reviews

Related threats