CVE-2026-55445: Qinglong: Incomplete fix for CVE-2026-3965: Improper Authentication
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.
Security readout for executives and security teams
Plain-English summary
Qinglong before 2.20.1 lets an unauthenticated remote attacker reset administrator credentials on an already initialized instance. That can hand control of the task management platform to an outsider. The source says the issue is fixed in 2.20.1.
Executive priority
Treat this as an urgent patching item for any exposed Qinglong instance. The business risk is administrative takeover of automation infrastructure, which may affect scripts, secrets, scheduled jobs, and operational workflows managed through Qinglong.
Technical view
The init guard checks /api/user/init but misses /open/user/init. A rewrite from /open/* to /api/$1 happens after JWT authentication and the guard have passed, allowing an unauthenticated PUT to reach the administrator initialization path. This is CWE-287 improper authentication with CVSS 4.0 score 9.3.
Likely exposure
Exposure is limited to Qinglong instances running versions before 2.20.1, especially if reachable from the internet or untrusted networks. The source bundle does not identify specific hosted services, package managers, containers, or deployment defaults beyond the whyour/qinglong product.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The described flaw is remotely reachable, unauthenticated, low complexity, and affects administrator credentials, so exploitation risk is serious even without confirmed in-the-wild activity.
Researcher notes
Evidence points to an incomplete fix involving route guarding and post-auth rewrite ordering. The fix reference is public, but the provided sources do not include proof-of-concept status, exploitation telemetry, or broader ecosystem impact. Avoid assuming compromise without log or credential evidence.
Mitigation direction
Upgrade Qinglong to version 2.20.1 or later.
Restrict Qinglong access to trusted networks until upgraded.
Rotate administrator credentials after patching if exposure is possible.
Review vendor advisory and release notes for any follow-up guidance.
Prioritize externally reachable instances before internal-only deployments.
Validation and detection
Inventory all Qinglong deployments and record their versions.
Confirm no instance is running below 2.20.1.
Check whether Qinglong is reachable from the internet or shared networks.
Review logs for suspicious requests to /open/user/init.
For forks, verify the init guard covers rewritten open routes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-287 · source CWE mapping
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.