The short version
- The additions. CISA added four CVEs on 18 November, citing evidence of active exploitation. The Apache Axis, REDCap and Synology DSM flaws are rated 9.8; the LiteLLM flaw is rated 8.8. All four allow an attacker to run code remotely.
- Apache Axis. The flaw affects Axis 1.x, a branch that has reached end of life, and has no official fix. The Hacker News reports it is used alongside the 4EverAble2Shell vulnerabilities in N-able N-central to install cryptocurrency miners.
- REDCap. CISA says exploitation requires knowledge of a valid public survey hash. Safe Security reported an unknown attacker staging a web shell, then loading the XMRig miner disguised as image files and hiding it as syslog-ng, with persistence through cron and an added SSH key.
- LiteLLM. A Google Threat Intelligence Group report describes attackers using the flaw to turn limited-access inference keys into full administrative credentials and keep a foothold, in what it calls LLMjacking attacks against organisations in financial services, retail, transport and technology.
- Synology DSM. Synology disclosed the DSM flaw earlier in November, according to The Hacker News, as exploited in ransomware attacks on network attached storage devices that deployed C3RB3R ransomware.
Timeline
| Date | Event |
|---|---|
| 12 July | A commit carrying a patch for the Apache Axis flaw is made; Axis 1.x remains unpatched as it has reached end of life, but users can alternatively use a build of Axis with the patch applied. |
| Late October | Safe Security publishes a report on an attacker using the REDCap flaw to run a miner and establish persistence. |
| November | Synology discloses that the DSM flaw has been exploited in ransomware attacks on its storage devices. |
| 18 November | CISA adds CVE-2026-90436, CVE-2026-90817, CVE-2026-40217 and CVE-2024-10441 to its catalogue of vulnerabilities known to be exploited. |
| 19 November | The Hacker News reports the additions and the exploitation activity recorded behind each flaw. |
What CISA added and why
CISA's 18 November update adds four vulnerabilities to the Known Exploited Vulnerabilities catalogue, a list the agency keeps of flaws with evidence of use in real attacks. The agency names no victims and gives no count of affected systems; it states only that all four are being exploited.
Three of the four are rated 9.8 in severity: an unsafe reflection flaw in Apache Axis, a code injection flaw in REDCap, and an output encoding flaw in Synology DSM. The Axis and REDCap flaws allow an unauthenticated attacker to run code remotely; the Synology flaw allows a remote attacker to do so. The LiteLLM flaw is rated 8.8 and is reached through a specific endpoint, /guardrails/test_custom_code, where rewritten bytecode can be executed.
The Axis case is the awkward one for defenders. Apache Axis 1.x has reached end of life and the flaw has no official patch, so the vendor route is migration to another SOAP engine such as Axis 2 for Java, or a self-built Axis carrying the fix from a 12 July 2026 commit.
The three campaigns behind the listing
The Axis flaw, according to The Hacker News, is being used together with the 4EverAble2Shell vulnerabilities in N-able N-central to place cryptocurrency miners on vulnerable servers. The report does not say how many N-central installations were involved or who is carrying out the attacks.
For REDCap, Safe Security described a chain in which an attacker staged a short-lived web shell, then an in-memory loader that fetched XMRig samples disguised as image files. The miner was named to look like syslog-ng, and persistence came from a cron job and an added SSH key. CISA notes that an attacker also needs a valid public survey hash to reach the vulnerable import path.
The LiteLLM activity is different in aim. Google Threat Intelligence Group reported that attackers took limited-access inference keys and turned them into full administrative credentials, keeping access as part of LLMjacking, the use of an organisation's large language model capacity for the attacker's own purposes. Targets named in the report span North America, South America and Asia Pacific.
Who is exposed
The affected products are Synology NAS devices running DSM, Apache Axis 1.x deployments, REDCap, and LiteLLM. The sources give no figure for how many organisations or devices have been hit in any of the attacks.
CISA frames the catalogue as a prioritisation tool and encourages organisations outside US federal agencies to treat listed flaws as the first patching work. The agency also says a KEV entry requires a CVE identifier, evidence of exploitation and clear mitigation guidance.
What is not known yet
- Who is carrying out each of the three campaigns, and whether the same actor is behind more than one.
- How many organisations or devices have been compromised in the Axis, REDCap and LiteLLM activity.
- Whether data was taken in the LiteLLM intrusions or the Synology ransomware attacks, beyond access and code execution.
- Whether the N-central exploitation involving Axis is ongoing, and how many servers were affected by it.
- Whether working exploits exist for the DSM and REDCap flaws beyond the activity the researchers observed.
What to do
If you run Apache Axis 1.x
- Move to a supported SOAP engine such as Apache Axis 2 for Java, or build Axis with the patch from the 12 July 2026 commit applied.
- Check servers that ran exposed Axis 1.x for cryptocurrency mining processes and for mining traffic, since the flaw is linked to miner deployment.
If you run Synology DSM, REDCap or LiteLLM
- Apply the vendor fix or documented mitigation for the listed flaw in each product you operate.
- On REDCap, review import activity and treat any server that handled public survey imports as a candidate for compromise: look for web shells, XMRig files disguised as images, unexpected cron entries and unknown SSH keys.
- On LiteLLM, replace inference keys and audit for administrative credentials created from limited-access keys, and review who has called the /guardrails/test_custom_code endpoint.
- On Synology NAS devices, look for signs of C3RB3R ransomware before restoring anything from backup.
For everyone else
- Inventory any internet-facing instance of these four products in your estate and record its version.
- Prioritise flaws already known to be exploited over lower-risk findings when planning patching work.
- Check hosts for signs of compromise as well as patching, because exploitation may have happened before the fix was available.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.