Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-54569 – Unauthenticated Remote Code Execution – SENAITE.CORE 2.0.0–2.6.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-54569 is a critical, unauthenticated remote code execution vulnerability in SENAITE.CORE, the open-source laboratory information management system (LIMS). It results from a combination of an eval injection flaw and a missing authorization check in the JSON API, allowing unauthenticated attackers to execute arbitrary Python code on the server. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause 1 (CWE-95, Eval Injection): The JSON API’s field processing logic (invoked via the /@@API/update route) calls Python’s eval() on raw, user-supplied string values when parsing RecordField and RecordsField data types, before any input validation occurs.
  • Root cause 2 (CWE-862, Missing Authorization): The update route (and related routes such as update_many, remove, doActionFor, and doActionFor_many) does not enforce the Access JSON API permission check that is present on other routes such as create, allowing anonymous/unauthenticated requests to reach the vulnerable code path.
  • Attack vector: Network-based; a remote, unauthenticated attacker sends a crafted JSON API request to the /@@API/update endpoint containing Python expressions in place of expected field values.
  • Impact: Arbitrary Python code execution in the application context, leading to full compromise of the underlying ZODB data store, filesystem access, and the ability to create persistent administrative accounts — resulting in complete loss of confidentiality, integrity, and availability.

Affected software

  • senaite.core versions 2.0.0 through 2.6.0 (inclusive)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade senaite.core to version 2.7.0 or later, where the eval injection and missing authorization check have been fixed.
  • If immediate upgrade is not possible: Apply the vendor-provided hotfix package (SenaiteHotfix20260602) via buildout configuration and restart the instance.
  • Additional network mitigation: Restrict or block external access to the /@@API/update endpoint (and other unauthenticated JSON API state-changing routes) at a reverse proxy or WAF until the upgrade/hotfix is applied. Monitor JSON API request logs for Python syntax or suspicious eval-style payloads in request bodies.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: senaite.core.static/

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge