CVE-2025-5525VulnerabilityPublished 3 Jun 2025

CVE-2025-5525: Jrohy trojan · OS Command Injection

Affects Jrohy trojanSource 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: 2.7% chance of exploitation in 30 days – higher than 86% 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:L/VA:L/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
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: 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: 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 3 Jun 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
Gogithub.com/ainrm/Jrohy-trojan`pkg:golang/github.com/ainrm/Jrohy-trojan`Other threats	Affected =2.15.0 =2.15.1 =2.15.2 =2.15.3	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. Immediate identification and removal of the Jrohy trojan from all affected systems using updated anti-malware tools and endpoint detection and response (EDR) solutions. 2. Since no official patches are currently linked, organizations should monitor vendor advisories for updates or patches addressing this vulnerability and apply them promptly once available. 3. Implement network segmentation and strict firewall rules to limit inbound and lateral network traffic, reducing the attack surface for remote exploitation. 4. Employ application whitelisting and restrict execution of unauthorized binaries or scripts, which can prevent the trojan from executing injected commands. 5. Enhance monitoring for unusual command execution patterns or suspicious activity related to the LogChan function or similar processes. 6. Conduct regular threat hunting exercises focused on detecting Jrohy trojan indicators and command injection attempts. 7. Educate security teams on the specifics of this vulnerability and the complexity of its exploitation to improve incident response readiness. 8. Harden Linux systems by applying security best practices, including minimizing exposed services and using mandatory access controls (e.g., SELinux, AppArmor) to limit process capabilities.

Description

A vulnerability was found in Jrohy trojan up to 2.15.3. It has been declared as critical. This vulnerability affects the function LogChan of the file trojan/util/linux.go. The manipulation of the argument c leads to os command injection. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Impact

For European organizations, the impact of CVE-2025-5525 depends largely on the presence and use of the Jrohy trojan within their environments. Since this vulnerability allows remote OS command injection, it could enable attackers to execute arbitrary commands, potentially leading to further compromise, data exfiltration, or disruption of services. However, the medium CVSS score and high attack complexity suggest that widespread exploitation may be limited to targeted attacks against high-value or sensitive systems. Organizations involved in critical infrastructure, government, finance, or technology sectors could face increased risks if targeted by threat actors leveraging this vulnerability. The presence of the trojan itself indicates prior compromise, so this vulnerability may be exploited to escalate control or maintain persistence. The low impact on confidentiality, integrity, and availability indicates that while exploitation is serious, it may not lead to catastrophic system failures or data breaches on its own, but could facilitate further malicious activities. European entities with inadequate endpoint detection or incident response capabilities may be more vulnerable to exploitation and subsequent damage.

References

Community reviews

Loading reviews…