How severe is CVE-2026-90945?

CVE-2026-90945 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-90945 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-90945?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-90945 published?

CVE-2026-90945 was published on 2026-09-14 and last updated on 2026-09-16.

CVE-2026-90945

CVE-2026-90945 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v4: 9.3
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-321
Published: 2026-09-14
Last modified: 2026-09-16

Description

Crawlab through 0.6.3 uses a hard-coded HMAC-SHA256 secret for JWT token signing that cannot be overridden via configuration or environment variables. Unauthenticated attackers can forge valid administrator tokens to access administrative APIs and execute code on worker nodes.

Frequently asked questions

What is CVE-2026-90945?: Crawlab through 0.6.3 uses a hard-coded HMAC-SHA256 secret for JWT token signing that cannot be overridden via configuration or environment variables. Unauthenticated attackers can forge valid administrator tokens to access administrative APIs and execute code on worker nodes.
How severe is CVE-2026-90945?: CVE-2026-90945 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-90945 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-90945?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-90945 published?: CVE-2026-90945 was published on 2026-09-14 and last updated on 2026-09-16.

References

Other CWE-321 vulnerabilities

CVE-2024-30207 — Critical (CVSS 10.0): A vulnerability has been identified in SIMATIC RTLS Locating Manager (6GT2780-0DA00) (All versions < V3.0.1.1), SIMATIC…
CVE-2014-5419 — Critical (CVSS 10.0): GE Multilink ML800, ML1200, ML1600, and ML2400 switches with firmware 4.2.1 and earlier and Multilink ML810, ML3000,…
CVE-2024-35344 — Critical (CVSS 9.9): Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects…
CVE-2026-89026 — Critical (CVSS 9.8): The Issabel Framework, the web framework supporting Issabel PBX software, before commit b97dbaf contains a hard-coded…
CVE-2026-87929 — Critical (CVSS 9.8): MaxSite CMS through 109.6 ships with a hardcoded session encryption key in application/config/config.php that is never…
CVE-2026-16504 — Critical (CVSS 9.8): Deployment of the VPS.org one-click Zulip template deploys a hardcoded application signing key, a default database…

Browse all CWE-321 vulnerabilities →