CasaOS contains weak JWT secrets

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-2023-37266: 6.84% estimated exploitation activity in the next 30 days; percentile 94.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Unauthenticated attackers can craft arbitrary JWTs and access features that usually require authentication and execute arbitrary commands as root on CasaOS instances. Patches The problem was addressed by improving the validation of JWTs in 705bf1f. This patch is part of CasaOS 0.4.4. Workarounds Users should upgrade to CasaOS 0.4.4. If they can't, they should temporarily restrict access to CasaOS to untrusted users, for instance by not exposing it publicly. References - 705bf1f - https://www.sonarsource.com/blog/security-vulnerabilities-in-casaos/

Published by the source

17 Jul 2023, 14:40 UTC

Last modified by the source

12 Dec 2024, 22:30 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5q5-8mfw-p2hr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-37266

Advisory: CasaOS contains weak JWT secrets
IDs: CVE-2023-37266, GHSA-m5q5-8mfw-p2hr
Record: https://patchnext.com/advisories/cve-2023-37266 (revision 1, source checked 26 Oct 2026, 15:08 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 fix available; fixed versions by package: github.com/IceWhaleTech/CasaOS 0.4.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/IceWhaleTech/CasaOS: affected < 0.4.4; fixed in 0.4.4

## Suggested inspection (read-only)
- Go github.com/IceWhaleTech/CasaOS: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/IceWhaleTech/CasaOS.
- 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-m5q5-8mfw-p2hr (GitHub-reviewed advisory GHSA-m5q5-8mfw-p2hr lists affected ranges: Go github.com/IceWhaleTech/CasaOS >=0 <0.4.4)

Commands are suggestions: review each one before running it.