senaite.core Vulnerable to Eval Injection and Missing Authorization
CVE-2026-54569GHSA-jrw6-7x4q-w25j
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI senaite-core
- Affected
- >= 2.0.0, <= 2.6.0
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jrw6-7x4q-w25j lists affected ranges: PyPI senaite-core >=2.0.0 <=2.6.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jrw6-7x4q-w25j lists affected ranges: PyPI senaite-core >=2.0.0 <=2.6.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-54569: 1.16% estimated exploitation activity in the next 30 days; percentile 67.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An unauthenticated remote code execution vulnerability in the SENAITE JSON API allows any network-reachable attacker to execute arbitrary Python on the Zope worker process via a two-request anonymous chain. The /@@API/update route is reachable to anonymous callers and runs eval() on attacker-controlled input before any permission check fires. This is a different code path from the eval() in the calculations module: no authenticated account of any kind is required. Details The vulnerability is the chain of two independent flaws. Either fix alone breaks the unauthenticated chain, but the eval sink remains exploitable by any authenticated user with write access to a RecordsField, so both fixes are needed. 1. Missing AccessJSONAPI gate on JSON API write routes (CWE-862). The route at src/bika/lims/jsonapi/update.py:45-165 does not enforce the senaite.core: Access JSON API permission upfront. Compare with the sibling create.py:179-182, which does: The check is present on create…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-jrw6-7x4q-w25j
- Revision 2 · amended ·
Amended from osv record GHSA-jrw6-7x4q-w25j
- Revision 1 · created ·
Published from ghsa record GHSA-jrw6-7x4q-w25j
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-54569 Advisory: senaite.core Vulnerable to Eval Injection and Missing Authorization IDs: CVE-2026-54569, GHSA-jrw6-7x4q-w25j Record: https://patchnext.com/advisories/cve-2026-54569 (revision 3, source checked 26 Oct 2026, 13:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI senaite-core: affected >= 2.0.0, <= 2.6.0 ## Suggested inspection (read-only) - `python -m pip show senaite-core`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on senaite-core. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jrw6-7x4q-w25j (GitHub-reviewed advisory GHSA-jrw6-7x4q-w25j lists affected ranges: PyPI senaite-core >=2.0.0 <=2.6.0) - Verified: https://osv.dev/vulnerability/GHSA-jrw6-7x4q-w25j (OSV record GHSA-jrw6-7x4q-w25j lists affected ranges: PyPI senaite-core >=2.0.0 <=2.6.0) Commands are suggestions: review each one before running it.
Loading voting…