CVE-2026-54569 is an unauthenticated remote code execution vulnerability in SENAITE.CORE versions 2.0.0 through 2.6.0, the framework used by the SENAITE laboratory information management system. A two-request JSON API exploit chain combines missing authorization on state-changing and user-enumeration routes with unsafe evaluation of attacker-controlled RecordField and RecordsField values. Raw values reach Python eval() before field-mutator write-permission validation. An anonymous attacker can obtain the bika_setup object identifier through the @@uuid endpoint and submit a crafted value to the update API route, executing arbitrary Python in the Zope worker process before a subsequent mutation failure rolls back ZODB changes. Related unsafe record-parsing patterns are also present in SENAITE.CORE record field handlers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability affecting SENAITE LIMS that was targeted by the observed threat cluster.
Vulnerability in SENAITE LIMS targeted during the reported multi-vector exploitation campaign.
A SENAITE LIMS vulnerability listed among technologies exploited or targeted by the observed actor.
Vulnerabilidad de SENAITE LIMS explotada durante la campaña.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.