CVE-2026-54569
Exploitation reported by one source. First attested on 2026-09-22 by GCVE · previdian.
- Published2026-08-26
- WeaknessCWE-862 · CWE-95
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2026-08-2616:16CVE publishedNVD
- 2026-09-2211:33Listed as exploited by GCVEGCVE
- 2026-09-2211:33Exploitation first reportedGCVE
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | ≥ 2.0.0, ≤ 2.6.0 | no fix published | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- senaite.coreAffected
- = >= 2.0.0, <= 2.6.0no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-08-26
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2026-08-26
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-10-23
- GCVEexploitation2026-09-22
- CISA-ADPSSVC decisionpoc2026-08-26
- CNACVSS 3.19.8known since 2026-10-23
- CNAweakness (CWE)CWE-862, CWE-95known since 2026-10-23
- FIRST EPSSEPSS score1.2 %2026-11-18
- OSVaffected packages—
- GitHub AdvisoriesadvisoryCRITICAL2026-08-26
Identifiers
- EUVD-2026-66596same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-jrw6-7x4q-w25jsame flawGitHub Advisory Database · CC-BY-4.0
- PYSEC-2026-3919same flawPyPA Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-08-26
- Last Modified
- 2026-09-09
- NVD status
- Deferred
- GitHub Advisory
- GHSA-jrw6-7x4q-w25j
Frequently asked questions
What is CVE-2026-54569?
Is CVE-2026-54569 actively exploited?
What is the CVSS score for CVE-2026-54569?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GCVE · GCVE dump terms (preserve source attribution)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-jrw6-7x4q-w25j
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0