CISA Warns of 4 Exploited Flaws Linked to Ransomware, Cryptomining, and LLMjacking Attacks
The striking point is that CISA added flaws in four different products at once: Apache Axis, Vanderbilt University’s REDCap, BerriAI LiteLLM, and Synology DiskStation Manager (DSM). CISA cited evidence of active exploitation, so the entries cover real-world abuse, not just theoretical risks. For Axis and REDCap, the article describes flaws that can let attackers execute code on a server. Axis exploitation was linked to cryptocurrency miners and to attacks on Confluence servers using the library. A separate REDCap report described a temporary web shell and an XMRig miner. LiteLLM’s flaw was used to turn limited-access inference keys into full administrative credentials in LLMjacking attacks. Synology disclosed its flaw as exploited in ransomware attacks targeting network-attached storage. The article gives more detail about Axis, REDCap, and LiteLLM exploitation than about the Synology attacks. These cases show how one catalog update can involve different products, entry points, and criminal goals. Defenders need to identify which listed products they run and follow the relevant remediation guidance.
Which four software products had flaws added to CISA’s exploited-vulnerability list, and what kinds of attacks are linked to them?
The striking point is that CISA added flaws in four different products at once: Apache Axis, Vanderbilt University’s REDCap, BerriAI LiteLLM, and Synology DiskStation Manager (DSM). CISA cited evidence of active exploitation, so the entries cover real-world abuse, not just theoretical risks.
For Axis and REDCap, the article describes flaws that can let attackers execute code on a server. Axis exploitation was linked to cryptocurrency miners and to attacks on Confluence servers using the library. A separate REDCap report described a temporary web shell and an XMRig miner. LiteLLM’s flaw was used to turn limited-access inference keys into full administrative credentials in LLMjacking attacks.
Synology disclosed its flaw as exploited in ransomware attacks targeting network-attached storage. The article gives more detail about Axis, REDCap, and LiteLLM exploitation than about the Synology attacks. These cases show how one catalog update can involve different products, entry points, and criminal goals. Defenders need to identify which listed products they run and follow the relevant remediation guidance.
How many vulnerabilities were listed, and what range of CVSS severity scores did they receive?
CISA added four vulnerabilities to its Known Exploited Vulnerabilities catalog. Their CVSS scores ranged from 8.8 to 9.8, placing all four at the high end of the scale reported in the article. Three vulnerabilities scored 9.8: the Apache Axis, REDCap, and Synology DSM flaws. The LiteLLM flaw scored 8.8.
The scores describe vulnerability severity, while CISA’s catalog addition reflects a separate point: CISA cited evidence that the flaws were being actively exploited. The article identifies the affected products and gives a short description of each vulnerability, including the potential for attackers to execute code in Axis, REDCap, and LiteLLM.
A high score does not mean every installation has been compromised, and the score alone does not tell an organization whether its systems are exposed. The practical next step is to check whether affected software is in use and follow available vendor guidance. For Axis 1.x, the article notes that the software is end-of-life and recommends migration or using a build with a specified patch applied.
What is CISA’s Known Exploited Vulnerabilities catalog, and what does it mean when a flaw appears on it?
CISA’s Known Exploited Vulnerabilities catalog, or KEV, is a list of security flaws that are known to be exploited. In this article, CISA added four vulnerabilities and explicitly cited evidence of active exploitation. The catalog helps distinguish flaws being used in attacks from flaws that are only known or theoretically exploitable.
The article gives examples of the activity behind the listings. Attackers exploited Apache Axis in activity involving Confluence, used a REDCap flaw to stage a web shell and miner, and abused LiteLLM to gain administrative credentials in LLMjacking attacks. Synology disclosed exploitation of its DSM flaw in ransomware attacks. These are separate incidents and mechanisms, not one coordinated campaign described in the article.
A KEV listing is a warning that the vulnerability has real-world relevance; it does not establish that a particular organization has been attacked. Organizations should check whether they use affected products and consult the relevant vendor guidance. The article specifically recommends replacing end-of-life Axis 1 or applying a build containing a stated patch.
What does remote code execution let an attacker do on a vulnerable server?
Remote code execution, or RCE, means an attacker can make a computer run code they supply from another location. If the vulnerable system is a server, that can give the attacker a way to run commands or programs on it. The article describes several listed flaws as allowing arbitrary code execution.
For example, the Axis flaw could let an unauthenticated remote attacker execute arbitrary code. The REDCap flaw could let an unauthenticated attacker execute code on the server. The article reports that REDCap exploitation involved staging a transient web shell, then using an in-memory loader to retrieve XMRig, a cryptocurrency miner disguised as image files.
The precise impact depends on the vulnerable software and the attacker’s actions; RCE does not automatically mean an attacker has complete control over every connected system. Still, code execution on a server can enable further activity. In the Confluence incident, attackers ran shell commands and scripts, then explored the environment and sought sensitive files and credentials.
How did attackers use these flaws to enable ransomware, cryptomining, and LLMjacking?
The four flaws were linked to several criminal outcomes, but the article does not describe one shared attack chain. Synology said its DSM vulnerability was being exploited in ransomware attacks targeting network-attached storage. The article does not provide further details about those ransomware incidents.
For cryptomining, a report described REDCap attackers staging a temporary web shell and an in-memory loader that retrieved XMRig disguised as image files. Axis exploitation was also linked to deploying cryptocurrency miners. In a separate Confluence incident, attackers ran commands and searched for credentials, tokens, VPN configurations, private keys, and payment card numbers. They later accessed Microsoft 365 using an integration service account.
LiteLLM exploitation served a different purpose: attackers elevated limited-access inference keys into full administrative credentials and established persistence as part of LLMjacking attacks. The reports show how attackers can turn software flaws into access for different objectives. The article describes active exploitation, but it does not say that every affected installation experienced these outcomes.
Why could a flaw in the Apache Axis library put a Confluence server at risk?
A flaw in a software library can put a product at risk when that product uses the library. Rapid7 reported detecting exploitation of the Apache Axis flaw against Atlassian Confluence Data Center. Confluence uses the Axis library as part of its XML-RPC and SOAP APIs, connecting the library vulnerability to the corporate workspace platform.
The key condition was whether Confluence had its Remote API (XML-RPC & SOAP) enabled. Atlassian said this setting was turned off by default for new installations starting with Confluence 3.0. The feature was fully removed in Confluence 10.0. The Axis flaw itself affects Axis 1.x and could allow an unauthenticated remote attacker to execute arbitrary code.
That means the article’s reported Confluence risk was conditional, rather than applying to every Confluence installation. Organizations need to consider both the software version and the relevant setting. The article also says Axis 1 has reached end-of-life and remains unpatched; it recommends migrating to another SOAP engine or using an Axis build with a specified patch applied.
What does it mean for software to be end-of-life, and why might organizations need to replace it rather than wait for a fix?
In general, end-of-life (EOL) means a software product has reached the end of its supported life. It may no longer receive routine updates or fixes. That definition is general background; the article specifically states that Apache Axis 1 has reached EOL and that the flaw remains unpatched.
This matters because organizations using affected software may not be able to rely on a future standard vendor update. The article describes CVE-2026-90436 as an unsafe reflection flaw that could let an unauthenticated remote attacker execute arbitrary code. It says Axis 1.x is affected and notes that the flaw has been exploited, including against Confluence instances with the relevant Remote API enabled.
CISA’s listing and the reported attacks make the decision more urgent for organizations still relying on Axis 1. The article recommends migrating to a different SOAP engine, such as Apache Axis 2/Java. Alternatively, users can use an Axis build with the patch from a July 12, 2026, commit applied. The source does not give a migration deadline.
This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.
Read more in the JupiteX app
Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.
Or read more news on the web