VulnerabilityPublished 14 Dec 2025Updated 24 Feb 2026

CVE-2025-14674: aizuda snail-job · Injection

Affects aizuda snail-jobSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.7.0 : update aizuda snail-job when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 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 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.7.0

CVSS:4.0/AV:N/AC:L/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: Low
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: 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: 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 14 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 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 or the CVSS exploit maturity 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
Mavencom.aizuda/snail-job`pkg:maven/com.aizuda/snail-job`Other threats	Affected 1.0 – 1.6.0 7 affected builds	Fixed in–

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

AI-suggested

To mitigate CVE-2025-14674, organizations should upgrade aizuda snail-job to version 1.7.0-beta1 or later, which contains the official patch addressing the injection flaw. Until upgrading is possible, restrict network access to the snail-job service to trusted hosts only, using firewall rules or network segmentation to limit exposure. Review and audit any custom expressions or scripts evaluated by QLExpressEngine for unsafe input or injection vectors. Implement strict input validation and sanitization on any user-supplied data that may reach the expression engine. Monitor logs for unusual or suspicious expression evaluation activity that could indicate exploitation attempts. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block injection payloads targeting the expression engine. Regularly update and patch related dependencies and maintain an inventory of affected versions to ensure timely remediation. Finally, conduct security awareness training for developers and administrators on secure coding practices related to expression evaluation and injection prevention.

Description

A vulnerability was found in aizuda snail-job up to 1.6.0. Affected by this vulnerability is the function QLExpressEngine.doEval of the file snail-job-common/snail-job-common-core/src/main/java/com/aizuda/snailjob/common/core/expression/strategy/QLExpressEngine.java. The manipulation results in injection. The attack can be launched remotely. Upgrading to version 1.7.0-beta1 addresses this issue. The patch is identified as 978f316c38b3d68bb74d2489b5e5f721f6675e86. The affected component should be upgraded.

Impact

The injection vulnerability in aizuda snail-job could allow remote attackers to execute arbitrary expressions within the QLExpressEngine context, potentially leading to unauthorized code execution, data manipulation, or disruption of scheduled workflows. This can impact the confidentiality of sensitive data processed by the system, the integrity of job execution results, and the availability of critical automation tasks. Organizations relying on snail-job for business-critical workflows may experience operational disruptions, data corruption, or unauthorized access to internal systems. Although the impact is rated as low to medium on confidentiality, integrity, and availability, the ease of remote exploitation without authentication increases the risk profile. The absence of known exploits reduces immediate threat but does not eliminate the risk of future exploitation. The vulnerability could be leveraged as a foothold for further attacks within a compromised environment, especially in complex enterprise deployments.

Summary

CVE-2025-14674 is an injection vulnerability identified in the aizuda snail-job workflow scheduling system, specifically in the QLExpressEngine.doEval function within the snail-job-common-core module. The vulnerability affects all versions up to 1.6.0 and allows an attacker to remotely inject malicious input that is evaluated by the QLExpressEngine, potentially leading to unauthorized code execution or manipulation of the system's behavior. The injection occurs due to insufficient input validation or sanitization in the expression evaluation logic, enabling crafted payloads to alter the intended execution flow. Exploitation does not require user interaction or elevated privileges, making it accessible to remote unauthenticated attackers. The vulnerability was patched in version 1.7.0-beta1, with the fix identified by commit 978f316c38b3d68bb74d2489b5e5f721f6675e86. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and low impacts on confidentiality, integrity, and availability. No known exploits have been reported in the wild as of the publication date. This vulnerability is significant for organizations using snail-job for job scheduling and workflow automation, as it could allow attackers to inject and execute arbitrary expressions, potentially disrupting operations or leaking sensitive information.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 23:01 UTC

Technical details

References

Community reviews

Related threats