CVE-2026-54569

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

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

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
No fix on record yet. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

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 pull request

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 pull request

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 / EcosystemFix (by version range) / 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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
senaite-core2.0.0 ... 2.6.0 (8 versions)
  • 2.0.0 through 2.6.0: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 182× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 325 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 225 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 10:41 UTCEG score recompute
  2. 2026-10-14 10:41 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-10-13 08:48 UTCEG score recompute
  5. 2026-10-13 08:48 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  7. 2026-10-12 15:56 UTCEG score recompute
  8. 2026-10-12 06:56 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:39 UTCEG score recompute
  10. 2026-10-11 16:54 UTCEG score recompute
  11. 2026-10-11 14:17 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  14. 2026-10-10 15:15 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-10 11:02 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 06:08 UTCEG score recompute
  17. 2026-10-10 06:08 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  19. 2026-10-09 07:42 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-09 03:22 UTCEG score recompute
  21. 2026-10-09 03:22 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  23. 2026-10-08 06:05 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-08 01:52 UTCEG score recompute
  25. 2026-10-08 01:52 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-10-07 09:55 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-07 05:19 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-07 01:08 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-06 20:43 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-06 16:05 UTCEG score recompute
  7. 2026-10-06 16:05 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  9. 2026-10-06 11:51 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-10-06 07:35 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-06 01:41 UTCEG score recompute
  12. 2026-10-06 01:41 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  14. 2026-10-05 17:39 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-05 13:28 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-05 09:02 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-05 04:37 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-04 23:53 UTCEG score recompute
  19. 2026-10-04 23:53 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  21. 2026-10-04 19:41 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-04 14:38 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-04 10:21 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-04 06:09 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-04 01:58 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-03 20:20 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-03 16:06 UTCEG score recompute
  28. 2026-10-03 16:06 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  30. 2026-10-03 04:54 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-03 00:30 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-02 19:25 UTCEG score recompute
  33. 2026-10-02 19:25 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  35. 2026-10-02 15:13 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  36. 2026-10-02 11:01 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-02 06:21 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-02 01:15 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-01 19:55 UTCEG score recompute
  40. 2026-10-01 19:55 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  42. 2026-10-01 13:55 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-01 09:44 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  44. 2026-10-01 05:32 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-01 01:01 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-09-30 19:58 UTCEG score recompute
  47. 2026-09-30 19:58 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  49. 2026-09-30 11:34 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-09-30 06:04 UTCEG score recompute
  51. 2026-09-30 06:04 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  53. 2026-09-29 12:26 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-09-29 05:43 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-09-29 01:31 UTCEG score recompute
  56. 2026-09-29 01:31 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-09-28 21:20 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-09-28 15:50 UTCEG score recompute
  59. 2026-09-28 15:50 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  61. 2026-09-28 11:26 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-28 07:15 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-09-28 03:04 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-27 22:51 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-09-27 18:39 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-27 14:28 UTCEG score recompute
  67. 2026-09-27 14:28 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  69. 2026-09-27 10:01 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-27 05:50 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-27 00:47 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-26 20:35 UTCEG score recompute
  73. 2026-09-26 20:35 UTCGHSA enrichmentGHSA-jrw6-7x4q-w25j · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 65th percentile
  75. 2026-09-25 16:59 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54569?
CVE-2026-54569 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54569 published?
The CVE record for CVE-2026-54569 was published on August 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-54569 actively exploited?
CVE-2026-54569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54569?
CVE-2026-54569 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54569?
No fix for CVE-2026-54569 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-54569 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs