News Vulnerabilities & Zero-Days

CISA KEV Adds Apache Axis and LiteLLM Flaws as Rapid7 Details Confluence Intrusion

CISA added four flaws to its Known Exploited Vulnerabilities catalog, covering Apache Axis, BerriAI LiteLLM, Vanderbilt REDCap and Synology DSM. Rapid7 says it saw the Axis flaw used against Atlassian Confluence Data Center, and Google's threat intelligence team ties the LiteLLM flaw to LLMjacking.

Published
Line art of a catalog card stack with a warning mark, beside the headline about CISA adding Apache Axis and LiteLLM flaws to KEV

Key takeaways

  • CISA added flaws in Apache Axis, BerriAI LiteLLM, Vanderbilt REDCap and Synology DSM to the KEV catalog.
  • The Axis flaw sits in an end-of-life library, and Rapid7 says Apache does not plan a fixed release for that line.
  • Rapid7 detected exploitation against Confluence Data Center, which it says is vulnerable only when the Remote API (XML-RPC & SOAP) setting is enabled.
  • Google's threat intelligence team says the LiteLLM flaw turned limited Virtual Keys into full admin credentials in LLMjacking intrusions.
  • Inventory embedded Axis copies and lock down access to AI gateways.

CISA has added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. Two of them matter directly to application security teams: an unsafe reflection flaw in Apache Axis (CVE-2026-90436) and an unprotected alternate channel flaw in BerriAI LiteLLM (CVE-2026-40217). The other two are a code injection flaw in Vanderbilt REDCap (CVE-2026-90817) and an output encoding flaw in Synology DiskStation Manager (CVE-2024-10441).

Axis: an end-of-life library inside shipping products #

Rapid7 describes CVE-2026-90436 as an unsafe reflection flaw (CWE-470) in the original, legacy Apache Axis line that allows unauthenticated remote code execution. That line is end-of-life. According to Rapid7, Apache does not plan a fixed release for it and recommends moving to another SOAP engine such as Axis 2, or applying a patch.

The library is still embedded in commercial software. Rapid7 names Atlassian Confluence Data Center and N-able N-central as affected, and says both need a non-default configuration to be vulnerable. For Confluence, that is the 'Remote API (XML-RPC & SOAP)' setting, which Rapid7 says has been off by default on new installations for a long time and is removed entirely in the newest major line. Atlassian Cloud is unaffected.

Rapid7 says its managed detection team observed exploitation against Confluence Data Center in a customer environment one day after a proof of concept targeting N-central was published. N-able reported exploitation against N-central the same day, and a Metasploit module for Confluence followed.

In the intrusion Rapid7 investigated, the attacker ran hundreds of commands, used Confluence's own database credentials to query page content and attachments, and searched for credentials and payment card numbers. An AS-REP roasting attempt against a domain controller failed. Rapid7 says the attacker queried a cloud data warehouse with a service account about four hours after the first exploit request, and signed in to Microsoft 365 over legacy authentication about twelve hours after it.

LiteLLM: the gateway that holds the keys #

Google's Threat Intelligence Group reports that a threat actor exploited CVE-2026-40217 during LLMjacking intrusions. Google describes the flaw as a sandbox escape in LiteLLM that lets an attacker elevate limited-access inference keys, called Virtual Keys, into full administrative credentials. An AI gateway sits in front of every model provider it proxies, so an admin credential there is a credential for all of them.

What to do #

  • Inventory where the legacy Axis library is bundled, including inside vendor products.
  • On Confluence Data Center, check whether 'Remote API (XML-RPC & SOAP)' is enabled. Rapid7's guidance is to upgrade to a fixed release or turn the setting off.
  • On N-central, apply N-able's hotfix, which Rapid7 says disables the 'Legacy API' feature.
  • Restrict who can reach your LiteLLM proxy, and review Virtual Key and admin key activity.
  • If a Confluence instance was exposed with the setting on, treat its database credentials and any secrets stored in pages as compromised.

CISA's remediation deadlines bind only Federal Civilian Executive Branch agencies, but the agency encourages every organization to prioritize KEV entries.

Sources

  1. CISA Adds Four Known Exploited Vulnerabilities to Catalog, CISA
  2. Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited, Rapid7
  3. GTIG AI Threat Tracker: Agentic Threat Activity Crosses a Significant Threshold, Google Cloud (Google Threat Intelligence Group)

Questions this raises

Is every Confluence Data Center instance vulnerable to the Axis flaw?
No. Rapid7 says Confluence Data Center is vulnerable only when the 'Remote API (XML-RPC & SOAP)' setting is enabled, which is not the default on new installations. Atlassian Cloud is unaffected.
Will Apache fix the legacy Axis line?
According to Rapid7, the affected Axis line is end-of-life and Apache does not plan a fixed release for it. Apache recommends moving to another SOAP engine such as Axis 2, or applying a patch.
Why does the LiteLLM flaw matter to appsec teams?
LiteLLM is a gateway in front of model providers. Google's Threat Intelligence Group reports that attackers used the flaw to elevate limited inference keys into full administrative credentials, which exposes every provider key the gateway manages.

CISA KEVapache-axisLiteLLM