CVE-2026-54569

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 26, 2026

Advisory Details (5)

Auto-updated Aug 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github, github_commit.
github Patch Available🟡 PoC Available

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') and Missing Authorization in senaite.core · Advisory · senaite/senaite.core · GitHub

https://github.com/senaite/senaite.core/security/advisories/GHSA-jrw6-7x4q-w25j
github_pr

Enforce the AccessJSONAPI permission on state-changing JSON API routes

Fix merged in senaite/senaite.core PR #2919 on 2026-05-26 — awaiting tagged release

https://github.com/senaite/senaite.core/pull/2919
github_pr

Replace unsafe eval with literal record parsing

Fix merged in senaite/senaite.core PR #2903 on 2026-05-22 — awaiting tagged release

https://github.com/senaite/senaite.core/pull/2903
github_commit

commit ef4b6d73575b (senaite/senaite.core)

Fix landed in senaite/senaite.core commit ef4b6d73575b — awaiting tagged release

https://github.com/senaite/senaite.core/commit/ef4b6d73575b0fbc0edc6114e5e025089aaf9eb7
github_commit

commit a24d65e99a17 (senaite/senaite.core)

Fix landed in senaite/senaite.core commit a24d65e99a17 — awaiting tagged release

https://github.com/senaite/senaite.core/commit/a24d65e99a17ac43c5374ed9f0a60d0fe60d2f74

Vendor Advisories for CVE-2026-54569(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipsenaite.core—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 32× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:45 UTCEG score recompute
  2. 2026-08-30 01:45 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 21:34 UTCGHSA enrichment
  5. 2026-08-29 17:22 UTCGHSA enrichment
  6. 2026-08-29 12:33 UTCGHSA enrichment
  7. 2026-08-29 08:22 UTCGHSA enrichment
  8. 2026-08-29 04:09 UTCGHSA enrichment
  9. 2026-08-28 23:57 UTCEG score recompute
  10. 2026-08-28 23:57 UTCGHSA enrichment
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 16:51 UTCGHSA enrichment
  13. 2026-08-28 12:21 UTCGHSA enrichment
  14. 2026-08-28 08:08 UTCGHSA enrichment
  15. 2026-08-28 03:55 UTCGHSA enrichment
  16. 2026-08-27 23:41 UTCGHSA enrichment
  17. 2026-08-27 19:30 UTCGHSA enrichment
  18. 2026-08-27 15:19 UTCEG score recompute
  19. 2026-08-27 15:19 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-27 11:08 UTCGHSA enrichment
  22. 2026-08-27 06:56 UTCGHSA enrichment
  23. 2026-08-27 02:45 UTCGHSA enrichment
  24. 2026-08-26 22:34 UTCGHSA enrichment
  25. 2026-08-26 18:23 UTCEG score recompute
Show 7 more
  1. 2026-08-26 18:23 UTCGHSA enrichment
  2. 2026-08-26 18:03 UTCEG score recompute
  3. 2026-08-26 18:03 UTCGHSA enrichment
  4. 2026-08-26 16:37 UTCEG score recompute
  5. 2026-08-26 16:37 UTCGHSA enrichment
  6. 2026-08-26 15:39 UTCEG score recompute
  7. 2026-08-26 15:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-54569?
CVE-2026-54569 is a critical vulnerability published on August 26, 2026. 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…
When was CVE-2026-54569 disclosed?
CVE-2026-54569 was first published in the National Vulnerability Database on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54569 actively exploited?
CVE-2026-54569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.2% of all scored CVEs.
What is the CVSS score of CVE-2026-54569?
CVE-2026-54569 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-54569?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54569, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54569

Explore →

Is Your Infrastructure Affected by CVE-2026-54569?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs