Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-54569Published 2026-08-26

CVE-2026-54569 — senaite senaite.core

criticalPublic exploit1 PoC repo

As of 2026-09-22, CVE-2026-54569 is a CRITICAL-severity vulnerability in senaite senaite.core, CVSS v3.1 9.8, EPSS 1.1% (66.1th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-54569, most recently “Chinese-Speaking 'Kapibala' Actor (Red Heron-Linked) Chains WordPress wp2shell, Zyxel GS1900, and Ubiquiti UniFi OS Flaws to Steal Government Data”.

CVSS v3.1
9.8/10Critical
EPSS
1.1%Higher than 66.1% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
9.5/10Threadlinqs triage score
Published
Updated 2026-09-22
CVSS v3.1 9.8 (CRITICAL) · EPSS 1.1% (higher than 66.1% of all scored CVEs) · Priority 9.5/10 · Published 2026-08-26

Last updated:

What is CVE-2026-54569?

SENAITE.CORE is the core framework for the SENAITE laboratory information management system. From 2.0.0 to 2.6.0, the SENAITE.CORE JSON API permits unauthenticated remote code execution through a two-request chain involving missing authorization and unsafe evaluation. The state-changing routes in src/bika/lims/jsonapi/update.py, including update, update_many, remove, doActionFor, doActionFor_many, and getusers, do not enforce the senaite.core: Access JSON API permission before resolving attacker-selected objects. In src/bika/lims/jsonapi/init.py, set_fields_from_request passes raw request values for RecordsField and RecordField instances to eval() before field mutator write-permission checks execute. An anonymous attacker can discover the bika_setup object identifier through @@uuid, send a value such as RejectionReasons to /@@API/update, and execute arbitrary Python in the Zope worker before a later mutation failure rolls back ZODB changes. The same unsafe evaluation pattern is present in src/senaite/core/browser/fields/record.py and src/senaite/core/browser/fields/records.py. Successful exploitation can expose or modify laboratory data, files, and accounts and can disrupt the service.

The record classifies CVE-2026-54569 under weakness classes CWE-95, CWE-862. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 85 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (FIRST)
1.1% probability of exploitation in the next 30 days, higher than 66.1% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
9.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-26

Is CVE-2026-54569 being exploited?

Weaponised exploit code for CVE-2026-54569 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 48 in the Threadlinqs vulnerability feed.

Affected products and versions

  • senaite: senaite.core

Affected software packages:

  • pip:senaite.core

How to fix CVE-2026-54569

No vendor patch reference has been recorded for CVE-2026-54569 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-54569

1 tracked threat in the Threadlinqs corpus references CVE-2026-54569, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories.

Vendor advisory and patch

Other references