CISA adds LiteLLM, REDCap, Apache Axis and Synology DSM as exploited; the records are 12 to 609 days old
CISA added LiteLLM, REDCap, Apache Axis and Synology DSM flaws to its exploited list on 18 November 2026. Their CVE records were published 222, 59, 12 and 609 days earlier (derived), and who exploits them is not stated.
By Parminder Kumar Sharma · LinkedIn · · 22 min read
Four CVE records, 12 to 609 days old, reached CISA's exploited list on one day (derived)
On Wednesday 18 November 2026 CISA added four flaws to its Known Exploited Vulnerabilities (KEV) catalogue: BerriAI's LiteLLM (CVE-2026-40217), Vanderbilt University's REDCap (CVE-2026-90817), Apache Axis (CVE-2026-90436) and Synology DiskStation Manager (CVE-2024-10441). The catalogue file this site read was released at 19:17 UTC that day and held 1,786 entries. The four CVE records had been public for 609, 222, 59 and 12 days (derived: each record's publication date to 18 November). The spread is the checkable fact. The same list names a flaw whose record is 12 days old and one whose record is 609 days old, and the one aimed at AI infrastructure, a guardrail test endpoint in the LiteLLM gateway, sits at 222 days.
Table 1 puts the four side by side. The method follows brief 738, the earlier KEV brief: catalogue entry, CVE record and vendor page read in full, every interval worked out here and labelled derived, nothing resolved where pages differ.
Table 1. The four catalogue entries of 18 November 2026 and the age of each CVE record. Day counts and the due date spans are derived; the other fields are as the entry and the record print them.
| Flaw | CVE record published, and by whom | Days to the 18 Nov entry (derived) | Entry due date |
|---|---|---|---|
| Synology DiskStation Manager, CVE-2024-10441 | 19 Mar 2025, Synology | 609 | 2026-11-21 (3 days) |
| BerriAI LiteLLM, CVE-2026-40217 | 10 Apr 2026, MITRE | 222 | 2026-12-02 (14 days) |
| Vanderbilt University REDCap, CVE-2026-90817 | 20 Sep 2026, Securifera | 59 | 2026-11-21 (3 days) |
| Apache Axis, CVE-2026-90436 | 6 Nov 2026, Apache | 12 | 2026-11-21 (3 days) |
Here is what the entries and the records do not establish:
- Who is exploiting any of the four, how many systems, since when, and what they did. Each entry says the flaw is in the catalogue and prints knownRansomwareCampaignUse as "Unknown". No saved page names an actor.
- What evidence CISA used. No entry states it.
- That the four are connected. No saved page links them to each other or to any group, and this brief does not.
- How many LiteLLM, REDCap, Axis or Synology installs are exposed. No saved page counts them.
- Whether the LiteLLM exploitation needed authentication. The advisory that the CVE record cites says the request must be authenticated. The catalogue entry says nothing on the point.
Four clocks, to scale, and why a record's age is not an exposure time
Diagram 1 draws each record's age on one linear time scale. The bars run from the CVE record to the catalogue entry, the red tips run from the entry to its due date, and the dashed band under each bar is the part the pages leave blank: the catalogue prints a date added, not a date exploitation began.
A record's age is also not the time a flaw was unfixed or unknown. Two of the four were public before their records. X41 D-Sec's LiteLLM advisory is dated 8 April 2026, two days before the CVE record (derived), which makes it 224 days before the entry (derived). Synology's advisory SA-24:20 was first released on 5 November 2024 according to brief 565, which read the advisory page on 2 November 2026; that is 743 days before the entry (derived), and 134 days before the CVE record, as that brief states. REDCap's and Axis's records are the first public pages this site saw for those flaws.
The due dates are a second spread. Three entries carry a due date 3 days after they were added, 2026-11-21, which is a Saturday (derived). LiteLLM's carries 14 days, 2026-12-02, a Wednesday. The next sections take the four in turn, LiteLLM first because its pages disagree most.
LiteLLM: a public advisory said patched versions were TBD, and then the project published its own
What the entry says. The catalogue entry says BerriAI LiteLLM "contains an unprotected alternate channel vulnerability that could allow remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI". It names the vendor as BerriAI and the product as LiteLLM, and does not mention authentication. What the CVE record says. The record was published on 10 April 2026 at 13:43 UTC by MITRE, not by the vendor, through a request form (the record's generator field reads "CVE-Request-form"). Its description is one sentence: "LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI." Its affected list names vendor BerriAI and product LiteLLM, with a default status of unknown, and gives the one affected version as a container image digest, not a release number. Its only reference is X41 D-Sec's advisory. The record carries a CVSS 3.1 score of 8.8, HIGH, with privileges required LOW, and the weakness class CWE-420.
What the advisory says. X41 D-Sec's advisory X41-2026-001, dated 8 April 2026, is titled "Guardrail Sandbox Escape in LiteLLM". It prints severity High, CVSS 4.0 score 8.7, CWE-94, the vector "Authenticated HTTP API request", confirmed affected version "main-latest" with an image digest, "Confirmed Patched Versions: TBD", and "CVE: TBD". It describes an endpoint that lets authenticated users submit Python code for guardrail testing, filters that code with regular expressions, and says the filter "can be bypassed using bytecode rewriting techniques". It adds that the attacker gets commands as the user the LiteLLM process runs as, which is "root in the default Docker image". Its workarounds say "No vendor patch is available at the time of publication" and, for the endpoint, "requires authentication with the master key". X41 sells penetration testing and source code audits; the advisory is its own finding. The advisory also prints a proof of concept and a six step description of the bypass. This brief reproduces neither.
X41's account of the disclosure. The advisory's timeline, which is X41's account and the only one this site saved, runs from "Issue identified" on 13 February 2026 to publication on 8 April: 54 days (derived). It says LiteLLM acknowledged the report on 18 February "giving an initial ETA for fix: by the end of next week", 49 days before publication (derived). It then lists follow-ups on 20, 24 and 25 March, one of which met a delivery failure for a technical contact's address, acknowledgements on 26 March and 6 April, and a request on 6 April to submit through the project's GitHub security reporting page. On 7 April X41 and a distributions mailing list noted that the embargo ran out on 8 April, and the advisory went public that day. The timeline writes the vendor as "Berry" in its later entries. The project's own account of these months is not on any page this site saved for this brief.
What this site read earlier. The entry's notes field points to a GitHub security advisory in LiteLLM's repository, GHSA-wxxx-gvqv-xp7p. This site did not re-read it for this brief, but brief 346 read LiteLLM's repository advisory list on 15 October 2026 and the saved copy holds that advisory, so what follows is that earlier reading, attributed and not re-checked. The advisory lists CVE-2026-40217, was published on 7 May 2026, which is 27 days after the CVE record (derived), and was last updated on 30 June. It is titled "Sandbox escape in custom-code guardrail", severity medium, and says that "Reaching the endpoint requires a proxy-admin credential" in default configurations. It prints two fixed versions: its text says the flaw is fixed in 1.83.11 and that the hand-rolled sandbox was replaced, its structured range says patched from 1.83.10 and the vulnerable range is 1.81.8 up to but not including 1.83.10, and its reference line names the v1.83.10-stable release. Brief 346's copy of PyPI's release list gives upload times of 19 April 2026 for 1.83.10 and 22 April for 1.83.11, which are 9 and 12 days after the CVE record and 213 and 210 days before the entry (derived). The same list gives 17 April for 1.83.9, the release that brief 346 is about; it fixes two different flaws, and it falls inside this advisory's vulnerable range, so it is not a fix for this one. The advisory page in the entry's notes is therefore the answer to "which release", in two versions that LiteLLM's own text does not reconcile. The 18 November entry itself names none.
Rating differences. The same flaw carries four scores on four pages (Table 2). The LiteLLM advisory's CVSS 4.0 vector, as the earlier copy prints it, sets attack complexity high and privileges required high, against the CVE record's low and low.
Table 2. One LiteLLM flaw as five pages rate it and describe its reach. Each is as printed; none is resolved.
| Page | Rating | Reach as printed |
|---|---|---|
| CISA catalogue entry, 18 Nov | No score | "remote attackers"; no word on authentication |
| CVE record, MITRE, 10 Apr | CVSS 3.1 8.8 HIGH, privileges required LOW, CWE-420 | "remote attackers" |
| X41 D-Sec advisory, 8 Apr | CVSS 4.0 8.7, severity High, CWE-94 | "Authenticated HTTP API request"; the master key in the workaround |
| LiteLLM advisory, read 15 Oct | Medium, CVSS 4.0 5.9, CWE-913 | A proxy-admin credential in default configurations |
| Red Hat container inside the CVE record | Red Hat severity Important, CVSS 3.1 8.8, CWE-94 | "A remote attacker" |
The Red Hat container in the CVE record, last updated on 15 July 2026, lists Red Hat Ansible Automation Platform 2.6, Red Hat OpenShift AI 3.3 and Lightspeed Core among its products under this CVE and points to two Red Hat errata, one for each of the first two. Its workaround field says mitigation is either not available or does not meet Red Hat's criteria. That is a reminder from the record itself that an AI gateway can sit inside a larger platform whose owners may not think of it as a LiteLLM install. The page does not say which of those products bundle LiteLLM beyond listing them.
The catalogue line is a summary, not a prerequisite. "Remote attackers" in the entry and the record's text describes where an attacker sits. X41 and LiteLLM's own advisory say what the attacker must hold. This site reads the entry's sentence as a catalogue summary and not as a statement that no credential is needed; the entry does not say either way, and the pages do not say whether the exploitation CISA lists needed one.
Two earlier signals, neither settling the question. First, the CISA container inside the CVE record prints an SSVC rating of "Exploitation: active" stamped 2026-06-15, 156 days before the 18 November entry (derived). The container was last updated on 19 November, and the page does not say what the June stamp records, so this site does not read it as the date exploitation began or as the date CISA knew. It also prints "Automatable: no", where the other three records print "yes". Second, Zenity Labs' post of 30 June 2026, saved for brief 346, says its decoy sensors saw "the first exploitation attempts" against CVE-2026-40217 within days of 10 April, nearly 600 attack requests from eight source addresses over six weeks. That is a log of decoy servers, not a victim list, and the post does not say that it is the activity CISA relied on. Zenity says it builds detection rules for its platform from such findings. The catalogue entry adds no detail of its own to either signal.
LiteLLM has had other incidents this site covered, including a poisoned release in October; no saved page connects that to this flaw.
REDCap: unauthenticated, and a survey hash
The entry for CVE-2026-90817 says an unauthenticated attacker could execute arbitrary code on the server by crafted HTTP requests that reach "an unintended controller route from a public survey context" with "a crafted file-path or stream parameter during data import processing". It ends with the sentence that matters: "Exploitation requires knowledge of a valid public survey hash." The record was published on 20 September 2026 by Securifera, a security firm that publishes advisories, not by Vanderbilt University, the REDCap developer named as the vendor in the entry. It repeats the preconditions ("The attacker does not have to be authenticated in order to exploit this, but exploitation requires knowledge of a valid public survey hash"), says the flaw exists in REDCap 13.3.0 and higher, and prints CVSS 3.1 9.8, CRITICAL, vector AV:N/AC:L/PR:N/UI:N, with CWE-94 and CWE-73. The CVE id was reserved on 13 September, 7 days before publication (derived). The record's solution text says to upgrade to REDCap 16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard Release, as applicable, and lists those three as unaffected. Its affected version field lists 13.3.0 with a default status of unknown.
This site's reading is that "unauthenticated" and "no precondition" are different statements. The vector prints low attack complexity and no privileges, and the description adds a knowledge requirement the vector has no slot for. Whether the hash is guessable, exposed in survey links people share, or was known to the attackers is not stated, and neither is how many public surveys exist. The entry's notes point to the REDCap project's community resources page, which this site did not read, so the vendor's own advisory text is not among the saved pages. The entry is due 2026-11-21 and carries forensicTriage "Yes". The record's date is 59 days before the entry (derived).
Apache Axis: a library with no fix to apply
The entry for CVE-2026-90436 describes "an unsafe reflection vulnerability" in which an unauthenticated remote attacker uses a crafted SOAP fault message to make Axis load and instantiate an attacker-specified class "when a suitable class is available on the application classpath". Then: "The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version." Its notes field adds that the flaw could affect an open source component or library "that could be used by different products", so the product named in the entry is not the only place to look.
The Apache record was published on 6 November 2026, 12 days before the entry (derived), and is less hedged: its title says "Apache Axis 1.x (EOL)" and its description opens with "UNSUPPORTED WHEN ASSIGNED". It says an inbound SOAP fault naming a class is loaded, and with a suitable class on the classpath this leads to remote code execution. It says "authentication handlers configured on a service do not protect against it", because the fault is handled before any per service handler chain runs. It affects all Axis 1.x versions through 1.4. Its advice is to migrate to a different SOAP engine, such as Apache Axis 2/Java, or to apply a patch from a linked commit, and it states: "The Apache Axis project does not expect to create an Axis 1.x release fixing this problem." So the catalogue's "apply mitigations in accordance with vendor instructions" resolves, for this flaw, to the vendor's instruction to leave Axis 1.x or patch it yourself. This site did not read the commit.
The record's own part prints only a textual severity, "critical". The score of 9.8, CVSS 3.1 with no privileges and no user interaction, sits in the CISA container, which is not the assigner. The record credits a researcher at the security firm OKIOK and was reserved on 11 September, 56 days before publication (derived). The CISA container's rating of Exploitation active is stamped 2026-11-17, a day before the entry. Which products bundle Axis 1.x, and which class an attacker used, are not stated. The entry is due 2026-11-21.
Synology DSM: the oldest record, and two operating systems in one sentence
The entry for CVE-2024-10441 names the product as "DiskStation Manager (DSM)" and says Synology DSM "contains an improper encoding or escaping of output vulnerability in the system plugin daemon in Synology BeeStation OS (BSM)" that could let a remote attacker execute arbitrary code "via unspecified vectors". The record was published on 19 March 2025, 609 days before the entry (derived), reserved on 28 October 2024, and its vendor part was last edited on 28 March 2025. It lists two products as affected: DSM before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1, with 7.1 before 7.1.1-42962-7 also listed, and BeeStation OS before 1.1-65374. It prints CVSS 3.1 9.8, CRITICAL, no privileges and no user interaction, and CWE-116. It references two Synology advisories, SA-24:20 for DSM and SA-24:23 for BeeStation, both named with "(PWN2OWN 2024)". The entry's notes link only the first. The record has no solution field; the fixed versions are the "before" versions in its description.
The catalogue entry's sentence joins the two: it says DSM contains a flaw in a daemon of BeeStation OS. The record says the same flaw is in both. This site reports the difference and does not resolve it.
Brief 565 covered Synology's press release of 29 October 2026, which said threat actors were exploiting "a vulnerability patched in December 2024" on outdated DSM to encrypt data and extort ransom, pointed to SA-24:20 and named no CVE. SA-24:20 covers three CVEs, of which this is the critical one; that brief's catalogue copy of 30 October held no Synology entry. The 18 November entry is 20 days after the press release (derived). No saved page says the catalogue entry concerns the activity Synology described, and the entry prints knownRansomwareCampaignUse as "Unknown". The CISA container, which that brief recorded as "Exploitation none" on 19 March 2025, now prints "active", stamped 2026-11-18. The entry is due 2026-11-21 and carries forensicTriage "Yes".
What the four catalogue entries set, and what they leave out
All four entries carry the same required action. It starts "Apply mitigations in accordance with vendor instructions", names CISA's directive BOD 26-04 and its "Forensics Triage Requirements", says to follow the directive's guidance for cloud services or discontinue use of the product if mitigations are unavailable, and ends: "Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines." This site did not read the directive or the triage requirements. CISA's catalogue is a US government list: this site reads the due date as a deadline for US federal agencies and a prompt for everyone else, because the entry text does not say whom it binds.
Table 3. Fields of the four entries as the catalogue file prints them (released 2026-11-18 at 19:17 UTC). The span from dateAdded to dueDate is derived.
| Product | dueDate, and days after dateAdded | forensicTriage | cwes in the entry |
|---|---|---|---|
| Synology DSM | 2026-11-21, 3 days | Yes | CWE-116 |
| BerriAI LiteLLM | 2026-12-02, 14 days | No | CWE-420 |
| Vanderbilt University REDCap | 2026-11-21, 3 days | Yes | CWE-73, CWE-94 |
| Apache Axis | 2026-11-21, 3 days | Yes | CWE-470 |
The three entries with a 3 day due date are the three with forensicTriage "Yes"; the one with 14 days is "No", as the Puppet entry in brief 738 was (14 days, "No"). The pattern is in the file. This site did not read the directive and does not say the field sets the date. All four print knownRansomwareCampaignUse as "Unknown", which is not a statement that no ransomware actor uses them.
Where the pages differ, with nothing resolved
Diagram 2 sets what the entry says against what the record or advisory says for all four, with the unstated row dashed. Table 4 lists the differences, each as printed.
Table 4. Differences between and inside the saved pages. Each is reported as printed; none is resolved.
| Point | One page prints | Another prints |
|---|---|---|
| LiteLLM: who can reach it | Entry and CVE text: "remote attackers"; CVE vector PR:L | X41: "Authenticated HTTP API request"; the master key. LiteLLM's advisory: a proxy-admin credential |
| LiteLLM: severity | CVE record 8.8 HIGH; X41 8.7 High; Red Hat Important | LiteLLM's advisory: medium, CVSS 4.0 5.9 |
| LiteLLM: weakness class | CWE-420 in the record and the entry | CWE-94 from X41 and Red Hat; CWE-913 from LiteLLM |
| LiteLLM: fixed release | X41: patched versions TBD, no vendor patch at publication; the record has no solution | LiteLLM's advisory: 1.83.11 in its text, 1.83.10 in its range and link; the entry names none |
| LiteLLM: what is affected | Record: an image digest as the version, "through 2026-04-08", vendor BerriAI | X41: main-latest and the same digest. LiteLLM: 1.81.8 up to before 1.83.10 |
| LiteLLM: when rated active | CISA container stamp: 2026-06-15 | Catalogue dateAdded: 2026-11-18 |
| REDCap: the precondition | Entry and record: unauthenticated, but a valid public survey hash is needed | Vector: low complexity, no privileges, 9.8 |
| REDCap: who wrote the record | Securifera, a security firm | Vanderbilt University is the vendor in the entry; its community page is in the notes, unread |
| Axis: end of life | Entry: "could be" end of life or end of service | Record: "UNSUPPORTED WHEN ASSIGNED"; no Axis 1.x release expected |
| Axis: severity | Apache's part: "critical", no score | CISA container: CVSS 3.1 9.8 |
| Synology: which product | Entry: DSM, in a daemon of BeeStation OS | Record: DSM and BeeStation OS listed as separate affected products with separate fixed versions |
| Synology: ransomware | Synology's 29 Oct warning (brief 565): attacks aim to encrypt data, no CVE named | Entry: knownRansomwareCampaignUse "Unknown" |
| Due dates | Three entries: 3 days, forensicTriage Yes | LiteLLM: 14 days, forensicTriage No |
What the pages state, and what they do not
Table 5. What the saved pages establish and what they leave open.
| Question | Stated | Not stated |
|---|---|---|
| Is each flaw exploited? | All four are in the catalogue from 2026-11-18, and each CISA container prints Exploitation active | Who, how many systems, since when, what they did, the evidence |
| Did LiteLLM exploitation need authentication? | X41 and LiteLLM's advisory say the endpoint is reached with a credential | What the exploitation CISA lists used |
| Which LiteLLM release fixes it? | LiteLLM's advisory as read on 15 Oct: 1.83.11 in text, 1.83.10 in range | The catalogue names none; the two figures are not reconciled; not re-read since |
| Is there a vendor fix for Axis 1.x? | Apache: none expected; migrate or apply a patch | Which products bundle Axis; whether the patch was reviewed |
| Are the four linked? | Nothing | Any shared campaign or actor |
| Ransomware use? | knownRansomwareCampaignUse: Unknown for all four | Any group, campaign or victim |
| How many are exposed? | Nothing counted | Instances of LiteLLM, REDCap, Axis or DSM |
What the records print
This is the defensive text the saved pages print, copied as printed. The pages print no log lines, hashes, network addresses or other indicators. This site prints no request body, no code from the advisory's bypass and no step beyond the advisory's one sentence. The first block is the LiteLLM entry and record; the version string is a container image digest the record uses as its version.
cveID: CVE-2026-40217
vendorProject: BerriAI
product: LiteLLM
vulnerabilityName: BerriAI LiteLLM Unprotected Alternate Channel Vulnerability
dateAdded: 2026-11-18
dueDate: 2026-12-02
knownRansomwareCampaignUse: Unknown
forensicTriage: No
cwes: CWE-420
record datePublished: 2026-04-10T13:43:23.147Z
record affected: vendor BerriAI, product LiteLLM, defaultStatus unknown
record version (custom): bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f
record description: LiteLLM through 2026-04-08
cvssV3_1: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 8.8 HIGH
CISA-ADP ssvc: timestamp 2026-06-15 Exploitation: active Automatable: no Technical Impact: total
The second block is the advisory X41 D-Sec published and the earlier reading of LiteLLM's own advisory. The nginx location line is X41's own defensive example, copied as printed; it denies the endpoint at a reverse proxy. LiteLLM's advisory gives the same workaround in words.
X41: Severity Rating: High
X41: Confirmed Affected Versions: main-latest (docker image, repo digest sha256:bb0639701796218a3447160e55c0f1097446e4e6085df7dfd39f476d4143743f)
X41: Confirmed Patched Versions: TBD
X41: Vector: Authenticated HTTP API request
X41: CVE: TBD CWE: CWE-94
X41: CVSS Score: 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
X41 workaround: location /guardrails/test_custom_code { deny all; return 403; }
X41 workaround: Avoid running LiteLLM as root. The default Docker image runs the process as root.
LiteLLM advisory: GHSA-wxxx-gvqv-xp7p, severity medium, published 2026-05-07, updated 2026-06-30
LiteLLM advisory: vulnerable_version_range >= 1.81.8, < 1.83.10 ; patched_versions >= 1.83.10
LiteLLM advisory text: Fixed in **`1.83.11`**. The hand-rolled sandbox has been replaced with `RestrictedPython`.
LiteLLM advisory text: block POST /guardrails/test_custom_code at your reverse proxy or API gateway
LiteLLM advisory: cvss_v4 CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N 5.9 CWE-913
The third block holds the REDCap, Axis and Synology entries and records, one field per line.
CVE-2026-90817 Vanderbilt University, Research Electronic Data Capture (REDCap)
entry: dateAdded 2026-11-18 dueDate 2026-11-21 forensicTriage Yes cwes CWE-73, CWE-94
record (assigner Securifera, published 2026-09-20): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 9.8 CRITICAL
record: This vulnerability exists in REDCap 13.3.0 and higher.
record: Upgrade to REDCap 16.0.49 LTS, 17.3.10 LTS, or 17.4.4 Standard Release, as applicable.
CVE-2026-90436 Apache, Axis
entry: dateAdded 2026-11-18 dueDate 2026-11-21 forensicTriage Yes cwes CWE-470
record (assigner Apache, published 2026-11-06): title Apache Axis 1.x (EOL)
record: affected versions up to and including 1.4 (Maven coordinates axis:axis and org.apache.axis:axis)
record: ** UNSUPPORTED WHEN ASSIGNED **
record: The Apache Axis project does not expect to create an Axis 1.x release fixing this problem.
CISA-ADP (not the assigner): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 9.8 CRITICAL
CVE-2024-10441 Synology, DiskStation Manager (DSM)
entry: dateAdded 2026-11-18 dueDate 2026-11-21 forensicTriage Yes cwes CWE-116
record (assigner Synology, published 2025-03-19): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 9.8 CRITICAL
record: Synology BeeStation OS (BSM) before 1.1-65374 and Synology DiskStation Manager (DSM) before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1
record references: Synology-SA-24:20 DSM (PWN2OWN 2024) ; Synology-SA-24:23 BeeStation (PWN2OWN 2024)
What to do, in order
First, what the entries and records say. Each entry says to apply mitigations in accordance with vendor instructions, in line with BOD 26-04 and the forensics triage requirements, by the due date: 2026-11-21 for REDCap, Axis and Synology DSM, 2026-12-02 for LiteLLM. The records name the fixes: REDCap 16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard Release; Synology DSM and BeeStation OS versions at or after those in the record; for Axis 1.x, Apache's advice to migrate or patch; for LiteLLM, the release in LiteLLM's advisory, which names two figures. The rest is this site's suggestion.
Take this with you
A checklist for owners of any of the four
- The records: apply the vendor fix named in each record by the due date, and for Axis 1.x follow Apache's advice to migrate to a supported engine or apply its patch. This site did not read the patch.
- This site's suggestion, LiteLLM: find every proxy instance, including inside AI platforms and containers (the record's Red Hat container lists three Red Hat products). Check whether the guardrail test path is reachable and by whom, and block it at the reverse proxy as both advisories say.
- This site's suggestion, LiteLLM: upgrade to a release your vendor confirms as fixed, and read LiteLLM's advisory yourself, because its text, its range and its release link do not name the same version.
- This site's suggestion, LiteLLM: review provider keys and spend logs, treat the proxy as a high value host, and run it as an unprivileged user where you can, as X41 advises.
- This site's suggestion, REDCap: check your version against 16.0.49, 17.3.10 and 17.4.4, find which surveys are public, apply the vendor's fix and review data import logs.
- This site's suggestion, Axis: list Java applications that bundle Axis 1.x, including inside other products, and remove or isolate them. There is no Axis 1.x release to wait for.
- This site's suggestion, Synology: apply the DSM or BeeStation OS update listed in the Synology advisories, and do not expose management interfaces to the internet.
- This site's suggestion, all four: start log review at the CVE record date, not the 18 November catalogue date. For Synology that is 19 March 2025, 609 days back (derived), and the pages give no earlier start for exploitation than the catalogue date.
- This site's suggestion, US federal agencies: the due date applies. Everyone else: use the catalogue as a prioritisation input, not as proof that your instance was reached.
- This site's suggestion: read the headline for what it is. The catalogue says exploited. It does not say by whom, how many, or how.
The question the list leaves open
The catalogue settles one thing four times: somebody has used these flaws. It does not say who, or whether they held a credential, or whether a patched installation was ever at risk. For the gateway the answer to the last part exists on a page the entry points to, in a form that does not agree with itself. If the AI gateway you run was on a public CVE record for 222 days before the exploited list named it, who was reading the record?
Key facts
Sources
- PrimaryThe Known Exploited Vulnerabilities catalogue feed, file released 2026-11-18 at 19:17 UTC with 1,786 entries: the four entries added on 18 November 2026, with dateAdded, requiredAction, dueDate, forensicTriage, knownRansomwareCampaignUse and notes. Saved on 19 November 2026CISAaccessed 2026-11-19
- PrimaryThe CVE record for LiteLLM CVE-2026-40217: dates, description, CVSS 3.1 metrics, version as an image digest, the CISA container with the 2026-06-15 stamp, and the Red Hat container. Read in full on 19 November 2026CVE Services (record assigned by MITRE, with CISA-ADP and Red Hat containers)accessed 2026-11-19
- PrimaryThe CVE record for REDCap CVE-2026-90817: description with the survey hash precondition, CVSS 3.1 9.8, affected and unaffected versions, solution text. Read in full on 19 November 2026CVE Services (record assigned by Securifera)accessed 2026-11-19
- PrimaryThe CVE record for Apache Axis CVE-2026-90436: unsupported when assigned, Axis 1.x through 1.4, no Axis 1.x release expected, and the CISA container. Read in full on 19 November 2026CVE Services (record assigned by Apache)accessed 2026-11-19
- PrimaryThe CVE record for Synology CVE-2024-10441: DSM and BeeStation OS affected versions, CVSS 3.1 9.8, two Synology advisory references, and the CISA container. Read in full on 19 November 2026CVE Services (record assigned by Synology)accessed 2026-11-19
- PrimaryAdvisory X41-2026-001, Guardrail Sandbox Escape in LiteLLM, dated 8 April 2026: severity, vector, CVSS 4.0, patched versions TBD, workarounds and the disclosure timeline. Saved on 19 November 2026; the proof of concept in it is not reproducedX41 D-Sec GmbHaccessed 2026-11-19
- PrimaryLiteLLM's repository advisory GHSA-wxxx-gvqv-xp7p for CVE-2026-40217: severity medium, proxy-admin credential, fixed versions. Read through GitHub's public API on 15 October 2026 for brief 346 and used here from that saved copy, not re-fetchedBerriAI (LiteLLM repository advisory)accessed 2026-10-15
- PrimaryPyPI release list for litellm: upload times of 1.83.9, 1.83.10 and 1.83.11. Read through the JSON release list on 15 October 2026 for brief 346 and used here from that saved copy, not re-fetchedPyPIaccessed 2026-10-15
- Reported byZenity's post of 30 June 2026 on decoy server findings, including attempts against CVE-2026-40217 from within days of 10 April. A vendor's own decoy log, saved on 15 October 2026 for brief 346 and used here from that saved copy, not re-fetchedZenity Labsaccessed 2026-10-15


