Threat intel5 min read
CISA adds exploited Synology, LiteLLM, Apache Axis and REDCap flaws to KEV
Four vulnerabilities joined CISA's exploited list on 18 November, three of them allowing unauthenticated code execution. US agencies must fix the Synology, Axis and REDCap flaws by 21 November.
4Tify Team

On 18 November 2026 the US Cybersecurity and Infrastructure Security Agency added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. Three of them allow an unauthenticated attacker to run code on the target. US federal agencies have until 21 November to deal with the Synology, Axis and REDCap flaws, and until 2 December for LiteLLM.
What happened
The CISA alert lists these entries:
- CVE-2024-10441, Synology DiskStation Manager (DSM) and BeeStation OS, CVSS 9.8
- CVE-2026-40217, BerriAI LiteLLM, CVSS 8.8
- CVE-2026-90436, Apache Axis 1.x, CVSS 9.8
- CVE-2026-90817, Vanderbilt University REDCap, CVSS 9.8
For the Synology, Axis and REDCap entries, CISA also flags forensic triage. Under its new directive BOD 26-04, agencies have to check whether a system was compromised before the patch went on, not only install it.
The four products have little in common. One is a storage appliance, one is a gateway for AI models, one is an old Java library for SOAP web services, and one is a research survey platform. The KEV listing confirms that each flaw is being exploited. It does not say the same attackers are behind all four.
Who is affected
Synology DSM. The bug sits in a system plugin daemon and was first shown at Pwn2Own 2024. Synology fixed it in November 2024. The patched builds are DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 and 7.1.1-42962-7, plus BeeStation OS 1.1-65374. NAS boxes that missed those updates are now being hit in ransomware attacks that deploy C3RB3R.
LiteLLM. The /guardrails/test_custom_code endpoint ran user-supplied Python inside a home-made sandbox, and bytecode tricks can break out of it. Code then runs inside the proxy process, which is root in the default Docker image. Versions from 1.81.8 are affected. In default setups the endpoint needs a proxy-admin credential. Attackers have used the flaw to turn limited inference keys into full admin access and to stay on the gateway, a pattern known as LLMjacking.
Apache Axis 1.x. Every release up to 1.4 is affected, and the project is end-of-life. A crafted SOAP fault can make Axis load and instantiate a class the attacker names. This happens before any per-service handler runs, so authentication set on a service does not stop it. Apache does not plan a fixed 1.x release. Axis is often bundled inside other products. It has been exploited against Atlassian Confluence Data Center, where the attacker went on to use the application's own database credentials. Confluence is only exposed when the "Remote API (XML-RPC & SOAP)" setting is enabled.
REDCap. Versions from 13.3.0 are affected. The fixed releases are 16.0.49, 17.3.10 and 17.4.4. An attacker without an account can reach a controller route from a public survey and pass a crafted file path during data import. They need a valid public survey hash, which any institution running public surveys hands out by design. In one reported case attackers dropped a web shell and then a cryptominer.
What to do now
- Synology: check the DSM build under Control Panel > Info Center and install the latest update for your model. Take DSM management off the internet and keep a backup that is offline or off-site.
- LiteLLM: upgrade to 1.83.11 or later, as the GitHub advisory recommends. Until then, block
POST /guardrails/test_custom_codeat your reverse proxy. Rotate admin and virtual keys, and review which keys were created recently. - Apache Axis: search your Java applications and vendor products for
axis-1.4.jaror older. Move to another SOAP engine, or follow the vendor's fix for products that bundle Axis. For Confluence Data Center 9.2 that means 9.2.28 or a 10.x release. Turn off the remote API if nobody uses it. - REDCap: move to 16.0.49, 17.3.10, 17.4.4 or a later release.
- For all four: patching closes the hole but tells you nothing about the weeks before. Look for unknown admin accounts, new scheduled tasks or cron jobs, added SSH keys and unusual outbound traffic, starting with anything exposed to the internet.
The hard part with lists like this is knowing where the software runs, especially a library like Axis that hides inside other products. Our vulnerability scanning service maps internet-facing hosts and the versions they expose, so a KEV entry turns into a short list of systems to fix.