CISA Adds Exploited Synology, LiteLLM, REDCap, Axis Flaws to KEV

CISA added exploited code-execution flaws in Synology DSM, LiteLLM, REDCap and Apache Axis to KEV on Nov 18. Federal deadlines start Nov 21. Steps to take.

CISA added four actively exploited vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog on November 18, covering Synology DiskStation Manager, BerriAI’s LiteLLM, Apache Axis 1.x and the REDCap research data platform. Each one can lead to code execution. Federal agencies must fix three of them by November 21 and the fourth by December 2, but anyone running these products should treat them as urgent.

What happened

CVEProductCVSSFlaw
CVE-2026-90436Apache Axis 1.x9.8Unsafe reflection, unauthenticated code execution
CVE-2026-90817REDCap9.8Code injection via survey routing
CVE-2024-10441Synology DSM9.8Output-escaping flaw, remote code execution
CVE-2026-40217LiteLLM8.8Guardrail sandbox escape, code execution

CISA has not said how widespread the attacks are or who is behind them. Other researchers have filled in part of the picture:

  • Synology: the company had already warned that attackers were hitting DSM-based NAS devices with C3RB3R ransomware. CISA’s listing now names this specific flaw, which was patched in 2024 updates.
  • Apache Axis: Axis 1 is end of life, and Apache does not plan an official fixed 1.x release. Rapid7 first saw the flaw used against a Confluence Data Center server on November 13, and it has also been paired with N-able N-central bugs to install crypto miners.
  • REDCap: exploitation needs no account but does need a valid public survey hash. Safe Security reported an unknown actor planting a web shell and then an XMRig miner disguised as syslog-ng, with persistence through cron and an added SSH key.
  • LiteLLM: Google Threat Intelligence Group reported attackers using the flaw to turn limited-access inference keys into administrator credentials in LLMjacking attacks. Zenity’s honeypots logged 569 requests to the vulnerable endpoint between April 15 and May 24, many guessing default master keys such as sk-1234.

Why it matters

The exposed groups are Synology owners who have not updated, organizations running Confluence Data Center or N-central with legacy Axis exposure, research institutions hosting public REDCap surveys, and teams running LiteLLM gateways. The LiteLLM case stands out because a gateway holds provider keys: Zenity notes that an escape can expose the host’s environment variables, including provider and cloud credentials. A KEV listing means exploitation has been observed somewhere. It does not mean any particular system was compromised.

What to do

The steps below come from vendor and researcher guidance in the sources; where marked, they are our own analysis.

  • Inventory first: find Synology devices, REDCap servers, LiteLLM proxies and any product that bundles Axis 1.x.
  • Synology: update DSM or BeeStation OS to a fixed build. Keeping the admin interface off the internet is our analysis, not vendor guidance in these sources.
  • REDCap: confirm your version and move to 16.0.49, 17.3.10, 17.4.4 or later.
  • Axis: apply Apache’s patch commit or migrate to another SOAP engine such as Axis2/Java, and ask vendors who embed Axis what they are doing. Confluence Data Center admins with the legacy SOAP and XML-RPC remote API enabled should upgrade to 9.2.28 or an unaffected 10.x release.
  • LiteLLM: upgrade to a current release, change the master key if it is a default, keep /guardrails/test_custom_code off the public internet and run the proxy as a non-root user.
  • If a system was exposed, patching will not remove an intruder. Preserve logs first, then look for unfamiliar processes, cron jobs and SSH keys (our analysis, based on the REDCap activity above).

What we still do not know

CISA has not disclosed the scale of the attacks, the victims or the actors. The catalog lists ransomware use as unknown for all four, even though other reports tie the Synology flaw to C3RB3R. Sources also differ on LiteLLM: Zenity says the fix shipped in 1.83.10, while another tracker says 1.83.11, and descriptions vary on whether attackers need the master key or administrator credentials. That is why we suggest simply moving to the latest release.

Sources: CISA alert (Nov 18, 2026, as cited by the reports below); The Hacker News (Nov 19, 2026); GBHackers (Nov 19, 2026); Mallory (Nov 19, 2026); Zenity Labs (Jun 30, 2026).

Leave a Reply

Your email address will not be published. Required fields are marked *